IVM Bug

[youneeq]

Hi, Isubmitted a bug report recently and have heard nothing back, so I'm posting on here as well, also in case other ppl have run into the same issue... In IVM 4.11 (my version) and confirmed in the latest 5.02, when "Caller Blocking" is checked and "Block private or unknown numbers" is checked and a SIP call comes in with CID prefixed with +1 it always gets blocked. It's interpreting these numbers as private or unknown when it shouldn't be.

 

Also, is IVM/Axon ever going to get MWI support? And an option to be able to playback voicemails in first in/first out order would be great. Thanks!

[djakober]

Hi Casual,

 

Thank you. I have submitted this to our development team for testing. I will also make sure that MWI and FI/FO VM playback are listed as product suggestions.

 

DJ

[youneeq]

Hi DJ,

 

Did anyone confirm and/or fix the bug? I can't imagine it's a huge change in code. I'd really like to be able to block the phone spam.

 

Thanks,

youneeq

 

 

Hi Casual,

 

Thank you. I have submitted this to our development team for testing. I will also make sure that MWI and FI/FO VM playback are listed as product suggestions.

 

DJ

[djakober]

Hi DJ,

 

Did anyone confirm and/or fix the bug? I can't imagine it's a huge change in code. I'd really like to be able to block the phone spam.

 

Thanks,

youneeq

 

Hi,

 

IVM does have Message Waiting Indicator Support - at this time it has only been thoroughly tested with Axon - only limitation is your light will stay on as long as there are messages in your IVM mailbox folder, so if you get your voicemails by email attachment, you would have to use the "delete after sending" option in IVM for the MWI light to be accurate.

 

FI/FO is a suggestion for next release.

 

The current code recognizes a call as private if it does not begin with a digit, it is being modified to allow for the '+' sign. We should be able to get this released fairly soon.

 

Hope this helps.

 

DJ

[youneeq]

Hi,

 

IVM does have Message Waiting Indicator Support - at this time it has only been thoroughly tested with Axon - only limitation is your light will stay on as long as there are messages in your IVM mailbox folder, so if you get your voicemails by email attachment, you would have to use the "delete after sending" option in IVM for the MWI light to be accurate.

 

FI/FO is a suggestion for next release.

 

The current code recognizes a call as private if it does not begin with a digit, it is being modified to allow for the '+' sign. We should be able to get this released fairly soon.

 

Hope this helps.

 

DJ

 

Hi DJ,

 

Looks like you guys took care of the "+" prefix bug in the latest IVM 5.03 beta. Thanks!.

 

But! The MWI still does not work correctly in IVM 5.03. I've submitted a bug report for you guys explaining it. I'll post here for anyone else's benefit.

 

IVM's SIP NOTIFY message logic is not consistent. When IP phone sends SUBSCRIBE message, IVM sends proper NOTIFY message including "Voice-Message: 1/0" header but if IVM receives a new voicemail it then sends a NOTIFY message but missing the "Voice-Message: 2/0" header. So the registered IP phone does not get updated with the total new message count from IVM. If the IP phone sends a SUBSCRIBE then IVM will properly send the updated "Voice-Message: 2/0" header. It should send this header all the time.

 

Here's examples of working and non-working trace from IVM.

 

After IP phone SUBSCRIBE is sent:

 

19:59:22 UDP Packet Sent to 10.1.2.219:36390 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

NOTIFY sip:101@10.1.2.219:36390;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.1.2.212:5061;rport;branch=z9hG4bK193788

To: "phone"<sip:101@10.1.2.212>;tag=bb0eff73

From: "phone"<sip:101@10.1.2.212>;tag=21

Call-ID: NWMzNzIzM2QzODBiMjVjNmIwYjU0YWUxMDk1ZDE0Zjc.

CSeq: 243 NOTIFY

Max-Forwards: 20

User-Agent: NCH Software IVM Answering Attendant 5.03

Contact: <sip:199@10.1.2.212:5061>

Event: message-summary

Subscription-State: active

Content-Type: application/simple-message-summary

Content-Length: 80

 

Messages-Waiting: yes

Message-Account: sip:101@10.1.2.212

Voice-Message: 1/0

 

----------------------------------------------------------------

 

After leaving new voicemail:

 

20:03:49 UDP Packet Sent to 10.1.2.219:36390 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

NOTIFY sip:101@10.1.2.219:36390;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.1.2.212:5061;rport;branch=z9hG4bK203788

To: "phone"<sip:101@10.1.2.212>;tag=bb0eff73

From: "phone"<sip:101@10.1.2.212>;tag=21

Call-ID: NWMzNzIzM2QzODBiMjVjNmIwYjU0YWUxMDk1ZDE0Zjc.

CSeq: 244 NOTIFY

Max-Forwards: 20

User-Agent: NCH Software IVM Answering Attendant 5.03

Contact: <sip:199@10.1.2.212:5061>

Event: message-summary

Subscription-State: active

Content-Type: application/simple-message-summary

Content-Length: 80

 

Messages-Waiting: yes

Message-Account: sip:101@10.1.2.212

Missing this header ----> Voice-Message: 2/0

[graigloxton]

By this time the NCH team has developed the codes to correct the IVM bug.

[youneeq]

By this time the NCH team has developed the codes to correct the IVM bug.

 

Hi Graig, so you are confirming the bug is fixed? If so, that's great. What version off IVM so I can check it out?

[youneeq]

It looks like this was somewhat fixed but now when you delete one or more messages from a mailbox an updated MWI header with the updated ratio of new to old messages is not sent. I'll try to submit another beg report I suppose.