Page 1 of 1

Is there something wrong with my dial plan entry?

PostPosted: Tue Jan 24, 2012 11:24 am
by slayer090
I got here a problem. If I register at my softphone directly I can made a call, but when I dial thru our vicidial, I am getting an error Call Failed: Not Found. and at the asterisk logs Chanunavalable.

[microtalk]
username=username
secret=secret
disallow=all
allow=ulaw
allow=alaw
context=default
type=peer
host=91.220.132.10
dtmfmode=rfc2833


exten => _X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _X.,2,Dial(${MTTRUNK}/${EXTEN},55,Totr)
exten => _X.,3,Hangup


Thank you in advance.

PostPosted: Wed Jan 25, 2012 5:36 am
by boybawang
do you have MTTRUNK = SIP/microtalk

PostPosted: Wed Jan 25, 2012 5:49 am
by slayer090
Yes I have. Its on the global string.

cli output

PostPosted: Sat Jan 28, 2012 7:39 am
by striker
post the cli result for a single call
also check these commands
sip show peers
sip show registry

PostPosted: Sun Jan 29, 2012 12:08 am
by williamconley
1) Welcome to the party! 8-)

2) when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Post your entire carrier setup, not just pieces of it, and post a single failed call's asterisk CLI. Ask directions if you don't know how.

4) Avoid "X.", it's lazy and leads to problems. Use an extension that accurately describes your calling country AND allows for a dial prefix to identify your carrier so you can add new carriers later.

5) Please use the Vicidial Manager's Manual as referenced above to set up your system for the first time. Beginning to end, don't skip anything. Makes life much simpler (and you often get to keep much more of your hair). When you hit your first pothole, tell us the page and line of the manual and the error you see (precisely) and we'll help you get past it. ;)

Re: Is there something wrong with my dial plan entry?

PostPosted: Wed Jun 27, 2012 1:49 pm
by termite
Got the same issue with microtalk too.. i even tested it on my asterisk test server and it still fails.. but if I use a softphone I can make calls.. very puzzling!!! :? :? :?

Re: Is there something wrong with my dial plan entry?

PostPosted: Wed Jun 27, 2012 2:28 pm
by beghins
have you change in to vicidial campagn dial prefix= "white" because default is "9" if you change
from

xten => _X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _X.,2,Dial(${MTTRUNK}/${EXTEN},55,Totr)
exten => _X.,3,Hangup
to

xten => _9.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9.,2,Dial(${MTTRUNK}/${EXTEN},55,Totr)
exten => _9.,3,Hangup

Vicidial use this extensions

Re: Is there something wrong with my dial plan entry?

PostPosted: Sat Jun 30, 2012 7:04 am
by fibres
It could be that Microtalk do not allow asterisk trunks to register to their service. Have you spoken to them about this?

A post of your call_log would be helpful of the calls failing to check for this.

Also try adding the following to the globals section of your sip.conf on the server

useragent = Firefly

make sure you reload asterisk after making the change. This can make the carrier think your using a softphone and not asterisk.

If this change works then the provider does not support asterisk. This is not advised to be used as a permanent solution as you may well be in breach of your carriers t&c's.

Regards