Hi all,
I have just successfully created a trunk in Asterisk with Chan_Mobile, I mean than I am using a bluetooth dongle on my asterisk pc, connected to an old mobile phone and calls work perfectly in and out !
But unfortunatly everything is not so nice…
When the phone looses signal, or if for whichever reason the call does not go through and the trunk replies its unavailability to Asterisk, then the call just drops, and for those outbounds routes that go firt on this trunk, no way to make any call…
So I was wondering… did I miss something ?
mobile.conf is like that :
[adapter]
id=dlink
address=00:0A:84:00:07:37
[Samsung-GT-S5670]
address=6C:83:36:49:8F:B7
port=1
context=from-Samsung-GT-S5670
adapter=dlink
group= 1
My trunk is a custom trunk with only a dial rule like this :
Mobile/Samsung-GT-S5670/$OUTNUM$
and my extensions.conf does include this :
[from-Samsung-GT-S5670]
exten => s,1,Noop(Entering macro-from-Samsung-GT-S5670 with DID = ${DID} and setting to: 3112460066)
exten => s,n,Set(__FROM_DID=3112460066)
exten => s,n,Goto(from-trunk,3112460066,1)
exten => s,h,Hangup
I was thinking, (I am a newbie) , maybe something is missing in the extensions.conf to tell ASterisk not to “Hangup” if the “Goto” the trunk fails, but fallback to the next trunk in the list…
Or maybe the whole extensions.conf section I added is useless for what I need ?
I followed a tutorial to reach this, but please help me solve this last part to allow calls going through that trunk follow the logical order of my outbound rules in case of failure.
Thanks in advance
PS : I edited the title to make it more generic because I found out that I have this problem also with my google voice trunk, but it is much more rare to detect the issue with this trunk as it is almost always working, but if I invert my outbound routes, cut off my internet, and put google voice as first outbound route, the outbound call (that try to go though google) will never fallback to the Chan_mobile trunk), so this is a generic problem of a Trunk fallback. I will add the traces in the next reply.