Hello,
I wrote earlier today about a new PRI installation in the Caribbean,
where all outbound calls are functioning fine *except* calls to Sprint
phone numbers, which get rejected immediately as "busy".
The telco has been working with their switch manufacturer and took the
output of "pri show span 1" from me and came back with this:
----quote---
Please check your timers below. How did you determine your settings?
* Timer and counter settings:
N200: 3
N202: 3
K: 7
T200: 1000
T201: 1000
T202: 2000
T203: 10000
T303: 4000
T305: 30000
T308: 4000
T309: 6000 Our switch: Telcordia National ISDN 2: Range 10 - 90
seconds, default 90 seconds.
*
T312: 6000
T313: 4000
T316: -1 Our switch: Telcordia National ISDN 2: Range 10 -
120 seconds, default 30 seconds.
N316: 2
T-HOLD: 4000
T-RETRIEVE: 4000
T-RESPONSE: 4000
---end quote---
Now I have no idea what T309 or T316 represent, but it seems odd that
timers and counters would cause such an odd result... and the failure is
immediate, not after some amount of timeout. Can anyone shed light on
these settings and tell me if they are configurable?
Cheers,
j
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20140819/146313bd/attachment.html>
Doubtful that T309 or T316 are causing the problem, but you can always change them to correspond with their defaults. http://www.nmscommunications.com/manuals/6272-16/appendxe.htm --Don From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Jeff LaCoursiere Sent: Tuesday, August 19, 2014 4:56 PM To: asterisk-users at lists.digium.com >> Asterisk Users Mailing List - Non-Commercial Discussion Subject: [asterisk-users] PRI timing settings Hello, I wrote earlier today about a new PRI installation in the Caribbean, where all outbound calls are functioning fine *except* calls to Sprint phone numbers, which get rejected immediately as "busy". The telco has been working with their switch manufacturer and took the output of "pri show span 1" from me and came back with this: ----quote--- Please check your timers below. How did you determine your settings? * Timer and counter settings: N200: 3 N202: 3 K: 7 T200: 1000 T201: 1000 T202: 2000 T203: 10000 T303: 4000 T305: 30000 T308: 4000 T309: 6000 Our switch: Telcordia National ISDN 2: Range 10 - 90 seconds, default 90 seconds. * T312: 6000 T313: 4000 T316: -1 Our switch: Telcordia National ISDN 2: Range 10 - 120 seconds, default 30 seconds. N316: 2 T-HOLD: 4000 T-RETRIEVE: 4000 T-RESPONSE: 4000 ---end quote--- Now I have no idea what T309 or T316 represent, but it seems odd that timers and counters would cause such an odd result... and the failure is immediate, not after some amount of timeout. Can anyone shed light on these settings and tell me if they are configurable? Cheers, j -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20140819/8c69316d/attachment.html>
On 2014-08-19 23:56, Jeff LaCoursiere wrote:> Hello, > > I wrote earlier today about a new PRI installation in the Caribbean, where all outbound calls are functioning fine *except* calls to Sprint phone numbers, which get rejected immediately as "busy". > > The telco has been working with their switch manufacturer and took the output of "pri show span 1" from me and came back with this: > > ----quote--- > > Please check your timers below. How did you determine your settings? > > * Timer and counter settings: > N200: 3 > N202: 3 > K: 7 > T200: 1000 > T201: 1000 > T202: 2000 > T203: 10000 > T303: 4000 > T305: 30000 > T308: 4000 > T309: 6000 Our switch: Telcordia National ISDN 2: Range 10 - 90 seconds, default 90 seconds. > > * > > > T312: 6000 > T313: 4000 > T316: -1 Our switch: Telcordia National ISDN 2: Range 10 - 120 seconds, default 30 seconds. > > > N316: 2 > T-HOLD: 4000 > T-RETRIEVE: 4000 > T-RESPONSE: 4000 > > ---end quote--- > > > Now I have no idea what T309 or T316 represent, but it seems odd that timers and counters would cause such an odd result... and the failure is immediate, not after some amount of timeout. Can anyone > shed light on these settings and tell me if they are configurable? >I don't think that this has something to do with the timers. I recommend to enable debug of your pri connection to get a trace to a sprint phone number. There you should get the disconnect cause of the call. Then your provider should be able to help you out. Maybe the reason of the problem is an incorrect number setting. Regards Hans
On Aug 19, 2014, at 5:56 PM, Jeff LaCoursiere <jeff at jeff.net<mailto:jeff at jeff.net>> wrote: I wrote earlier today about a new PRI installation in the Caribbean, where all outbound calls are functioning fine *except* calls to Sprint phone numbers, which get rejected immediately as "busy". I don?t know what expectations for CLID your carrier might have, or for that matter the upstream carrier, however, we found through our CLEC here in the US that while the CLEC was happy to take e.164 formatted numbers from us as CLID, Global Crossing would reject them further upstream resulting in our calls to many toll frees being rejected. Switching to 10 digit CLID on all outbound calls through that PRI solved the problem. I don?t know if this is your problem but be sure your CLID is in the most simple format possible for your region to help rule it out. sl -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20140820/c5e95c92/attachment.html>