IP Office 9.1.7 Server Edition SIP Options and Avaya SBCs

[NYSTECH]

Here is the setup.
IPO SE main server and Avaya SBC at one site and secondary server and Avaya SBC at Remote site.
If the connection to level 3 goes down on main SBC the secondary SBC is supposed to take over. works for inbound but not out bound. The trunk between the IPO main Sever and SBC does not see Level 3 connection go down and thus the calls fail because it does not route to Secondary server via the ARS pattern I have set up.
In looking at Monitor logs I do not see any Option messages coming from the IPO to SBCs but see them from SBCs to IPOs.

Has anyone else seen this? Maybe I am missing some setting. I saw some white paper mention this but not how it is fixed.
Some of them mention the Binder refresh time and also putting something in the no user tab but, neither seem to do anything.

Any help is appreciated..

 

[NYSTECH]

OK.

I now see the option going back and forth from IPO and SBC. I was not patient enough while doing the traces before. By default the options are sent every 300 seconds ( 5 Minutes). I have since shortened that.

The issue I have now is when the Public side of the SBC is down it sends either a 400 or 500 SIP message back to IPO but the IPO does not declare the Trunk between the SBC and IPO down so I can not use the ARS alternate rout to other Backup trunk to SBC for outbound calls. Is the IPO capable of knowing the link from the SBC to provider is down if not directly connected to provider?

 

[NYSTECH]

So just to follow up on my question.

If you have an SBC connected to a SIP provider and a trunk between the SBC and IPO, if the trunk between the provider and SBC goes down and IPO is getting a 440 or 500 error message from the SIP provider shouldn't it declare the SIP trunk between the SBC and IPO down? Or does the IPO only know the next available hope?

Any help would be appreciated.

 

[fendy3117]

Have you figured out the result? I cant remember, done this last 2 years. I configured IPO500v2 and ASBCE Portwell with 3 WAN links on Peplink to single SIP provider. The Options is relayed by the SBC from IPO to SIP provider, once the 1st trunk is Down, IPO route to the second trunk, using ARS and 3 SIP line pointing to the same ITSP address. And on the SBC I have to use 3 IP's on an interface, topology hiding for public IP translations and using profiles to link with each trunk in IPO. A bit complicated setup but it works. Found out the SBC doesn't do the failover for outbound call if using only one trunk between SBC and IPO.

 

[derfloh]

So three A1 IP addresses and three B1 IP addresses along with three public IPs?

 

[NYSTECH]

Opened a ticket with Avaya and was told that they are working on another case similar to what I described. I have to provide them with traces etc.. will update when I have anything. I am surprised that no one has run into this before.
I am also surprised that this would even be an issue.. You would think this is Basic SIP standards and the IPO would declare trunks down if the get the 400 or 500 error messages.
thanks for responses