PPM

[wpetilli]

I'm on a roll today. I'm testing my remote SIP endpoints and suddenly they are logging in and showing 9 call-appearances and not showing any of the bridges assigned. Assuming this is PPM related, but this has been working for quite some time. Is there something on SM I can restart the PPM service?

 

[kyle555]

restart mgmt
do that at the CLI of SM. It's not service impacting. Depending on release, I recall it fixing a few gremlins in 6.3.12ish.

You can traceSM with PPM enabled and "reload complete" in SM User Registrations to force a PPM download and see in GetAllEndpointConfiguration if the keys are actually being passed from SM to the phone.

Maybe the bridges are on another page? I think you might be hitting the problem where SIP shows your appearances before bridges or something along those lines

 

[wpetilli]

I was able to validate PPM data against internally registered SIP endpoints to ASM. I restarted the SBC application and it started working again remotely.

 

[wpetilli]

Can I run this one across.. adding bridged lines seem to work fine and show up on the remote endpoint, but things like autodials don't show up at all. How do you troubleshoot that?

 

[kyle555]

contents of GetAllEndpointConfigurationResponse direct on SM vs thru SBC

 

[wpetilli]

Is that data and things like the brdg-appr data considered the same? Meaning should one work and not the other?

 

[kyle555]

it should include all the keys - so if you have autodials programmed, it should come across in there just like brdg-appr

do a traceSM with PPM on both the SBC and SM. See if what's coming out the SBC is the same as what came out the SM

 

[wpetilli]

I ran the trace on both and for the getcontactlist I see ASM respond to the internal SBC interface with NoOfElements 0. Which can't be correct because the endpoint autodials configured. On the SBC trace I'm not even seeing responses in the trace from ASM.

 

[wpetilli]

from the CLI of both systems I ran a date command. The SBC seems to be 15 seconds behind ASM. Can that be an issue?

 

[kyle555]

autodial is a key only locally significant in CM.
It's not a "contact" in the SIP sense like you monitor it's presence or anything.
15s? probably not. BUT some events are timestamped from SM thru and can get screwy, but probably not that

Look at the keys pushed thru getallendpointconfig

 

[wpetilli]

I found this setting in one of the readme files.. SMGR_AUTO_FAVORITE 1 It definitely helped. Got most of the buttons I programmed, but a bit inconsistent. 1 of the autodials is just not showing up where the other 3 do. Weird.

 

[wpetilli]

Also upgraded the F/W to 4.0.3 and everything appeared on the expansion module. I then added a new autodial and it doesn't appear. Reload and reboot and still nothing. Not understanding.

 

[kyle555]

Expansion modules are buggy as hell right now. J's arent 1st class citizens until R8

 

[bankingguy]

what is the version of your CM?

 

[gwebster]

The J100 software ReadMe file has a list of known limitations if you are not on a current release of CM/SM/SMGR.