Avaya 7.6 SIP Rerouting on 'Unallocated Number' (404 Not Found)

[ipguru76]

Fair warning, first post for new member concerning really old equipment integration with new equipment.

We have an Avaya IP PBX (Migrated on Nortel CS1000 platform) running Avaya Release 7.6. Avaya is SIP Enabled and trunk endpoints configured for 2 separate Ribbon SBC Appliances (primary and secondary) for SIP PSTN and SIP Device endpoint (call boxes) communications.

We are successful at routing a call from the Avaya to the primary SBC for SIP phones that are registered locally on the primary SBC. However, we also have an alternate SBC for the SIP phones to register to as failover/load balancing.

The problem we have is that we need to have the Avaya PBX reroute calls when the response from the primary SBC is SIP/2.0 404 Not Found "Reason: Q.850;cause=1;text="Unallocated Number". This is an indication that the number being called is registered on the secondary SBC. Instead of the Avaya rerouting the call to the secondary SBC when this message is received, the call fails.

Is there a straightforward solution for having the Avaya attempt to reroute the call to the secondary SBC when it receives the NOT FOUND response from the primary SBC?

 

[biglebowski]

Can the devices dual register with both SBCs?

There is a CS1k forum here which may be a better place to ask this.

https://www.tek-tips.com/threadminder.cfm?pid=798

 

[bignose21]

If I understand what you are saying correctly the call hits the CS1000 and then forwards over SIP to the SBC, how is this setup Is the SIP trunks to the SBC's separate routes on the CS1000, or are you sending the calls on towards a Session Manager or NRS etc. that is making that decision for you?

 

[ipguru76]

I do not believe the devices can dual register. There are configurable with a Call Server address and an Alternative Call Server address, which acts as a failover only, as I understand it. The devices specifically are Viking call boxes.

 

[ipguru76]

bignose21. The call originates on an analog/digital extension that terminates on the CS1000. We are trying a few things with regards to routing, but currently we have equal cost routes configured for each SBC to be reached directly from the CS1000, no other systems in play. The trunks and routes work as expected, being as how we do see SIP requests from the CS1000 for the appropriate destination numbers.

I was hoping there was a way to configure and 'alternate' IP on the CS1000 side for the primary SBC, which would contain the IP of the secondary SBC.

 

[Wanebo]

You do not want to route directly from a CS100 to an SBC. Use system/Session Manager in between. There's even a special adaptation put out by Avaya to handle manipulating the headers.

 

[bignose21]

so if there is a session Manager in between and you want the CS1K to control the reroute for instance you could just add a prefix that the SM knows to route to the specific SBC

eg

call 1000 which is a TSC for example points to RLI 1

RLI 1
Entry 0
ROUT xx (sip Route to SM)
DMI 1 (inserts 8801 prefix for example)
SBOC rra (re route all)

Entry 1
ROUT xx (sip Route to SM)
DMI 2 (inserts 8802 prefix for example)

in SM point 8801 at SBC 1 and 8802 at SBC 2

OR

if you had say 1000 in the SM just point at SBC 1 rank 1 and SBC 2 as rank 2 does that not try both, if not is SBOC set to RRA in the RLI