Project

General

Profile

Forums » GOautodial Help »

Carrier not calling. No such extension/context. Goautodial V4

Added by Sotmir Laci almost 5 years ago

Hi,
i have configured 2 carriers in Goautodial 4, the first carrier is working very well in all campaigns, but the second configured carrier doesn't work at all and it is throwing this error in asterisk log :

NOTICE[22654]: core_local.c:756 local_call: No such extension/context 65300393497857850@default while calling Local channel

Here is the configuration of my second carrier:

Registration String
register => 011XXXXXXX:[email protected]:5060/011XXXXXXX

Account Entry

[BSS5368]
disallow=allow
allow=ulaw
type=friend
dtmfmode=rfc2833
qualify=yes
insecure=invite,port
nat=force_rport,comedia
host=XXX.XX.XXX.XXX
username=011XXXXXXXX
secret=Password
context=trunkinbound

Server IP/Host
127.0.0.1 - My GOautodial Server

Protocol
Sip

Global String
B555368 = SIP/011XXXXXXXX

Dialplan Entry
exten => _6530039.,1,AGI
exten => _6530039.,2,Dial(SIP/${EXTEN:3}@B555368,,tTo)
exten => _6530039.,3,Hangup

I am stuck in here ,if somebody can help i would really appreciate it.


Replies (2)

RE: Carrier not calling. No such extension/context. Goautodial V4 - Added by Sotmir Laci almost 5 years ago

I found that asterisk is not updating dialplan in:

/etc/asterisk/extensions-vicidial.conf

That's why carrier is not working.

In server settings i had already set this fields to yes

Generate Conf Files and Rebuild Conf Files

I don't understand why is not updating the dialplan?

RE: Carrier not calling. No such extension/context. Goautodial V4 - Added by Sotmir Laci almost 5 years ago

The cause of this issue was the missing crontab entries, all crontab entries were deleted and were injected a malicious bot script to run. Deleted the malicious script and inserted again all crontab entries, now it is working ok.
Issue Solved.

    (1-2/2)     Go to top