Sip Issue

[shadow181]

HI

We have been installing SIP trunks for our clients and have come across an unexpected issue.
Callers get a message that the # is not in service when all channels are full.
The carrier is telling us that we require them to supply us with an additional channel in order to get a busy signal.
IE. we have 4 channels allocated in our switch for the SIP Trunk, they say we require to order a 5th from them to get a busy.
I have tested this by allocating 3 channels on this trunk and the 4th call does get a busy.
Is this common that we require ordering 1 additional channel from the the carrier then required in order to get a busy signal?

Any suggestions would be helpful..

Thanks,

 

[AACon]

That honestly sounds a bit odd. If all channels are busy, they really should supply the tone from their end, to the caller.

-Austin
ACE: Implement IP Office

 

[atcom]

Caller's should definitely get a busy signal when the call cannot get through either due to congestion (no available channels) or when the PBX is unavailable.

-----------------------------------

Calgary Telephone Systems, Avaya LG Asterisk (FreePBX) VOIP & TDM

 

[Bas1234]

This is a know issue and solved soon.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[tlpeter]

Bas, can you tell me more?
Does the IPO send a 503 instead of a 486?
When this is the case then this happened before (more then two years ago as i had Intrigrant over in my first week for my current company.


BAZINGA!

I'm not insane, my mother had me tested!

 

[Bas1234]

tlpeter, R9 see the sip trunk on the right side.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[Bas1234]

Ipo send a 503, if you add an extra license and leave the channels like they are the problem is solved, in r9 you can choose to respond with a 503 or a 486 busy here

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[tlpeter]

I know the 486 in R9 but i have seen this bug before.


BAZINGA!

I'm not insane, my mother had me tested!

 

[Bas1234]

Avaya says it's not a bug but work as designed...my @$$ but for r9 its finally an option.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[tlpeter]

Bas, it is a bug and they piss me of with this and i think intrigrant still remembers this one.
When i order 10 channels (licenses) then i should not need an 11th unused channel just for a busy notification.


BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

When they can't fix something they say design intent, even though it clearly isn't and would serve no purpose to design it that way....sometimes they are just plain bell ends



"No problem monkey socks

 

[Bas1234]

I wrote NFR on 8.0 and 8.1 but never got a decent answer.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[tlpeter]

Bas, i think i found it and this is the the CQ :CQ107301
It was a 404 and it should give a 486.
A 503 would happen when you have less channels configured than licenses but nobody does do that.
This is solved in 6.1.12:

CQ107301
Response Code 404 (Not Found ) should not be returned when the Manager Help states that the IP Office returns “busy”

Somehow i noticed this bug in 7.0.5 bug vanished somewhere in 7.0




BAZINGA!

I'm not insane, my mother had me tested!

 

[Bas1234]

I thought that was in R6.1 also but i can be mistaken.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[intrigrant]

I have raised this once as a bug and I agree with Avaya, it is not a bug it is a misconfiguration in IP Office.
If you use only one URI then it works as expected, if you have more URI's then this error occurs.
In the case I raised the case the SIP line had to have a URI for each DDI number as each DDI number has its own login credentials.
In order to have four channels for each DDI I created multiple URI's with four channels and the problem arise if the provider allows more incoming channels as ordered.
If four channels are busy and a fifth call comes in then the call is rejected not because all channels are busy but because there is no license available and thus responding with a 503 "Service Unavailable" message. Adding a license allows the call to be answered but it only puts the problem forward, if five channels are busy the sixth caller gets a 503 message etc. until all VCM channels are occupied, only then the IPO generate a 503 message.
As Avaya claims this is not a supported way of working as documented in the SIP RFC's and so it is a providers problem( I could'nt find the document so they send it and I lost it when changing jobs, @BAS1234 maybe it is on your server somewhere.
There should be only one URI on each SIP trunk. In rel 9 you can replace the 503 message with a 486 message were the caller gets a busy tone, which is more acceptable.
In the latest releases you can have multiple SIP trunks to the same providers IP Address using DNS shuffling but it is not easy to deploy and I don't reccomend it.

Know your product and become a Pro

 

[Bas1234]

I will have a look on the sever if i'll find it and they didn't solve it for 8.1 for the next release i'll try it another time but don't think they will have a solution then. I think they could easily create a NoUser string for it but it could be me.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[intrigrant]

Yes they can but they don't. As so often.....

Know your product and become a Pro

 

[amriddle01]

They should simply allow 0 channel URIs for incoming matching or even more sensibly in the absence of a matching user/group URI the system checks incoming call route....easy



"No problem monkey socks