IPO 500 V2 - SIP 503 "service unavailable" for invalid numbers 1

[Rixy]

Hello All,

I've come up against a trivial but valid issue with a particular SIP provider. Due to the nature of their platform, we have to configure 2 SIP trunks to two different SIP gateways. Think of it as a primary and a secondary for outbound calls. AS such, the IPO has been configured with ARS routing to try one first, and then the other.

The scenario is, user dials an invalid number (unknowingly), and the IPO retunrs waiting for line to the users handset with 5 short beeps. it continues to do this for over 30 seconds, unfortunately i was not in a position to wait to see how long before it naturally timed out.

The SIP provider has run a trace for us and can see that the invalid number passes back a 503 reponse across their network.

Is anyone able to advise if there is a way in IPO to alleviate the "waiting for line" issue as it tries the two routes? or is it a case that provider needs to send some kind of null/invalid tone. If it's up to the provider, i'm up a certain creak without a paddle.

I also have a mitel system that experiences the same via the same provider, but just gives me a busy tone. Another mitel on another SIP provider gets invalid.

Anyone got any idea's

Thanks in advance.

Rixy

 

[Rixy]

Bumpy

 

[Rixy]

Sorry, to Add, it's running firmware level 8.1

 

[AACon]

As far as I know, it will only send calls to alternate routes when the primary route is out of service or unavailable. With SIP, it technically is "available", but the provider doesn't recognize it. It's the same thing that would happen with any line whether PRI/Analog/Tincan&String. If it's invalid, it's invalid. It doesn't mean the route is bad. I would just inform users to STOP DIALING WRONG NUMBERS and there is no issue

I suppose maybe the provider could just put the line out of service for you when people dial wrong numbers.


I gotta ask though, why the two lines from the same provider? They should be able to accept any *valid* number and route it accordingly.

-Austin
ACE: Implement IP Office

 

[Rixy]

Thanks AA,

The provider's SIP platform consists of two spereate peers from an external point of view. And they load balance on inbound calls between the 2 peers. so you have to program both on the system in order to catch all calls.

Unforutnately it's not ideal as you have to configure more on the PBX end, rather than just pointing the system to one Peer which does it's own failover on the providers network.

 

[amriddle01]

Sounds like you need a different/decent SIP provider



"No problem monkey socks