Re: [asterisk-users] Issues with Twilio number incoming call and context matching

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

[asterisk-users] e164.org dead ?

Hello, Does the ENUM service e164.org died? All queries that I do lead to "NXDOMAIN". I feel that the base has simply been empty for several months. Maybe some old addresses are still resolved, but the newer ones are not. The website still works, but it seems that everyone has left the plane,

Re: [asterisk-users] Issues with Twilio number incoming call and context matching

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

Re: [asterisk-users] Issues with Twilio number incoming call and context matching

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

Re: [asterisk-users] Issues with Twilio number incoming call and context matching

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.

[asterisk-users] Failed to authenticate device 100

Hello, I continued to see this errors in the logs: [2015-12-02 10:05:57] NOTICE[19949]: chan_sip.c:23277 handle_request_invite: Failed to authenticate device 100;tag=10cdeaf7 how do I guard against this kinds of attacks? Also, to get the IP address from where this

Re: [asterisk-users] Failed to authenticate device 100

The details of the source IP are available in the asterisk security log (if you have that enabled) – but that particular attack hides its address from the messages file. It’s essential that you secure your PBX; there are options ranging from free to commercial. Have a look at:

Re: [asterisk-users] Issues with Twilio number incoming call and context matching

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 --

[asterisk-users] Issues with Twilio number incoming call and context matching

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