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 IamaSherpa 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
- Thread starter
- #2
in user registrations, reload complete - that makes a PPM update
If you made the change in CM directly, you need to incremental sync, or in the inventory, set "enable updates" in CM - you need to pop the SMGR CA in CM as trusted and tell CM to syslog securely to SMGR.
So, when your 'list history' shows 'wpetilli change station 1234' and that syslog hits SMGR, SMGR goes to display station 1234 and find what changed to put it in it's db that replicates to SM to get crunched for PPM that the phone gets.
If you made the change in CM directly, you need to incremental sync, or in the inventory, set "enable updates" in CM - you need to pop the SMGR CA in CM as trusted and tell CM to syslog securely to SMGR.
So, when your 'list history' shows 'wpetilli change station 1234' and that syslog hits SMGR, SMGR goes to display station 1234 and find what changed to put it in it's db that replicates to SM to get crunched for PPM that the phone gets.
- Thread starter
- #4
I have CM as a managed element by SMGR. I've also tried using the endpoint editor in SMGR to modify the station, instead of in CM. Not sure if this matters, but I'm trying to do dual registration (h.323 / SIP). Like I said, both register fine and I can pass calls. I thought the 'CONFIG_SERVER_SECURE_MODE' setting in the 46xx file was the issue, because I changed that to 1 and I did get the additional call-appr that was added. Originally it was 3. However, I also had a few busy-ind buttons that didn't show up.
tracesm with ppm enabled?
Between CM/SM, there might be some bugs re:H323 dual registration. I believe the feature was intended for soft clients.
I think the logic being "if you're going to set up SIP hard phones remote on a SBC anyway why won't you do it in the office?" and sure, maybe the whole floor/subnet isn't ready to flip.
The feature buttons aren't on the 2nd page of the sip phone when you key over to the right?
Between CM/SM, there might be some bugs re:H323 dual registration. I believe the feature was intended for soft clients.
I think the logic being "if you're going to set up SIP hard phones remote on a SBC anyway why won't you do it in the office?" and sure, maybe the whole floor/subnet isn't ready to flip.
The feature buttons aren't on the 2nd page of the sip phone when you key over to the right?
- Thread starter
- #6
If I register directly against SM, no issues. I see the button changes as I make them. Putting it outside and behind the SBC I do see the subscribe messages going back and forth while tracing PPM. When the phone registers the phone doesn't even have the same buttons I left off with when it was registered directly against SM. Making any changes and doing the reload complete doesn't change the phone at all. Firewall also is clean, for once.
smells like ppm missing
You probably see something in the 200 OK to the subscription response from CM that says request terminated or something.
Is A1 in the ip-network-map as belonging to a network region who's authoritative domain is that of the SIP phone?
Presuming on SM is fine i'd reckon your aar and private tables are all good.
You probably see something in the 200 OK to the subscription response from CM that says request terminated or something.
Is A1 in the ip-network-map as belonging to a network region who's authoritative domain is that of the SIP phone?
Presuming on SM is fine i'd reckon your aar and private tables are all good.
- Thread starter
- #8
I did add the entries to the network map, which weren't in there. I made another button change using the element cut through. Made sure the changes were consistent by looking in CM and in the endpoint editor. With the tracesbc running on PPM I did a reload complete from ASM. I get the Notify from ASM to the SBC with the event:avaya-ccs-profile. The notify then goes from the SBC to the remote endpoint and receives a 200OK from the endpoint. But the changes never occur on the phone.
maybe logout/login
if you trace with SIP and PPM enabled, you're supposed to see quite a bit of information. If a SUBSCRIBE gets a 200OK from CM with 'request terminated no body in polling notify' then you know you've got some goofy problem.
What's in your topology hiding profiles? I BELIEVE CM uses the IP in the oldest/bottom-most VIA header for network region. That's ultimately where the topology hiding profile on the SBC ought to rewrite that to the A1 IP inward thru SM to CM.
if you trace with SIP and PPM enabled, you're supposed to see quite a bit of information. If a SUBSCRIBE gets a 200OK from CM with 'request terminated no body in polling notify' then you know you've got some goofy problem.
What's in your topology hiding profiles? I BELIEVE CM uses the IP in the oldest/bottom-most VIA header for network region. That's ultimately where the topology hiding profile on the SBC ought to rewrite that to the A1 IP inward thru SM to CM.
- Thread starter
- #10
I commented out/removed the SET CONFIG_SERVER line out of the 46xx file and PPM started working. Considering I had the SM in that line is a bit bizarre. I just can't believe all the nuances with this setup. After the last one I thought this would be a breeze.
oh yeah. set config_server makes the phone use that for PPM and not the published IP from SM/SBC/PPM mapping profile.
"I just can't believe all the nuances with this setup. After the last one I thought this would be a breeze."
You must be new here.
"I just can't believe all the nuances with this setup. After the last one I thought this would be a breeze."
You must be new here.
- Thread starter
- #12
I've left my remote endpoint connected and I while I haven't been able to lock down the exact intervals, the endpoint is randomly logging out with a message saying another endpoint has logged in with that extension'. This is a test number that only I have knowledge about. On user registrations in SMGR this number is not registered. What would be triggering this phone to do that?
If it's doing simultaneous registration, maybe something about the topology hiding is not letting SM see the 2 signaling paths belong to the same phone.
There'd be some implicit difference if I took 2 dumb polycoms and registered the same extension to SM1 and SM2 vs having an Avaya phone simultaneously register.
There'd be some implicit difference if I took 2 dumb polycoms and registered the same extension to SM1 and SM2 vs having an Avaya phone simultaneously register.
- Thread starter
- #14
What's only max 1 registration? The Max Simultaneous Devices in the SM profile? Or the registration policy in the settings file? It can be set to simultaneous or alternate and there's a 'max simultaneous' parameter in the settings file too.
So, if I had Core SM1, Core SM2 and BSM, I'd say "simultaneous" with "max" 3 but i could still have "max devices" at 1 in my SM profile and my 1 9600 phone would simultaneously register to Core SM1/2/BSM.
If I had a IPO or Audiocodes as a branch gateway, I'd do everything the same except say "max simultaneous" is '2' in the settings file. When the 9600 registers, it'll get SM1, SM2, and "survivability server" from the SM profile in it's PPM as it's 3 SIP registrars. BSM supports registration while on core SM1/2 but a IPO or Audiocodes don't, so if I told the phone it should simultaneously register to all 3, bad things would happen.
Conversely, if you got max devices 1 in your SM profile, and something about the SBC is confusing the fact that it's the same endpoint trying to simultaneously register rather than two different endpoints trying to register the same profile, that could explain why the phone's 2nd registration is successful but SM1 tells the phone that it's first registration has been logged out. Because the phone considers the two registrations to be to the same core, if it's told it's logged out from either, it'll just go back to a login screen.
Do the phones stay up OK on 2 SMs when on the LAN vs the SBC? If so, I'd say you look hard at the register messages on both sides of the SBC to SM1 and 2. There's something in there that would make the SMs consider them 2 registrations from 2 endpoints and not 2 registrations from the same endpoint.
So, if I had Core SM1, Core SM2 and BSM, I'd say "simultaneous" with "max" 3 but i could still have "max devices" at 1 in my SM profile and my 1 9600 phone would simultaneously register to Core SM1/2/BSM.
If I had a IPO or Audiocodes as a branch gateway, I'd do everything the same except say "max simultaneous" is '2' in the settings file. When the 9600 registers, it'll get SM1, SM2, and "survivability server" from the SM profile in it's PPM as it's 3 SIP registrars. BSM supports registration while on core SM1/2 but a IPO or Audiocodes don't, so if I told the phone it should simultaneously register to all 3, bad things would happen.
Conversely, if you got max devices 1 in your SM profile, and something about the SBC is confusing the fact that it's the same endpoint trying to simultaneously register rather than two different endpoints trying to register the same profile, that could explain why the phone's 2nd registration is successful but SM1 tells the phone that it's first registration has been logged out. Because the phone considers the two registrations to be to the same core, if it's told it's logged out from either, it'll just go back to a login screen.
Do the phones stay up OK on 2 SMs when on the LAN vs the SBC? If so, I'd say you look hard at the register messages on both sides of the SBC to SM1 and 2. There's something in there that would make the SMs consider them 2 registrations from 2 endpoints and not 2 registrations from the same endpoint.
- Thread starter
- #16
Yes, the phone stays registered to both SM's when I keep it off the SBC. The setting for registrations is in the SM profile and is set to '1'. Dual registration (h.323/SIP) only permits that field to be set to '1'. I haven't checked the settings file. I wasn't aware there was a setting for registrations. Based on this it's clear it's the SBC as the common denominator.
- Thread starter
- #17
Yeah, and there's something in the SBC config that's not letting both SMs transparently see 2 registers from 1 device.
I was dealing with some IPOffices as branch gateways. Basically, they can act like big ATAs where it registers all its analog ports over a SIP trunk to SM and then SM registers that down to CM. The IPO had SM trunks to Core SM 1 and 2. The sw load of IPO was goofy and I could see it registering to SM1 with expires:180 - which means it should try to re-register at 50% of that - so, 90 seconds later. And then less than 90 seconds later it'd try SM2 who'd answer with expires:137 or whatever the time difference was. And the end result is that the analog ports were always 1/3rd online on SM1, 1/3rd online on SM2 and 1/3rd offline.
To have simultaneous registration to 2 or 3 SMs, that's a function of Avaya's SIP telephony - so, you need 9600s and SMs - you won't get a Polycom to register to 2 SMs simultaneously.
And there's something getting stripped off at your SBC causing that.
I gotta figure this out soon too and the way I'm looking at it, if I have a HA SBC in front, both IPs live on one live box and survive to the other anyway. I might be just be inclined to bite the bullet and say no simultaneous. If SM1 dies, the speech path'll stay up and the phone will register to SM2. Worst case I take a little bump.
I was dealing with some IPOffices as branch gateways. Basically, they can act like big ATAs where it registers all its analog ports over a SIP trunk to SM and then SM registers that down to CM. The IPO had SM trunks to Core SM 1 and 2. The sw load of IPO was goofy and I could see it registering to SM1 with expires:180 - which means it should try to re-register at 50% of that - so, 90 seconds later. And then less than 90 seconds later it'd try SM2 who'd answer with expires:137 or whatever the time difference was. And the end result is that the analog ports were always 1/3rd online on SM1, 1/3rd online on SM2 and 1/3rd offline.
To have simultaneous registration to 2 or 3 SMs, that's a function of Avaya's SIP telephony - so, you need 9600s and SMs - you won't get a Polycom to register to 2 SMs simultaneously.
And there's something getting stripped off at your SBC causing that.
I gotta figure this out soon too and the way I'm looking at it, if I have a HA SBC in front, both IPs live on one live box and survive to the other anyway. I might be just be inclined to bite the bullet and say no simultaneous. If SM1 dies, the speech path'll stay up and the phone will register to SM2. Worst case I take a little bump.
- Thread starter
- #19
In my case I have a DNS entry that points at 2 separate SBC's. They are setup to only go to the main unless the probe cannot reach it, so not round robin. On the primary SBC I only have routing setup to 1 SM. As I mentioned, in the SM profile for the user there's the primary and secondary SM for registration. In the settings file of the phone I have the controller list setup with the dns entry of the SBC and then the 2 SM's. So in my case the SBC isn't aware of the other SM.
- Thread starter
- #20
- Status
Similar threads
