IP trunk survivability

[kvoy]

I've a customer with the following scenario:
main-site: duplicated S8710 running CM 3.1.2 and a PN with 2 G650
remote site: 1 G700 and S8300-LSP running CM 3.1.2.

We have installed two QuesCom GSM gateway, one at Main-site and the other on the Remote-site.
The GSM gateway interoperate with Avaya Communication Manager using H.323 trunks, one per site.

I've configurate two sig-group with a C-Lan node-name board in Near-End field and the Quescom in Far-End field.

The problem we experienced, is that when the remote-site lost the connection with main-site, go in LSP mode and the related sig group go down cause the system can't reach the CLan board.

Normally if I want to use the S8300 board for the configuration of IP trunk, I've to insert the S8300 or "procr" as Near-End node-name. But in this case I can't insert the "procr" as node-name, cause the platform is different (duplicate S8710) and we can only use a CLan node name for the configuration of H.323 sig group.

Does somebody have any suggestion for fix the problem?



The configuration was made following the guide line described in the Application Notes:

https://devconnect.avaya.com/public/flink.do?f=/public/download/dyn/QuescomACM_H323.pdf

 

[pabxdude]

unfortunatley you cant have an LSP as the NE or FE of an IP Trunk.

if you changed it to a TDM trunk, this will overcome the issue.