MWI Change

[martin]

It would be interesting to know what they now expect given that MWI is based on a generic SIP SUBCRIBE message.

It might help if they can tell us what the NOTIFY message needs to look like.

[richard]

Hi Martin

I posed your question to Counterpath on what they are expecting as a Notify Message.

Here is the thread: CounterPath SIP Softphone Support :: View topic - eyeBeam MWI Notify Message Requirements

"...I have been using Voxalot for quite some time and some time last year they were able to tigger the MWI in eyeBEAM 1.1 to work with their service. After the release of eyeBEAM 1.5, the MWI stopped working.

Voxalot is quite willing to fully support eyeBEAM 1.5, but they don't know what the NOTIFY message needs to look like. They are also assuming that MWI is based on a generic SIP SUBCRIBE message.

Can you help clarify the MWI Notify Message Requirement? Voxalot.com has a large user base, many of which use eyeBEAM..."

[clundestad]

MWI does not seem to work on my ATA - it's a Zyxel P2002.
The only configuration is an on/off switch for MWI.

But it's not a big deal for me, getting the voicemail message via email is notification good enough...

[richard]

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

[wilsonhlacerda]

MWI is working fine with Grandstream HT-496 (firmware 1.0.3.70).

[richard]

Hi Martin

Does this information from CounterPath Help? Do you think you can get MWI working with Voxalot and eyeBeam once again?

If so, this would be fantastic and very much appreciated.

Thanks Richard

Originally Posted by richard

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

[mgoebel]

I use the Fritz!Box Fon ATA. When somebody leaves a message on my Sipgate voicemail I see the "Internet" light blinking when I come home. That doesn't happen when somebody leaves a message in my Voxalot voicemail box. So I suppose that Voxalot's MWI doesn't work with my ATA.

You can learn more about this ATA here: AVM - FRITZ! Box

[richard]

Hi Martin

I was wondering if this information from CounterPath was useful and if it will help fix the issue allowing eyeBEAM to shown the MWI when used with Voxalot.

Is there anything more information that I should get from eyeBEAM?

Richard

Originally Posted by richard

Hi Martin

Does this information from CounterPath Help? Do you think you can get MWI working with Voxalot and eyeBeam once again?

If so, this would be fantastic and very much appreciated.

Thanks Richard

[martin]

Originally Posted by richard

Hi Martin

I was wondering if this information from CounterPath was useful and if it will help fix the issue allowing eyeBEAM to shown the MWI when used with Voxalot.

Is there anything more information that I should get from eyeBEAM?

Richard

Hi Richard,

Yes it was and thanks. I raised a problem ticket and embedded the information you gave.

[richard]

Thank you Martin. I'll let you know as soon as I notice it working again

Originally Posted by martin

Hi Richard,

Yes it was and thanks. I raised a problem ticket and embedded the information you gave.