CM 5.1.2 - 2xS8730 - 14xG650 in 7 PNs -- recently upgraded from CM 2.2.2
I have 2 CLANs, 1 MedPro, and 4 MR320s in ip-network-region 3. 1 CLAN and all MR320s where added at the time of the upgrade.
Since doing the upgrade IP Agent can no longer call digital stations, analog stations, place outbound calls on digital or PRI trunks, or receive inbound calls from digital or PRI trunks. All of which are in network-region 2. There are no CLANS in network-region 2, only MedPros. network-region 2 is in a different network not connected to network-region 3's network.
NR2 is completely separate from the rest of the network, on separate switches with no connectivity to the rest of our network. NR2 is used for PN DSP resources only, no VoIP traffic.
Someone suggested I add an Inter Network Region connection (page 3) between nr3 and nr2. This works temporarily, but eventually (within 10 minutes) the ip-network-region fails the NR-CONN test and all inter-region calling is locked out until I remove the connection and re-add it. Obviously the NR-CONN test fails because the network-regions are on separate networks and the ping test cannot pass to any node in nr2.
Additionally, only 1 out of every 3 call attempts actually results in a talk path. Trace shows the call connected every time, but only 1/3 of them can the agent hear.
What changed from 2.2 to 5.1? Is there a way to disable NR-CONN between these two network-regions? What are some additional troubleshooting steps I can take? Am I doing something wrong here?
Thanks for any help you can provide!
I have 2 CLANs, 1 MedPro, and 4 MR320s in ip-network-region 3. 1 CLAN and all MR320s where added at the time of the upgrade.
Since doing the upgrade IP Agent can no longer call digital stations, analog stations, place outbound calls on digital or PRI trunks, or receive inbound calls from digital or PRI trunks. All of which are in network-region 2. There are no CLANS in network-region 2, only MedPros. network-region 2 is in a different network not connected to network-region 3's network.
NR2 is completely separate from the rest of the network, on separate switches with no connectivity to the rest of our network. NR2 is used for PN DSP resources only, no VoIP traffic.
Someone suggested I add an Inter Network Region connection (page 3) between nr3 and nr2. This works temporarily, but eventually (within 10 minutes) the ip-network-region fails the NR-CONN test and all inter-region calling is locked out until I remove the connection and re-add it. Obviously the NR-CONN test fails because the network-regions are on separate networks and the ping test cannot pass to any node in nr2.
Additionally, only 1 out of every 3 call attempts actually results in a talk path. Trace shows the call connected every time, but only 1/3 of them can the agent hear.
What changed from 2.2 to 5.1? Is there a way to disable NR-CONN between these two network-regions? What are some additional troubleshooting steps I can take? Am I doing something wrong here?
Thanks for any help you can provide!