vicidial.org

Hi,
I'm just a new member here and is also quite new with vicidial administration. I did a lot of research about how to configure in youtube and happened to get my vicidial server working. My dialer is working fine for a couple of weeks until our firewall's primary WAN goes offline and our failover WAN kicks in. I still get incoming calls to my dialer but this time they don't hear any audio at all. I checked my firewall's configuration on the RTP ports and all are configured correctly and I even forced all RTP and SIP port forwarding to our secondary WAN and still get the same error. Any idea on what to do? Please need your help. I noticed this error on vicidial.

[Aug 19 23:49:36] -- Executing [8600051@default:1] MeetMe("SIP/apeiron-000000af", "8600051,F") in new stack
[Aug 19 23:49:49] WARNING[2445]: chan_sip.c:4151 retrans_pkt: Retransmission timeout reached on transmission 2781932625-0-4186921980@66.85.57.9 for seqno 1 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/ ... nsmissions
Packet timed out after 15104ms with no response
[Aug 19 23:49:49] WARNING[2445]: chan_sip.c:4190 retrans_pkt: Hanging up call 2781932625-0-4186921980@66.85.57.9 - no reply to our critical packet (see https://wiki.asterisk.org/wiki/display/ ... nsmissions).

vicidial version 2.14-917a
build:240516-1720
2024 vicidial group


Thank you.

first off, edit out your IP, second these messages are typically from sip attacks, are you using vicibox? what are your firewall settings?

Are you referring to this settings in sip.conf file?

bindaddr=0.0.0.0 or
externip - this is currently set to our primary WAN ip address when I check

Would updating the externip to our secondary WAN ip address (failover) solve the retransmission problem when our failover WAN kicks in?

Yes I'm using vicibox_v11.x86_64-11.0.1.iso installer

Firewall settings are configured for both primary and failover wan (port forwarding for sip and rtp ports), once our primary WAN went back online everything went back smooth, its just when its offline and the failover WAN kicks in there is no audio but incoming calls are still coming in, connection to our voip provider still ok.

i meant posting your server IP above in your first post, there are people that look here with ill intentions. What is allowed in your public zone?

I understand, our vicibox built in firewall (suse) is disabled. We have a different firewall and this vicibox is behind this firewall via nat. Only ports 5060 and rtp ports are allowed coming in vicibox thru port port forwarding. All connections from vicibox going out the internet is allowed.

Can the externip option in sip.conf file configured with the 0.0.0.0 ip address same as the bindaddr so that whenever there is downtime it will switch using the secondory wan ip address?

yes it can

appie_lgk2024 wrote:I understand, our vicibox built in firewall (suse) is disabled. We have a different firewall and this vicibox is behind this firewall via nat. Only ports 5060 and rtp ports are allowed coming in vicibox thru port port forwarding. All connections from vicibox going out the internet is allowed.

Can the externip option in sip.conf file configured with the 0.0.0.0 ip address same as the bindaddr so that whenever there is downtime it will switch using the secondory wan ip address?

If the bindaddr is using the Public IP from the active WAN port, then yes. externip must be the PUBLIC IP to which the SIP protocol sends your audio packets (cuz that's where they're going: even if that's not YOU, which causes audio to fail). LOL. So setting externip manually or automatically and reloading asterisk's configuration is necessary whenever your public IP changes.

Sorry for the very late reply, I set the externip option to the active WAN ip address (during failover) and it solved the problem.
Thank you!