![]() ![]() X-Twilio-Error: 32202 Authentication failure - bad user credentials. I tried to make a tcpdumpo when I make a call, and two things come up:ġ) Instead of showing the external ip (34.233.200.60), it shows the internal amazon one: 172.31.27.253Ģ) "Authentication failure - bad user credentials" seems pretty clear per-se, but I triple checked the account and password but it is still coming upģ) On Twilio I added the both internal and external ip to the list of authorized IPs, termination and origination, but still no luck IP 54.172.60.0.sip > 172.31.27.253.sip: UDP, length tag=43545804_6772d868_5ca9a156-c7de-4ef5-93e1-f5846a68b2fb In addition, I have no fail2ban, no iptable on, it's just failing Services like Twilio provide gateway SMS services, where we contact them via an HTTP REST API and they handle the SMS sending for. There is also an additional perplexity on why I see chan_sip.c, even if I fully configured the nf, is it normal? Sending SMS messages to countries where Twilio numbers arent available. NOTICE chan_sip.c: Peer 'twilio2' is now UNREACHABLE! Last qualify: 0 NOTICE chan_sip.c: Peer 'twilio3' is now UNREACHABLE! Last qualify: 0 NOTICE chan_sip.c: Peer 'twilio0' is now UNREACHABLE! Last qualify: 0 NOTICE chan_sip.c: Peer 'twilio1' is now UNREACHABLE! Last qualify: 0 ![]() NOTICE chan_sip.c: Peer 'twilio6' is now UNREACHABLE! Last qualify: 0 NOTICE chan_sip.c: Peer 'twilio4' is now UNREACHABLE! Last qualify: 0 The problem is that at the moment of the call the twilio servers are said UNREACHABLE by Asterisk, even if the machine can ping them perfectly NOTICE chan_sip.c: Peer 'twilio5' is now UNREACHABLE! Last qualify: 0 Twilio offers a great guide for the Asterisk users, and I followed it step by step ( ) ![]()
0 Comments
Leave a Reply. |