Page 1 of 1

Inbound Call not Landing :

PostPosted: Tue Dec 10, 2013 6:34 am
by NileshM
Getting the following in SIP Debug. Out bound works fine.

Vicidial Redux Ver 5.0.2 -130821, Asterisk 1.8.23.0, Interl C2D/4GB/500GB, OpenSuse12.3, Firewall SonicWall, Ports 5060, 10000-25000 opened in firewall. PLEASE HELP!!!

[CMIB]
context=trunkinbound
host=sip.yyyy.yyy
type=peer
disallow=all
allow=ulaw
allow=g729
allow=gsm
insecure=port,invite
nat=yes



[Dec 10 16:02:44] No matching peer for '3012008686' from '46.19.209.14:5060'
<--- Reliably Transmitting (NAT) to 46.19.209.14:5060 --->
SIP/2.0 401 Unauthorized

Re: Inbound Call not Landing :

PostPosted: Sat Dec 21, 2013 4:23 pm
by williamconley
1) Welcome to the Party! 8-)

2) As you are obviously new here, I have some suggestions to help us all help you:

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 your installation is "Hosted" list the site name of the host.

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) Unauthorized means your user/pass is invalid, missing or worse. But this is not in any way related to the firewall. This is the same message you get from Paypal if you put in the wrong user/pass to log in "unauthorized". The only way to fix it is to get the RIGHT user/pass or remove the need for a user/pass entirely. (Many SIP carriers allow or require IP authentication ... so your IP may need to be added to your account's authorized IP address).