What is the expected behavior of a remote SIP phone when making button changes? I have a successfully registered 9611G that can make calls etc.. I am testing making normal station button changes and the phone isn't updating them. I haven't rebooted the phone yet, but I would have thought this would be something I wouldn't have to reboot for.
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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Remote SIP 961x
- Thread starter wpetilli
- Start date
TraceSBC and watch registration and PPM.
Broadly speaking, the endpoint will use whatever SM tells it to. And Avaya's never been clear enough about when a setting in DHCP 242 steps on 46xx or when static config overrides all and what settings CM for H323 or SM for SIP sends to the phone as being authoritative.
Regardless, it's probably fair to say that everything happening on SBC1 and SM1, the messaging to the phone would include the same stuff to simultaneously register to SM2 as if the phone were inside. So, I'd figure from remote access side of SM, if you have many entries say for SM1/2/3, then even if I come in SM1, if my PPM would say that I register to SM1/2, then that remote access data would funnel up to the first SBC. You might need to do stuff in your PPM mapping profile to match all SBCs in each SBC.
Broadly speaking, the endpoint will use whatever SM tells it to. And Avaya's never been clear enough about when a setting in DHCP 242 steps on 46xx or when static config overrides all and what settings CM for H323 or SM for SIP sends to the phone as being authoritative.
Regardless, it's probably fair to say that everything happening on SBC1 and SM1, the messaging to the phone would include the same stuff to simultaneously register to SM2 as if the phone were inside. So, I'd figure from remote access side of SM, if you have many entries say for SM1/2/3, then even if I come in SM1, if my PPM would say that I register to SM1/2, then that remote access data would funnel up to the first SBC. You might need to do stuff in your PPM mapping profile to match all SBCs in each SBC.
- Thread starter
- #22
I had another case of that. Visiting users would have their phone logout at the 1 hour mark.
In the settings file, you should only ever put core SMs, not BSMs. BSMs only learn about users that are assigned to that BSM in their SM profile.
So, when a user from site 1 went to login their phone at site 2, it got PPM information to register to that phones CM1/2/BSM, but the settings file had the local BSM in it and the phone would send a register periodically to that BSM. Because the settings file pointed to the BSM at that site and because the user's profile wasn't provisioned on that site, the register got a 404 and got logged out.
Moral of the story for me was "never put 3rd point of registration in a settings file, let PPM do it. It persists through reboots on the phone"
Maybe you can enable SNMP on the phone and walk it - it usually provides the list of parameters the phone is using - or, go in the SIP proxy part of the craft menu and see what it's doing for the hour it's up. Usually the 9600 phone's 'expires' timer is 3600, so it should re-register after 30 mins - so it's likely not something around refreshing registrations if you only see the problem around an hour in.
In the settings file, you should only ever put core SMs, not BSMs. BSMs only learn about users that are assigned to that BSM in their SM profile.
So, when a user from site 1 went to login their phone at site 2, it got PPM information to register to that phones CM1/2/BSM, but the settings file had the local BSM in it and the phone would send a register periodically to that BSM. Because the settings file pointed to the BSM at that site and because the user's profile wasn't provisioned on that site, the register got a 404 and got logged out.
Moral of the story for me was "never put 3rd point of registration in a settings file, let PPM do it. It persists through reboots on the phone"
Maybe you can enable SNMP on the phone and walk it - it usually provides the list of parameters the phone is using - or, go in the SIP proxy part of the craft menu and see what it's doing for the hour it's up. Usually the 9600 phone's 'expires' timer is 3600, so it should re-register after 30 mins - so it's likely not something around refreshing registrations if you only see the problem around an hour in.
- Thread starter
- #24
Rodrigo Estanol
Technical User
Hi Wpetilli
What SIP firmware version do you have. I had the same issue, the feature buttons didn't appear, until I made the upgrade to the 7.1.0.1.1 version for the 9611 and 9621 SIP phones. Hope it helps!
Best regards!
What SIP firmware version do you have. I had the same issue, the feature buttons didn't appear, until I made the upgrade to the 7.1.0.1.1 version for the 9611 and 9621 SIP phones. Hope it helps!
Best regards!
- Status
