SM re-configuration

[Juancho2015]

Hi. Due to some issues in datacenter, I installed a new SMGR (different IP and name) and now I need to re-configure SM to work with it. What commands need to be used?

 

[kyle555]

add the SM sip entity in the new SMGR, do a SMNetSetup on the SM and point it to the new SMGR.

That's a start, depending on release, SM might ask for the new SMGR fqdn, or you might need to add it to its hosts file

 

[Juancho2015]

SM is 6.3. I'm not able to edit the hosts file since I don't have the root password.

 

[kyle555]

then the SMNetSetup script should be all you need on the SM side to re-point it to a new System Manager.

Ideally, if you had routing that SM needed to do, you'd want that programming to be in the new SMGR before you did all that reconfiguration

 

[Juancho2015]

Thanks a lot Kyle! Take care.

 

[Juancho2015]

I finished SM configuration and data replication is working just fine. However SM shows that CM entity is down with reason 408 request timeout. Signaling group and trunk group are up. Maybe I forgot some settings. Any idea?

 

[kyle555]

TCP or TLS?
Do the IPs match in the sig group/node-names and the entities/entity links?

 

[Juancho2015]

I'm currently using TCP, and the IPs do match.

 

[Juancho2015]

I made an experiment to diagnose the monitoring issue. I set up a dummy CM entity pointing to my PC, then started a Wireshark capture.

I see packets coming from SM with source port 5060 and destination port being anything but 5060, typically between 20000 and 65000. What is this?

 

[Juancho2015]

Solved! Networking issue....

 

[Juancho2015]

Hi. Now, when calling from PSTN to CM stations through SBC, SM sends 407 proxy authentication required and the call does not complete. I'm pretty sure this is not an SM normal operation. What configurations should I check?