Project

General

Profile

Forums » GOautodial Help »

invalid extension when making a call

Added by Jumbz Tayamen over 11 years ago

Parsing '/etc/asterisk/manager.conf': Found
Manager 'sendcron' logged on from 127.0.0.1
-- Executing [8600051@default:1] MeetMe("Local/8600051@default-297b,2", "8600051|F") in new stack
> Channel Local/8600051@default-297b,1 was answered.
Starting Local/8600051@default-297b,1 at default,3in_file6509198872,1 failed so falling back to exten 's'
Starting Local/8600051@default-297b,1 at default,s,1 still failed so falling back to context 'default'
-- Sent into invalid extension 's' in context 'default' on Local/8600051@default-297b,1
-- Executing [i@default:1] Playback("Local/8600051@default-297b,1", "invalid") in new stack
Manager 'sendcron' logged off from 127.0.0.1
-- <Local/8600051@default-297b,1> Playing 'invalid' (language 'en')
[Jul 25 16:43:46] WARNING19086: file.c:1297 waitstream_core: Unexpected control subclass '-1'
[Jul 25 16:43:46] WARNING19086: file.c:1297 waitstream_core: Unexpected control subclass '-1' == Auto fallthrough, channel 'Local/8600051@default-297b,1' status is 'UNKNOWN'
-- Executing [h@default:1] DeadAGI("Local/8600051@default-297b,1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack

goautodial ce 3.0 rc1b updated via yum.

no custom dialplans/extensions.

my carrier dial plan:

exten => _3XXXXXXXXXX,1,AGI
exten => _3XXXXXXXXXX,2,Dial(SIP/2${EXTEN}@provider,,ToR)
exten => _3XXXXXXXXXX,3,Hangup

cant run in either manual or predictive. A direct call via sip phone can pass through and connect when dialling +31(XXX)XXX-XXXX
in an agent's screen, manually entering a phone number (xxx)xxx-xxxx does not connect as well.

any ideas?


Replies (2)

RE: invalid extension when making a call - Added by Levy Ryan Nolasco over 11 years ago

Hi Jumbz,

Good day! You can try adjusting the Campaign settings "Carrier to use for this Campaign: Custom Dial Prefix then input 3 or 31". Test which of the 2 prefix works with you.

Regards,
Ryan

RE: invalid extension when making a call - Added by Jumbz Tayamen over 11 years ago

It was a dialplan error. I still dont know what was causing the extension to be dialed as that of the dialed number (in bold) but declaring the carrier in the default context and adding the sip provider's ip directly:

Sip/12.34.56.78/${exten:1} as such solved my dialing issue.

Now running predictive for 60 seats.

Question is, how come with the same settings and configuration, this setup is having errors on amd hardware vs on intel?

    (1-2/2)     Go to top