Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP MWI

Status
Not open for further replies.

wpetilli

Technical User
May 17, 2011
1,877
US
We are in the process of having a new 3rd party VM system installed. System is online and we are able to cover to it. our CM is a 6.0.1 and have SIP (TLS) trunks to ASM and the VM system is an entity link of ASM via SIP (TCP). Our phones are 9630 H.323. We are able to cover to a test mailbox, but the MWI is not working. Seems like it is failing when it hits CM on the comeback with 501 not implemented. Any clues on what can be missing in CM.. the station is set as SIP-ADJ on page 2 to match the HG.
 
What would a traceSM show you? You ought to see a NOTIFY from voicemail to SM and then SM to CM. SIP domain from the VM has to match the far end signalling group, mailbox and extension numbers ought to line up. Is your voicemail sending SIP notifies through SM to CM, or directly to CM? I would think the former would be required. MWI type sip-adjunct, basic stuff like that.
 
501 Not Implemented

The server does not support the functionality required to fulfill the
request. This is the appropriate response when a UAS does not
recognize the request method and is not capable of supporting it for
any user.


I would verify configuration in your 3rd party VM system Solution

What system is it ? They should be able to pin point it.


Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
turned out Session Manager didn't have the CM as the destination entity for the return traffic from the VM system. It was sorted.. thanks again guys.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top