Voxalot / SIP Broker Support Forums - View Single Post

richard · 04-25-2007, 04:13 PM

Hi Martin

Here is the response I received from our MWI question to Counterpath.

Session Initiation Protocol
Request-Line: NOTIFY sip:1000@xx.xx.xx.xxx:61656;rinstance=c0f1f6de6a2a 208e;transport=udp SIP/2.0
Message Header
Message body
Messages-Waiting: yes\r\n
Message-Account: sip:asterisk@xx.xx.xx.xxx\r\n
Voice-Message: 1/0 (0/0)\r\n

The active thread on counterpath is here:

CounterPath SIP Softphone Support :: View topic - eyeBeam MWI Notify Message Requirements

I hope this can be easily fixed.

Thanks for your great support!!!

Richard

04-25-2007, 04:13 PM	#14
richard Senior Member Join Date: Mar 2006 Posts: 153 Thanks: 37 Thanked 7 Times in 7 Posts	Hi Martin Here is the response I received from our MWI question to Counterpath. Session Initiation Protocol Request-Line: NOTIFY sip:1000@xx.xx.xx.xxx:61656;rinstance=c0f1f6de6a2a 208e;transport=udp SIP/2.0 Message Header Message body Messages-Waiting: yes\r\n Message-Account: sip:asterisk@xx.xx.xx.xxx\r\n Voice-Message: 1/0 (0/0)\r\n The active thread on counterpath is here: CounterPath SIP Softphone Support :: View topic - eyeBeam MWI Notify Message Requirements I hope this can be easily fixed. Thanks for your great support!!! Richard