vicidial.org

Hi,

I'm having a issue setting up the carrier SIP account on vicibox server. The SIP account is IP authenticated and below is the config of it.

Code: Select all

[voip]
disallow=all
allow=ulaw
allow=alaw
allow=g729
type=friend
user=red voip
from=123.456.789
host=123.456.789
dtmfmode=rfc2833
context=trunkinbound
qualify=yes
insecure=port,invite
nat=force_rport,comedia

It was working fine for the past few months and all of sudden due to some network issue the SIP account is not registering and if we check in sip show peers it is showing as UNREACHABLE since noon yesterday.

I have created the carrier with different name but still it is showing up as unreachable, also restarted the server multiple times and if I use the same config settings on different server. It is getting registered in no time.

I've checked with the carrier if they have blacklisted the IP and found it was issue from the dialer end.

If I setup a new voip account of another carrier (different IP) it is getting registered on this server.

What could be the issue & how can I resolve it ?

The server Installation is done through vicibox 8.0.1 svn version

VERSION: 2.14-661a
BUILD: 180222-0017
© 2018 ViciDial Group

Kindly help me resolve this issue.

Thank you

"qualify=yes" tells the system to send "checkup packets". If those packets do not make the round trip or do not make the trip quick enough, the carrier is marked UNREACHABLE and your diaplan is expected to fail over to a carrier that is still in service. This allows enterprise-level systems to automatically heal if there is a fault in an upline carrier. As of the moment the carrier is marked UNREACHABLE, asterisk will refuse to send any traffic to that sip account.

That being said: If you change to "qualify=no" this behavior will no longer occur. It will try to send the call to that carrier even if the carrier is "down" (since it has no idea whether it's down or not, it's no longer checking).

Next up: If the carrier was unreachable, it's likely that either the carrier is "down" or not accepting your connection or you have a firewall issue blocking your communications. Once you get rid of the qualify, you'll start sending calls and either get a response ... or not. But at least it'll show up in the CLI as an attempt and you can work it out from there.

Happy Hunting

Hi William,

Thanks for the reply.

If I put the qualify=no it is showing up as Unmonitored.

Yep. That's the expected result.

Can you guide me how to fix this Unmonitored issue ?

I recommend running either an ngrep or a tcpdump on your end, then open in Wireshark. This will show you exactly where the problem is. Here is a brief tutorial for tcpdump:
http://nil.uniza.sk/network-security/an ... diagnostic

If you have some SIP protocol knowledge, another easy and preferred way to troubleshoot this would be running the ngrep command. Ngrep tutorial:
http://nil.uniza.sk/sip/tools/ngrep-tool-voip-analysis

zenithbsolutions wrote:Can you guide me how to fix this Unmonitored issue ?

Unmonitored isn't an issue. Your issue is connectivity to your carrier. UNREACHABLE is an issue because it specifically states "I am not going to try to send a call to this server because of a previous failure". But "unmonitored" means nothing. The server will still try to send a call to the carrier. If that call FAILS you need to find out why it failed. Firewall on your end? Firewall on their end? You didn't pay the phone bill? You have the wrong IP or domain for the carrier?