cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
706
Views
4
Helpful
1
Replies

Unity Connection 8.62 MWI issue

jeff.singh_2
Level 3
Level 3

           we have a CUCM 7.1x with a skinny  integration to unity 7.02 and a sip integration to Connection 8.62 .

MWI works fine on the skinny integration however we are not seeing any changes to the MWI indicator under user>MWI for the sip integration, the current status is always off - does not change to trying or pending or on . The IP phone light is off but I should atleast see the change under user>mwi settings.

Port status monitor shows mwi is being attempted:

State, 91, 908003289393, Event is [NULL]

Application, 91, 908003289393, <--MessageEditing

State, 91, 908003289393, Event is [NULL]

State, 91, 908003289393, State - PHGreeting.cde!AfterMsg

State, 91, 908003289393, Event is [NULL]

Application, 91, 908003289393, PHTransfer

State, 91, 908003289393, State - PHTransfer.cde!LoadInfo

State, 91, 908003289393, Event is [TrueEvent]

Application, 91, 908003289393, PHGreeting

State, 91, 908003289393, State - PHGreeting.cde!PlayGreeting

Display, 91, 908003289393, Call answered if needed

Display, 91, 908003289393, Playing greeting for Call Handler: Goodbye

CallData, 39, CallerId=, CalledId=, RedirectingId=, Origin=16, Reason=1024, CallGuid=, CallerName=, LastRedirectingId=, LastRedirectingReason=1024, PortDisplayName=CUCMLHR-1-023

Display, 39, , Dialing (MWI) '87090093'

Display, 39, , Idle

State, 91, 908003289393, Event is [HangupEvent]

State, 91, 908003289393, State - PHGreeting.cde!DoHangup

State, 91, 908003289393, Event is [HangupEvent]

Display, 91, 908003289393, Idle

CallData, 40, CallerId=, CalledId=, RedirectingId=, Origin=16, Reason=1024, CallGuid=, CallerName=, LastRedirectingId=, LastRedirectingReason=1024, PortDisplayName=CUCMLHR-1-010

Display, 40, , Dialing (MWI) '87090093'

Display, 40, , Idle

CallData, 41, CallerId=, CalledId=, RedirectingId=, Origin=16, Reason=1024, CallGuid=, CallerName=, LastRedirectingId=, LastRedirectingReason=1024, PortDisplayName=CUCMLHR-1-005

Display, 41, , Dialing (MWI) '87090093'

Display, 41, , Idle

CallData, 42, CallerId=, CalledId=, RedirectingId=, Origin=16, Reason=1024, CallGuid=, CallerName=, LastRedirectingId=, LastRedirectingReason=1024, PortDisplayName=CUCMLHR-1-196

Display, 42, , Dialing (MWI) '87090093'

Display, 42, , Idle

CallData, 43, CallerId=, CalledId=, RedirectingId=, Origin=16, Reason=1024, CallGuid=, CallerName=, LastRedirectingId=, LastRedirectingReason=1024, PortDisplayName=CUCMLHR-1-148

Display, 43, , Dialing (MWI) '87090093'

Display, 43, , Idle

1 Reply 1

Jonathan Schulenberg
Hall of Fame
Hall of Fame
The IP phone light is off but I should atleast see the change under user>mwi settings.

Untrue. The status will reflect whether the request to CUCM was successful or not.

What does the SIP trace look like for the unsolicited NOTIFY to the user's DN? The MWI on/off DNs are not used for SIP integrations so it should be direct to that user's DN. Best double-check the config guide to ensure you haven't missed a step too:

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/integration/guide/cucm_sip/cucintcucmsip060.html

Please remember to rate helpful responses and identify helpful or correct answers.