01-07-2013 04:12 PM - edited 03-16-2019 03:02 PM
I’m hoping someone can help me design/validate a pair of cisco voice gateways. I have two C2921s proving PSTN connectivity to a Microsoft Lync environment. I’m trying to figure out the best way to set these up for high availability. Below is a topology on how everything is connected. I’m having issues achieving full redundancy on either a T1/QSIG trunk failure or an upstream IP/Ethernet failure. Below are the results of my failover testing.
So far so good with failure scenarios, now here’s where the issues begin:
Is there any cisco voice technologies to help me overcome some of these issues?
Solved! Go to Solution.
01-08-2013 02:12 AM
Hi
That's correct.
On Lync, you should just need to associate both the gateways that you have defined in your topology to the PSTN Route in the voice policy - have you done that?
If so, test it again, but there may be some change that needs to be made so that Lync retries.
For example, with CUCM and H.323 gateways you have to enter the following:
'no dial-peer outbound status-check pots'
This stops the gateway returning 'user busy' if the E1/T1 is down, and makes it return a failure instead. Then CUCM fails over to the next gateway... If it doesn't fail over on Lync I'd try the same thing.
Aaron
01-07-2013 04:44 PM
I am NOT and expert at this, but it is an interesting problem and I thought maybe a tcl script could be leveraged to shutdown the T1 port when IP connectivity is lost in at least one of the two scenarios. Look at this post and see if it is any help:
https://supportforums.cisco.com/thread/2090532
Good luck.
01-08-2013 01:00 AM
Hi
You can use this configuration to monitor a specific LAN interface and drop the ISDN when it goes down:
voice-port 0/0/0:15
cptone GB
busyout monitor GigabitEthernet0/0
If the failure is further away you would be best to have a resilient network in place.... or go down the TCL route and monitor a route or something.
The gateway will return a code to Lync that tells it that the destination is not available. Lync should be able to respond to this and try the next gateway...
Aaron
-
01-08-2013 01:09 AM
Aaron, I take it that I would modify your configuration to drop my ISDN D-Channel correct? I'll have to test out T1 trunk failure some more to see if Lync is notified about the failure. Last time I simulated this, Lync would fail the call every time it tried routing it to the failed gateway.
voice-port 0/0/0:23
cptone GB
busyout monitor GigabitEthernet0/0
01-08-2013 02:12 AM
Hi
That's correct.
On Lync, you should just need to associate both the gateways that you have defined in your topology to the PSTN Route in the voice policy - have you done that?
If so, test it again, but there may be some change that needs to be made so that Lync retries.
For example, with CUCM and H.323 gateways you have to enter the following:
'no dial-peer outbound status-check pots'
This stops the gateway returning 'user busy' if the E1/T1 is down, and makes it return a failure instead. Then CUCM fails over to the next gateway... If it doesn't fail over on Lync I'd try the same thing.
Aaron
01-09-2013 10:00 AM
Hey Aaron, the following command resolved the issue of lync not hunting for another available gateway if the primary gw lost its PRI: 'no dial-peer outbound status-check pots'.
Without the command, the GW would return a "SIP/2.0 404 Not Found" error. With the command 'no dial-peer outbound status-check pots', the GW returns a "SIP/2.0 503 Service Unavailable" error. If Lync receives a 4xx error, it will fail the call. However, if Lync receives a 5xx error, it continues to hunt for the next available route/gateway.
01-09-2013 01:15 PM
Hi
Cool - I thought it was a good theory!
Thanks for reporting back!
Aaron
Principal Engineer at Logicalis UK
Please rate helpful posts...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide