Hi Stephane,
I just tried 2 simple case. I dialed the number 7057286882 which I know is a
disconnected number and I get the following:
> DL-DATA request
> Protocol Discriminator: Q.931 (8) len=9
> TEI=0 Call Ref: len= 2 (reference 4/0x4) (Sent from originator)
> Message Type: DISCONNECT (69)
TEI=0 Transmitting N(S)=12, window is open V(A)=12 K=7
> Protocol Discriminator: Q.931 (8) len=9
> TEI=0 Call Ref: len= 2 (reference 4/0x4) (Sent from originator)
> Message Type: DISCONNECT (69)
> [08 02 81 90]
> Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0
> Location: Private network serving the local user (1)
> Ext: 1 Cause: Normal Clearing (16), class = Normal Event
> (1) ]
-- Hungup 'DAHDI/1-1
-- Executing [failed@cadenceur:1] NoOp("OutgoingSpoolFailed", "REASON = 3")
in new stack
-- Executing [failed@cadenceur:2] NoOp("OutgoingSpoolFailed", "HANGUPCAUSE
= 0") in new stack
I also disabled my home answering maching and dialed my home number, letting
it ring and I got the following also:
> DL-DATA request
> Protocol Discriminator: Q.931 (8) len=9
> TEI=0 Call Ref: len= 2 (reference 5/0x5) (Sent from originator)
> Message Type: DISCONNECT (69)
TEI=0 Transmitting N(S)=15, window is open V(A)=15 K=7
> Protocol Discriminator: Q.931 (8) len=9
> TEI=0 Call Ref: len= 2 (reference 5/0x5) (Sent from originator)
> Message Type: DISCONNECT (69)
> [08 02 81 93]
> Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0
> Location: Private network serving the local user (1)
> Ext: 1 Cause: User alerting, no answer (19), class = Normal
> Event (1) ]
-- Hungup 'DAHDI/1-1
-- Executing [failed@cadenceur:1] NoOp("OutgoingSpoolFailed", "REASON = 3")
in new stack
-- Executing [failed@cadenceur:2] NoOp("OutgoingSpoolFailed", "HANGUPCAUSE
= 0") in new stack
It seems as the telco is sending the same response in both case. But the PRI
messages does indicate in the case of the real no answer a cause 19. But Is
that reflected in an asterisk variable somewhere ?
---
Andre Courchesne - Consultant
http://www.net-forces.com
MSN: [email protected]
Skype: VoipForces
L'information contenue dans le présent document est la propriété de Andre
Courchesne. Et est divulguée en toute confidentialité. Cette information ne
doit pas être utilisée, divulguée à d'autres personnes ou reproduite sans le
consentement écrit explicite de Andre Courchesne.
The information contained in this document is confidential and property of
Andre Courchesne. It shall not be used, disclosed to others or reproduced
without the express written consent of Andre Courchesne.
On 2011-06-06, at 11:16 AM, Stephan Monette wrote:
> Andre,
>
> Disconnect code 3 = No route to destination
>
> Look for a document called ISDN DISCONNECT CODE to find the explanation on
> all PRI-T1 disconnect code reasons.
>
> Thanks,
>
> Stephan Monette
> Unlimitel
>
> On 2011-06-06, at 11:10 AM, Andre Courchesne wrote:
>
>> Anyone on this ?
>>
>> ---
>> Andre Courchesne - Consultant
>> http://www.net-forces.com
>> MSN: [email protected]
>> Skype: VoipForces
>>
>>
>>
>> L'information contenue dans le présent document est la propriété de Andre
>> Courchesne. Et est divulguée en toute confidentialité. Cette information ne
>> doit pas être utilisée, divulguée à d'autres personnes ou reproduite sans le
>> consentement écrit explicite de Andre Courchesne.
>>
>> The information contained in this document is confidential and property of
>> Andre Courchesne. It shall not be used, disclosed to others or reproduced
>> without the express written consent of Andre Courchesne.
>>
>> On 2011-06-01, at 9:02 AM, Andre Courchesne wrote:
>>
>>> Hi all,
>>>
>>> I am working on an application that uses AMI Originate to generate a call
>>> which is sent to a context, all this is fine. This is a system connected to
>>> physical PRI circuits.
>>>
>>> However when doing an originate on a disconnected number, the call ends up
>>> in the failed extension (which is also fine), but with a ${REASON} = 3
>>> which according to the documentation I looked is a NoAnswer. Here is this
>>> section of the dialplan:
>>>
>>> exten => failed,1,GotoIf($["${REASON}" = "3"]?noanswer,1)
>>> exten => failed,n,GotoIf($["${REASON}" = "5"]?busy,1)
>>> exten => failed,n,GotoIf($["${REASON}" = "1"]?hangup,1)
>>> exten => failed,n,GotoIf($["${REASON}" = "8"]?congestion,1)
>>> exten => failed,n,GotoIf($["${REASON}" = "0"]?disconnected,1)
>>> exten => failed,n,Set(DialResult="failed_${REASON}")
>>> exten => failed,n,Hangup
>>>
>>> It seems like the telco is sending back a NoAnswer while at the same time
>>> playing the famous "The number you have reaches is no longer in service..."
>>> prompt.
>>>
>>> Anyone has any ideas how I could get the real failed result to properly
>>> identify those calls as disconnected numbers and not noanswers ?
>>>
>>> ---
>>> Andre Courchesne - Consultant
>>> http://www.net-forces.com
>>> MSN: [email protected]
>>> Skype: VoipForces
>>>
>>>
>>>
>>> L'information contenue dans le présent document est la propriété de Andre
>>> Courchesne. Et est divulguée en toute confidentialité. Cette information ne
>>> doit pas être utilisée, divulguée à d'autres personnes ou reproduite sans
>>> le consentement écrit explicite de Andre Courchesne.
>>>
>>> The information contained in this document is confidential and property of
>>> Andre Courchesne. It shall not be used, disclosed to others or reproduced
>>> without the express written consent of Andre Courchesne.
>>>
>>
>
