Avaya Support Forums

Avaya Support Forums (http://support.avaya.com/forums/index.php)
-   IP Telephony and Convergence (http://support.avaya.com/forums/forumdisplay.php?f=8)
-   -   No readout voice messages (MWI) CM<->HMS400R3 (http://support.avaya.com/forums/showthread.php?t=4616)

kminin 05-16-2014 03:12 AM

No readout voice messages (MWI) CM<->HMS400R3
 
2 Attachment(s)
Good day.
On your phone (1608) does not work lamp (MWI). Messages NOTIFY HMS sends. Calls from HMS operator pass. What could be the problem?
CM 6.3
HMS400 R3.0.5.0

ankamath 06-18-2014 12:59 AM

Hi,

Thanks for the logs... It seems that the HMS is sending a NOTIFY for the MWI

Messages-Waiting: yes\r\n
Message-Account: sip:6000@172.20.0.134\r\n

Now the question is why is it sending it to 6000 instead it should be sending it to 6411 which is the one it seemed should be recieving the Voicemails according to the first History Info sent from the CM...

From what i see, i see two History Info Header's out of which 6000 is the first sent and then 6411 is seen...

History-Info: <sip:6000@172.20.0.252>;index=1
History-Info: "HMS400" <sip:6411@172.20.0.252>;index=1.2

[truncated] History-Info: "\320\256\321\200\320\270\320\271 \320\235\320\270\320\272\321\203\320\273\320\270\3 20\275" <sip:6000@172.20.0.252?Reason=SIP%3Bcause%3D480%3B text%3D%22Temporarily%20Unavailable%22&Reason=Redi rection%3Bcause%3DNOR

Can you explain the call flow since it does not seem to be a straight forward calls from an extn to voicemail...

Kindly explain who is calling from which extn and which extn is forward etc..

Regards
Amith K

psa78 09-29-2015 02:13 AM

Quote:

Originally Posted by ankamath (Post 11264)
Hi,

From what i see, i see two History Info Header's out of which 6000 is the first sent and then 6411 is seen...

History-Info: <sip:6000@172.20.0.252>;index=1
History-Info: "HMS400" <sip:6411@172.20.0.252>;index=1.2



Regards
Amith K

Hi!
I've found, that sip-message NOTIFY from hms to cm are sending with use UDP transport. But the connection between CM and HMS established by TCP protocol.
Unfortunately, in the last firmware HMS 400 3.0.8 not include a fix this bug.

This a field from those messages, which CM was received successfully:
Via: SIP/2.0 TCP XX.XX.XX.XX
This a field in message NOTIFY:
Via: SIP/2.0 UDP XX.XX.XX.XX

Regards, Sergey


All times are GMT -7. The time now is 11:30 AM.