No readout voice messages (MWI) CM<->HMS400R3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • kminin
    Whiz
    • Aug 2010
    • 31

    No readout voice messages (MWI) CM<->HMS400R3

    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
    Attached Files
  • ankamath
    Whiz
    .
    • Jul 2013
    • 29

    #2
    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:[email protected]\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:[email protected]>;index=1
    History-Info: "HMS400" <sip:[email protected]>;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:[email protected]?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

    Comment

    • psa78
      Aspiring Member
      • Jun 2015
      • 1

      #3
      Originally posted by ankamath View Post
      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:[email protected]>;index=1
      History-Info: "HMS400" <sip:[email protected]>;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
      Last edited by psa78; 09-29-2015, 02:45 AM.

      Comment

      Loading