Thanks Annus, Amit.
Yes, Amit, the plus sign in front is necessary. I was able to get this to
work by changing the codecs that the SIP trunk will use. I had to set up
wireshark on my Asterisk instance, gather that it didn't work for a 488 SIP
"No acceptable here" message, which led me to
Thanks for your quick responses, Annus.
As you can see, in my original post, I forward to context "from-external".
I forward to "from-twilio-remove-plus" only to check if
http://orourketech.com/elastix-plus-sign-caller-id-messing-things/ will
solve my problem. It did not. At no point do I point
Yes, I have tried that too (i.e, exten => +17775551212,1,Log(WARNING,
TWILIO)). It does not work and NO error message in CLI.
I have also tried
http://orourketech.com/elastix-plus-sign-caller-id-messing-things/ since I
first emailed this group, but that does not seem to work either.
Here is my
Hello,
try to change:
exten => 17775551212,1,Log(WARNING, TWILIO)
same => n,Hangup()
with:
exten => +17775551212,1,Log(WARNING, TWILIO)
same => n,Hangup()
Regards
--
_
-- Bandwidth and Colocation Provided by
Maybe is because now it's a different context:
from-twilio-remove-plus
before
from-internal
is right?
regards
El 02/12/2015 a las 10:22, Sonny Rajagopalan escribió:
Yes, I have tried that too (i.e, exten => +17775551212,1,Log(WARNING,
TWILIO)). It does not work and NO error message in CLI.
Hi
Your extensions.conf should have +17775551212 extension and not 17775551212
Add + sign before your number. This should solve your issue.
[from-external]
exten => +17775551212,1,Log(WARNING, TWILIO)
same => n,Hangup()
*Thanks & Regards,*
Amit Patkar
--
Hello,
I am running Asterisk 13.6.0 in an AWS instance, and I set it up with
Twilio SIP trunk using pjsip_wizard.conf (nice feature!). I see that the
calls actually "reach" the PBX, but for some reason, they are not caught by
any of my extensions context.
Here's what I observe when I test this
