Outbound Call fails using call files in Asterisk 1.6

Hi all,

I am using Asterisk 1.6.2.13, dahdi-linux-complete-2.4.0+2.4.0, libpri-1.4.10 on Centos 5.2
our first PRI is outbound and is dialing properly when dial command is used from inside AGI script or dialplan.

my problem is that after installing asterisk, I was able to make calls using .call files, but after a couple of weeks later I suddenly found that call was not being dialed using .call files. i use following call file

Channel: DAHDI/g1/0323xxxxxxx
Application: AGI
Data: myagiscript.agi

here is the debug trace of CLI.

– Attempting call on DAHDI/g1/0323xxxxxxx for application AGI(myagiscript.agi) (Retry 1)
– Making new call for cr 35192
– Requested transfer capability: 0x00 - SPEECH

Protocol Discriminator: Q.931 (8) len=34
Call Ref: len= 2 (reference 2424/0x978) (Originator)
Message type: SETUP (5)
[04 03 80 90 a3]
Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Speech (0)
Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16)
User information layer 1: A-Law (35)
[18 03 a1 83 81]
Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Preferred Dchan: 0
ChanSel: As indicated in following octets
Ext: 1 Coding: 0 Number Specified Channel Type: 3
Ext: 1 Channel: 1 ]
[6c 02 21 81]
Calling Number (len= 4) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)
Presentation: Presentation permitted, user number passed network screening (1) ‘’ ]
[70 0c a1 30 33 32 33 32 33 39 33 37 38 38]
Called Number (len=14) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) ‘0323xxxxxxx’ ]
[a1]
Sending Complete (len= 1)
q931.c:3134 q931_setup: call 35192 on channel 1 enters state 1 (Call Initiated)
< Protocol Discriminator: Q.931 (8) len=10
< Call Ref: len= 2 (reference 2424/0x978) (Terminator)
< Message type: CALL PROCEEDING (2)
< [18 03 a9 83 81]
< Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan: 0
< ChanSel: As indicated in following octets
< Ext: 1 Coding: 0 Number Specified Channel Type: 3
< Ext: 1 Channel: 1 ]
– Processing IE 24 (cs0, Channel Identification)
q931.c:3683 q931_receive: call 35192 on channel 1 enters state 3 (Outgoing call Proceeding)
< Protocol Discriminator: Q.931 (8) len=9
< Call Ref: len= 2 (reference 2424/0x978) (Terminator)
< Message type: ALERTING (1)
< [1e 02 84 88]
< Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Public network serving the remote user (4)
< Ext: 1 Progress Description: Inband information or appropriate pattern now available. (8) ]
– Processing IE 30 (cs0, Progress Indicator)
q931.c:3596 q931_receive: call 35192 on channel 1 enters state 4 (Call Delivered)
< Protocol Discriminator: Q.931 (8) len=9
< Call Ref: len= 2 (reference 2424/0x978) (Terminator)
< Message type: DISCONNECT (69)
< [08 02 80 9f]
< Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0 Location: User (0)
< Ext: 1 Cause: Normal, unspecified (31), class = Normal Event (1) ]
– Processing IE 8 (cs0, Cause)
q931.c:3826 q931_receive: call 35192 on channel 1 enters state 12 (Disconnect Indication)
– Channel 0/1, span 1 got hangup request, cause 31
NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Disconnect Indication, peerstate Disconnect Request
q931.c:2967 q931_release: call 35192 on channel 1 enters state 19 (Release Request)
Protocol Discriminator: Q.931 (8) len=9
Call Ref: len= 2 (reference 2424/0x978) (Originator)
Message type: RELEASE (77)
[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’
[Nov 22 15:24:27] NOTICE[26946]: pbx_spool.c:339 attempt_thread: Call failed to go through, reason (1) Hangup
< Protocol Discriminator: Q.931 (8) len=5
< Call Ref: len= 2 (reference 2424/0x978) (Terminator)
< Message type: RELEASE COMPLETE (90)
q931.c:3766 q931_receive: call 35192 on channel 1 enters state 0 (Null)
NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null
NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null

any help will be highly appreciated.

thanks and regards,
Javaid
Software engineer
Axvoice Inc.

The call was to a valid number but wasn’t answered.

As an observation, you have type of number = national, but you are sending an initial zero. If the zero is the bit that indicates a national number is being dialled, I wouldn’t expect it to be included with that type of number.

Hi,

0 is the part of area code of another city to which i am dialing. this same number is dialed properly when using Dial() in dialplan or AGI. It was also working perfectly through call files but all of a sudden it stopped working. I basically have same asterisk setup on 6 servers and 4 of them are able to dial this number via call files.