Call forward on SIP failure

[FredisRed2]

We have a cordless phones in remote 24 hours facility connected to ATA's which are registered via SIP to an IP Office. We would like to set this up so incoming calls return busy tone if the cordless is in use. Which is working fine.

We would also like, if the SIP connection goes down, any calls automatically route to an external number.
It seems the problem is on SIP failure the IPO treats the extension as busy so I can’t seem to route a busy or SIP failure call differently.

It is release 9 & Voicemail Pro is available. Hoping there is a way.

 

[FredisRed2]

Sorry guys the first sentence above was supposed to read.
“We have cordless phones in remote 24 hour facilities connected to ATA's which are registered to an IP Office using SIP.”

 

[AACon]

I don't believe so; it would treat it like any other extension.

-Austin
ACE: Implement IP Office

 

[hairlessupportmonkey]

If the SIP connection goes offline, then you should be able to use the fallback extn in the ICR to do this for you

ACSS - SME
General Geek

 

[AvayaNACR]

What model ATA's are you using? We are looking at the same thing

For your problem, have you tried setting up a dummy extension forwarding that to your off PBX number? Then set the two up in a linear hunt group.

I have never tried it, but it seems like it should work.

Good luck

 

[amriddle01]

It follows the fallback when just busy though, there is no way to differentiate between busy and unregistered with the IP Office as far as call routing goes

 

[FredisRed2]

Thanks for your answers guys.

The ATA we are using is a Cisco SPA3102, with this model you can also connect a PSTN line so when registration fails the cordless can still dial out. And to top it off you can set dial plans so 000 (Emergency number for Australia) calls always route via PSTN, this allows the Emergency centre to automatically get the site address. Also, I believe (not setup yet) you can make dial plans for the PSTN so if you dial an extension number during SIP failure it will still work.

This PSTN line is where we wanted the external call to go when SIP fails, making each facility with full transparent inbound & outbound redundancy.

The closest I can get the divert on SIP failure to work is setting up a hunt group with the overflow timer pushed out. Then make the cordless a member & the overflow another hunt group with its member diverted to the PSTN. Then give out the hunt group number for users to call. We can also make the cordless ‘Ex Directory’ so users using the contact list are forced to dial the hunt group.

The only problem but still workable is the DSS button at Reception no longer rings the Extension when SIP registration fails.