PPM Tshooting

[wpetilli]

I'm tshooting a remote SIP hardphone and PPM issue. Phone is pointed to SBC-A (standalone) in datacenter A with registration to a local SM. In SM there is the remote access config with this SBC and SM in it and when things are normal, all is fine.

When we point the phone to SBC-B (Standalone) in datacenter B, the phone still registers to the same SM in datacenter A. This is when PPM does not work. There is nothing in the remote access config that references SBC-B and SM-A, which I think is the issue. I'm not sure I'd be able to add this or not, as it may not allow duplicate entries with the same IP's used. I haven't tried that, but perhaps someone already knows the answer. I have my network team tee'd up to check if the ports are open between that internal SM and the SBC in the other datacenter. That could be it as well. What should be the starting point with licking this?

 

[kyle555]

I'd like to be corrected on this, but as far as I can tell, the remote access config in SMGR is only about ticking the "remote office" box in user registrations.


What do your PPM mapping profiles look like?

What did you do to "point" the phone to SBC-B? Just point it there or change the primary/secondary SM to only have SM2 as primary?

Consider: Suppose you setup a RW SBC and didn't do a PPM mapping profile on the SBC. What would happen?
Well, I'd expect your phone would be pointed to the B1 IP and register via SIP.
Then it'd request PPM from the B1 IP which would have a reverse proxy (without a PPM mapping profile) and get to the SM.
SM would respond with your primary/secondary SMs in PPM and it would pass through the SBC to the phone and the phone would try registering to SM on 10.x.x.x and become unregistered because PPM is the law when it comes to where a phone should register.

Unless you changed the SM profile to only have SM2, or at least have it as primary SM, then the phone probably registered to SM2, got PPM, saw the public IP of SBC-A was it's primary SM and did what it thought it should do - go to its primary

 

[wpetilli]

I edited the 46xx.settings file to point the sip controller list of SBC-B. The phone registers and it registers to the primary SM, which is in the alternate data center.
On SBC-B, the PPM mapping profile has the SM in the alternate DC as the server address to the signaling address of SBC-B.

for the reverse proxy, it doesn't look right. In there it has the SM from Datacenter B as the server address.

I'm kind of lost now. I have 2 standalone SBC's in alternate DC's. Using DNS, we point to Datacenter A as the primary. There's an SM in each of those DC's that are prim/sec in the SIP endpoint profiles. In this case the SM in the Datacenter A is the primary. I'm assuming it's not the firewall between data center A SM and the DMZ of private SBC interface A in data center B. Could be, but probably not. The setup of SBC-B in the PPM and reverse proxy sections are probably sideways. Which is where I guess I'm lost with how it should be.

 

[kyle555]

Phone always remembers ppm.

Register the phone once.

Reboot.
46xx not available? Ppm says go sm1
Reboot.
46xx available and says use sm2? Fine. It still remembered ppm says SM1 and 2 and still goes to SM1.
Clear the phone, reboot, have 46xx point to SM2, login, get PPM saying SM1 is primary, you'll still wind up on sm1.

If your ppm mapping is goofy on sbc2/sm2, you'll know when you make that phone's only SM be SM2 as primary and reload PPM

 

[wpetilli]

I rebooted the phone once and now I see the buttons. What the?