-
1
- #1
This is for anyone who was banging their head against a wall wondering why the sip trunks stopped working after migrating a stand alone 500V2 to an expansion system.
After I migrated the expansion system the sip trunks dedicated to the expansion system looked like they were up, yet you could not call out and could not call in.
I performed all the normal steps, reboot, delete and reconfigure the SIP trunk and I could not get the SIP trunks to work.
When performing a monitor trace, I would not see anything about licensing. I saw 15:47:16 827886mS Sip: SIP Line (18) GetNetworkTopologySource Use Network Topology badly configured.
After checking all network paths, which were configured properly. It turned out to be a licensing issue.
Even if you are using the Local/Primary server as your license host instead of WebLM, you need to set your SIP trunk reserved licenses under Licenses-->Remote Server.
AJ-
After I migrated the expansion system the sip trunks dedicated to the expansion system looked like they were up, yet you could not call out and could not call in.
I performed all the normal steps, reboot, delete and reconfigure the SIP trunk and I could not get the SIP trunks to work.
When performing a monitor trace, I would not see anything about licensing. I saw 15:47:16 827886mS Sip: SIP Line (18) GetNetworkTopologySource Use Network Topology badly configured.
After checking all network paths, which were configured properly. It turned out to be a licensing issue.
Even if you are using the Local/Primary server as your license host instead of WebLM, you need to set your SIP trunk reserved licenses under Licenses-->Remote Server.
AJ-
