System Manager - Message-Summary

[RedTech443]

I have a previous post about this, but it got a bit complicated as I was trying to fix this problem, so I wanted to start a new one with fresh results.

We have avaya system manager 6.3 with a few SIP devices connected with no problems. However 2 of the new devices I am adding are acting funny.

I am adding some Ascom i62 Messenger devices. I have been using the following document.

https://www.devconnectprogram.com/fileMedia/download/ab68069a-4c7a-4cd0-9b26-60d383ca9edd

Everything works perfectly, except the message waiting indicator on one of the phones. One phone will get voice mail message waiting indicator, and the other will not. I have changed phones and different extensions. Here is a screen shot of what I think is a good place to look, however I am not as familiar with System manager and not sure where to look next. As you can see I pointed to what I suspect is the problem, there must be some way to force a message-summary register?

I have added a FAC to my system to force a MWI on and off, this works for the device that registers, but does not work for the phone that will not register with MWI.

 

[redphone]

There is no way to force a subscription for a SIP user. The SIP endpoint needs to send a SUBSCRIBE message with a SIP header of Event: message-summary, and Session Manager needs to Accept the subscription. Session Manager will only forward a NOTIFY message for MWI to a user with an active subscription for "message-summary".

ssh to Session Manager and run traceSM -uni while you reboot the phone in question. See if the phone sends a SUBSCRIBE message soon after it sends a REGISTER. Within the SUBSCRIBE message, check the Event and Expires headers. If it does not send a SUBSCRIBE message, then the problem lies within the phone.

 

[RedTech443]

Thank you, I will try this soon & post back with info.

 

[RedTech443]

Ok here is my summary of a working phone connecting, the first phone connecting is the one that works, but the second one ext 2313 is the problem, I noticed that it says (4) 400 Bad Request(no body in polling NOTIFY), and no route available, not sure what to look at here. Any suggestions?


14:47:22.939 |--REGISTE->| | | (9) <sip:7900@10.40.0.56> Exp:120
14:47:22.942 |<--Unautho-| | | (9) 401 Unauthorized
14:47:22.949 |--REGISTE->| | | (9) <sip:7900@10.40.0.56> Exp:120
14:47:22.952 |<--200 OK--| | | (9) 200 OK (REGISTER)
14:47:22.961 |--SUBSCRI->| | | (10) <sip:7900@10.40.0.56> Ev:message-summary Exp:120
14:47:22.963 |<--Unautho-| | | (10) 401 Unauthorized
14:47:22.975 |--SUBSCRI->| | | (10) <sip:7900@10.40.0.56> Ev:message-summary Exp:120
14:47:22.977 |<--ACCEPTE-| | | (10) 202 ACCEPTED
14:47:22.977 |<--NOTIFY--| | | (3) <sip:7900@10.40.0.56> Ev:message-summary
14:47:22.979 | |--SUBSCRI->| | (11) <sip:7900@dkhsip.############.org> Ev:message-summary Exp:0
14:47:22.981 | |<--200 OK--| | (11) 200 OK (SUBSCRIBE)
14:47:22.981 | |<--NOTIFY--| | (11) <sip:7900@dkhsip.#############.org> Ev:message-summary
14:47:22.983 |<--NOTIFY--| | | (10) <sip:7900@10.40.0.56> Ev:message-summary
14:47:22.984 | |--200 OK-->| | (11) 200 OK (NOTIFY)





14:51:50.486 |--REGISTE->| | | (2) <sip:2313@10.40.0.56> Exp:120
14:51:50.488 |<--Unautho-| | | (2) 401 Unauthorized
14:51:50.495 |--REGISTE->| | | (2) <sip:2313@10.40.0.56> Exp:120
14:51:50.499 |<--200 OK--| | | (2) 200 OK (REGISTER)
14:51:50.508 |--SUBSCRI->| | | (3) <sip:2313@10.40.0.56> Ev:message-summary Exp:120
14:51:50.510 |<--Unautho-| | | (3) 401 Unauthorized
14:51:50.515 |--SUBSCRI->| | | (3) <sip:2313@10.40.0.56> Ev:message-summary Exp:120
14:51:50.517 |<--ACCEPTE-| | | (3) 202 ACCEPTED
14:51:50.520 | |--SUBSCRI->| | (4) <sip:2313@dkhsip.##########.org> Ev:message-summary Exp:0
14:51:50.521 | |<--200 OK--| | (4) 200 OK (SUBSCRIBE)
14:51:50.521 | |<--NOTIFY--| | (4) <sip:2313@dkhsip.########.org> Ev:message-summary
14:51:50.524 | |--Bad Req->| | (4) 400 Bad Request(no body in polling NOTIFY)
14:51:50.524 |<--NOTIFY--| | | (3) <sip:2313@10.40.0.56> Ev:message-summary
14:53:18.524 |--SUBSCRI->| | | (3) <sip:2313@10.40.0.56> Ev:message-summary Exp:120
14:53:18.525 |--REGISTE->| | | (2) <sip:2313@10.40.0.56> Exp:120
14:53:18.526 |<--Call/Tr-| | | (3) 481 Call/Transaction Does Not Exist
14:53:18.528 |<--Unautho-| | | (2) 401 Unauthorized
14:53:19.281 |--REGISTE->| | | (2) <sip:2313@10.40.0.56> Exp:120
14:53:19.284 |<--200 OK--| | | (2) 200 OK (REGISTER)
14:53:28.742 |--SUBSCRI->| | | (3) <sip:2313@10.40.0.56> Ev:message-summary Exp:120
14:53:28.745 |<--Unautho-| | | (3) 401 Unauthorized
14:53:29.199 |--SUBSCRI->| | | (3) <sip:2313@10.40.0.56> Ev:message-summary Exp:120
14:53:29.202 |<--Not Fou-| | | (3) 404 Not Found (No route available)

 

[RedTech443]

I Think I figured it out, I did not have an entry for each individual station extension in my CM under public unknown numbering. I had to add extesnions in question (2313) to pub unknown numbers, and the SIP trunk group, so it would have a route to follow. That is what I somehow gathered from the traceSM.

 

[sekitori]

Thanks for the info - we're using a few i62 Talkers in our company.
Always nice to have extra info..

Sekitori