Multiple carrier connectivity issue

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Multiple carrier connectivity issue

Postby Milky » Mon Sep 02, 2013 4:19 am

Can anyone please assist? I will be greatly appreciative is you can assist!
We are not able to activate more than one carrier at a time. :(

We can successfully run one campaign at a time through one carrier, with as many agents logged in on the below channels listed below 201 - 232.
We can also successfully run any other campaign through any other carrier, with as many agents logged in on the below channels listed below 201 - 232 if we copy the respective dial plan into the carrier and only make that carrier active.

However we can not make more than one carrier active at one time, as soon as we attempt to connect two or more carriers within the system all channels and carriers become unreachable (see below example).

We have read and reread the manual and all related forums and have tried and tested many variations to configuration but still can not resolve.

If you need any further information than what is outlined below please ask.


Our installation set up is as outlined below:

Asterisk 1.4.44-vici
ViciBox Server v.4.0
- ViciBox Redux v.4.0.3 released
Vicidial GUI - VERSION: 2.8-408a, BUILD: 130711-2208


2nd Server for call center pbx:
1x Mainboard Gigabyte GA-78LMT-USB3
1x CPU AMD FX-8350 4Ghz 8 core cpu
2x Storage Samsung 840 series 120GB SSD
2x Ram 8GB DDR3 ECC memory module
1x Case CS 17
1x PSU Coolermaster 500W 85% psu
1x Backplane - SNT2221sata 2x 2.5”
1x IBM Net Extreme 2 port, pci-e 4x ethernet card
1x Case filter 12cm filter + fan

Nothing else is running on this server and there isn't a firewall to be concerned with.

However interestingly (and frustratingly) in parallel we have a second server (intended as a prototype - as it's on a very low spec machine) but its set up with identical configuration of vicidial GUI (VERSION: 2.6-375a, BUILD: 120831-1523), but on a slightly older version of vicidial (ViciBox Server v.4.0! ViciBox Redux v.4.0.1) & but same Asterisk (Asterisk 1.4.44-vicidial) & openSUSE 12.1 "Asparagus" - Kernal 3.1.10-1.16-pae (tty1).
This has the identical carrier account and dialplan setup and functions correctly, allowing multiple carriers to be connected.
Successfully enables the running of multiple campaigns in parallel.
This parallel set up is on the same network and utilises the same router as the above outlined server.



Configuration Details:

Carrier 1.

Carrier ID: TESTDUN
Carrier Name: TESTDUN
Registration String: register=>username1:secretpassword@sip.carrier.co.nz/username1

Account Entry:
[TESTDUN]
type=friend
username=username1
fromuser=username1
secret=password
host=sip.carrier.co.nz
context=trunkinbound
dtmfmode=rfc2833
disallow=all
allow=ulaw
allow=gsm
nat=yes
canreinvite=no
nat=yes
canreinvite=no
insecure=invite,port


Protocol: SIP

Dialplan Entry:

exten => _5ZXXXXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _5ZXXX03250.*,2,Dial(SIP/${EXTEN:5:9}@TESTCHCH)
exten => _5ZXXX03425.*,2,Dial(SIP/${EXTEN:5:9}@TESTDUN)
exten => _5ZXXX.*,n,Hangup


Carrier 2.

Carrier ID: TESTCHCH
Carrier Name: TESTCHCH
Registration String: register=>username2:secretpassword@sip.carrier.co.nz/username2

Account Entry:
[TESTCHCH]
type=friend
username=username1
fromuser=username1
secret=password
host=sip.carrier.co.nz
context=trunkinbound
dtmfmode=rfc2833
disallow=all
allow=ulaw
allow=gsm
nat=yes
canreinvite=no
nat=yes
canreinvite=no
insecure=invite,port

Protocol: SIP


Asterisk read out of server failing.

Sip Show peers - showing successfully connection status with only one carrier activated, that can run one campaign on one carrier


Name/username Host Dyn Nat ACL Port Status
gs102/gs102 (Unspecified) D N 0 UNKNOWN
444/444 (Unspecified) D N 0 UNKNOWN
232/232 (Unspecified) D N 0 UNKNOWN
231/231 (Unspecified) D N 0 UNKNOWN
230/230 (Unspecified) D N 0 UNKNOWN
229/229 (Unspecified) D N 0 UNKNOWN
228/228 (Unspecified) D N 0 UNKNOWN
227/227 (Unspecified) D N 0 UNKNOWN
226/226 (Unspecified) D N 0 UNKNOWN
225/225 (Unspecified) D N 0 UNKNOWN
224/224 (Unspecified) D N 0 UNKNOWN
223/223 (Unspecified) D N 0 UNKNOWN
222/222 (Unspecified) D N 0 UNKNOWN
221/221 (Unspecified) D N 0 UNKNOWN
220/220 (Unspecified) D N 0 UNKNOWN
219/219 (Unspecified) D N 0 UNKNOWN
218/218 (Unspecified) D N 0 UNKNOWN
217/217 (Unspecified) D N 0 UNKNOWN
216/216 (Unspecified) D N 0 UNKNOWN
215/215 (Unspecified) D N 0 UNKNOWN
214/214 (Unspecified) D N 0 UNKNOWN
213/213 (Unspecified) D N 0 UNKNOWN
212/212 (Unspecified) D N 0 UNKNOWN
211/211 (Unspecified) D N 0 UNKNOWN
210/210 (Unspecified) D N 0 UNKNOWN
209/209 (Unspecified) D N 0 UNKNOWN
208/208 (Unspecified) D N 0 UNKNOWN
207/207 192.168.123.134 D N 40099 OK (104 ms)
206/206 (Unspecified) D N 0 UNKNOWN
205/205 (Unspecified) D N 0 UNKNOWN
204/204 (Unspecified) D N 0 UNKNOWN
203/203 (Unspecified) D N 0 UNKNOWN
202/202 (Unspecified) D N 0 UNKNOWN
201/201 (Unspecified) D N 0 UNKNOWN
TESTDUN/039291171 27.111.14.65 N 5060 OK (19 ms)
35 sip peers [Monitored: 2 online, 33 offline Unmonitored: 0 online, 0 offline]


CLI error messages with two carriers activated

vicibox1*CLI>

[Sep 2 19:58:03] NOTICE[2737]: chan_sip.c:8434 sip_reg_timeout: -- Registration for 'username1@sip.carrier.co.nz' timed out, trying again (Attempt #1)
[Sep 2 20:00:18] NOTICE[2737]: chan_sip.c:8434 sip_reg_timeout: -- Registration for 'username2@sip.carrier.co.nz' timed out, trying again (Attempt #2)

Sip Show peers - showing unsuccessfully connection status with two carriers activated


vicibox1*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
gs102/gs102 (Unspecified) D N 0 UNKNOWN
444/444 (Unspecified) D N 0 UNKNOWN
232/232 (Unspecified) D N 0 UNKNOWN
231/231 (Unspecified) D N 0 UNKNOWN
230/230 (Unspecified) D N 0 UNKNOWN
229/229 (Unspecified) D N 0 UNKNOWN
228/228 (Unspecified) D N 0 UNKNOWN
227/227 (Unspecified) D N 0 UNKNOWN
226/226 (Unspecified) D N 0 UNKNOWN
225/225 (Unspecified) D N 0 UNKNOWN
224/224 (Unspecified) D N 0 UNKNOWN
223/223 (Unspecified) D N 0 UNKNOWN
222/222 (Unspecified) D N 0 UNKNOWN
221/221 (Unspecified) D N 0 UNKNOWN
220/220 (Unspecified) D N 0 UNKNOWN
219/219 (Unspecified) D N 0 UNKNOWN
218/218 (Unspecified) D N 0 UNKNOWN
217/217 (Unspecified) D N 0 UNKNOWN
216/216 (Unspecified) D N 0 UNKNOWN
215/215 (Unspecified) D N 0 UNKNOWN
214/214 (Unspecified) D N 0 UNKNOWN
213/213 (Unspecified) D N 0 UNKNOWN
212/212 (Unspecified) D N 0 UNKNOWN
211/211 (Unspecified) D N 0 UNKNOWN
210/210 (Unspecified) D N 0 UNKNOWN
209/209 (Unspecified) D N 0 UNKNOWN
208/208 (Unspecified) D N 0 UNKNOWN
207/207 192.168.123.134 D N 40099 UNREACHABLE
206/206 (Unspecified) D N 0 UNKNOWN
205/205 (Unspecified) D N 0 UNKNOWN
204/204 (Unspecified) D N 0 UNKNOWN
203/203 (Unspecified) D N 0 UNKNOWN
202/202 (Unspecified) D N 0 UNKNOWN
201/201 (Unspecified) D N 0 UNKNOWN
TESTDUN/username1 27.111.14.65 N 5060 UNREACHABLE
TESTCHCH/username2 27.111.14.65 N 5060 UNREACHABLE
36 sip peers [Monitored: 0 online, 36 offline Unmonitored: 0 online, 0 offline]



vicibox1*CLI> sip set debug
SIP Debugging enabled
[Sep 2 20:08:34] REGISTER 11 headers, 0 lines
[Sep 2 20:08:34] Reliably Transmitting (NAT) to 27.111.14.65:5060:
REGISTER sip:sip.carrier.co.nz SIP/2.0
Via: SIP/2.0/UDP 202.160.51.126:5060;branch=z9hG4bK7c3863a9;rport
From: <sip:username2@sip.carrier.co.nz>;tag=as70818112
To: <sip:username2@sip.carrier.co.nz>
Call-ID: 39bad52005329f33081adbe52b007abc@192.168.123.50
CSeq: 109 REGISTER
User-Agent: Asterisk PBX
Max-Forwards: 70
Expires: 120
Contact: <sip:username2@202.160.51.126>
Event: registration
Content-Length: 0


---
[Sep 2 20:08:34] Retransmitting #1 (NAT) to 27.111.14.65:5060:
REGISTER sip:sip.carrier.co.nz SIP/2.0
Via: SIP/2.0/UDP 202.160.51.126:5060;branch=z9hG4bK7c90910c;rport
From: <sip:username1@sip.carrierco.nz>;tag=as2aba442d
To: <sip:username1@sip.carrier.co.nz>
Call-ID: 750a49bf71f9ae621deefd4d40189243@192.168.123.50
CSeq: 109 REGISTER
User-Agent: Asterisk PBX
Max-Forwards: 70
Expires: 120
Contact: <sip:username1@202.160.51.126>
Event: registration
Content-Length: 0


---
[Sep 2 20:08:34] Reliably Transmitting (NAT) to 192.168.123.134:40099:
OPTIONS sip:207@192.168.123.134:40099;rinstance=e6ce4db534bc8932;cpd=on SIP/2.0
Via: SIP/2.0/UDP 192.168.123.50:5060;branch=z9hG4bK7749061b;rport
From: "asterisk" <sip:asterisk@192.168.123.50>;tag=as1c3ad6b9
To: <sip:207@192.168.123.134:40099;rinstance=e6ce4db534bc8932;cpd=on>
Contact: <sip:asterisk@192.168.123.50>
Call-ID: 6ea6f9933e29b238432510fd65fb5cce@192.168.123.50
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Mon, 02 Sep 2013 08:08:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces
Content-Length: 0


---
[Sep 2 20:08:34] Reliably Transmitting (NAT) to 27.111.14.65:5060:
OPTIONS sip:sip.carrier.co.nz;cpd=on SIP/2.0
Via: SIP/2.0/UDP 202.160.51.126:5060;branch=z9hG4bK1e2ad6e1;rport
From: "asterisk" <sip:asterisk@202.160.51.126>;tag=as3c490308
To: <sip:sip.carrier.co.nz;cpd=on>
Contact: <sip:asterisk@202.160.51.126>
Call-ID: 0d150d992532ad15335699235281f941@202.160.51.126
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Mon, 02 Sep 2013 08:08:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces
Content-Length: 0


---
[Sep 2 20:08:34] Reliably Transmitting (NAT) to 27.111.14.65:5060:
OPTIONS sip:sip.carrier.co.nz;cpd=on SIP/2.0
Via: SIP/2.0/UDP 202.160.51.126:5060;branch=z9hG4bK5f592504;rport
From: "asterisk" <sip:asterisk@202.160.51.126>;tag=as2acfabfc
To: <sip:sip.carrier.co.nz;cpd=on>
Contact: <sip:asterisk@202.160.51.126>
Call-ID: 7c0bf2fc7575c4cb709f89853839d520@202.160.51.126
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Mon, 02 Sep 2013 08:08:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces
Content-Length: 0
Milky
 
Posts: 1
Joined: Mon Sep 02, 2013 4:12 am

Re: Multiple carrier connectivity issue

Postby DomeDan » Thu Sep 05, 2013 8:35 am

That's a strange issue..
I would run a diff on the config files, copy them from both the working test-server and the non-working
and do this:
diff -u asterisk_working_configs/ asterisk_non-working_configs/
then you can look at the differences and might find something you can try to change
Vicidial Partner. Region: Sweden/Norway.
Does Vicidial installation, configuration, customization, add-ons, CRM implementation, support, upgrading, network-related, pentesting etc. Remote and onsite assistance.
Email: domedan (at) gmail.com
DomeDan
 
Posts: 1226
Joined: Tue Jan 04, 2011 9:17 am
Location: Sweden


Return to Support

Who is online

Users browsing this forum: Bing [Bot] and 136 guests