I've been having problems with outgoing calls sent thru Vitelity for several weeks. I finally was able to narrow it down to their servers at ip 64.2.142.86 and 64.2.142.105. I can complete calls on their other two servers at ip 64.2.142.17 and 64.2.142.87. With sip debug on, I can see the invite going out, but never get a response. When the call timesout, I receive the following log:
[Feb 21 13:27:17] NOTICE[3869] chan_sip.c: Auto-congesting SIP/vitel-outbound-09f489b0
[Feb 21 13:27:17] VERBOSE[8600] logger.c: -- SIP/vitel-outbound-09f489b0 is circuit-busy
[Feb 21 13:27:17] VERBOSE[8600] logger.c: Reliably Transmitting (NAT) to 64.2.142.105:5060:
CANCEL sip:[email protected] SIP/2.0
If I set host=64.2.142.17 or host=64.2.142.87, then calls complete OK. I opened a ticket with Vitelity, but they cannot find anything wrong on their end and suggested that my ISP was blocking the two ip addresses. I can ping them OK.
Anyone having the same problem?
Ronw
[Feb 21 13:27:17] NOTICE[3869] chan_sip.c: Auto-congesting SIP/vitel-outbound-09f489b0
[Feb 21 13:27:17] VERBOSE[8600] logger.c: -- SIP/vitel-outbound-09f489b0 is circuit-busy
[Feb 21 13:27:17] VERBOSE[8600] logger.c: Reliably Transmitting (NAT) to 64.2.142.105:5060:
CANCEL sip:[email protected] SIP/2.0
If I set host=64.2.142.17 or host=64.2.142.87, then calls complete OK. I opened a ticket with Vitelity, but they cannot find anything wrong on their end and suggested that my ISP was blocking the two ip addresses. I can ping them OK.
Anyone having the same problem?
Ronw