SIP trunk Configuration issue

All installation and configuration problems and questions

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

SIP trunk Configuration issue

Postby pargat » Wed Jul 29, 2015 7:54 am

Hi,

I have setup a brand new vicibox single server machine. The install went fine and the details of the config are:
ViciBox Redux v.6.0.3-141118, Asterisk 1.8.32.3-vici, VERSION: 2.12-485a, BUILD: 150512-2225
No additional hardware installed.

Agent and admin both interfaces working fine. able to login, hear you are the only agent in the conference.

The machine has got two IP interfaces, one to the Local LAN and the other is configured solely for the SIP trunk.
Issue is with the configuration of the SIP trunk.
Parameters provided by the service provider are as follows:
Allocation IP : 10.18.1.40/30
>- IP SBC Telkom : 10.18.1.41
>- IP Customer-EDP : 10.18.1.42
>- Codec : G711-Alaw, G711Ulaw, and T38 For FAX
>- Protocol SIP : SIP-UDP
>- Port SIP : 5060
>- DTMF use : RFC2833
>- Allocation Number : 02180644300 to 02180644399

My settings:

sip.conf
[SIPtrunk]
type=peer
host=10.18.1.41
dtmfmode=rfc2833
disallow=all
context=default
allow=ulaw
nat=yes

extensions.conf
[Globals]
SIPtrunk=SIP/10.18.1.41

[default]
exten => _9XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9XXXXXXXXXX,n,Set(CALLERID(all)="+622180644300" <+622180646300>)
exten => _9XXXXXXXXXX,n,Dial(SIP/10.18.1.41/${EXTEN:1},,rTt)
exten => _9XXXXXXXXXX,n,Hangup

traces from CLI for sip show peers and at time of call

vicidial*CLI> sip show peers
Name/username Host Dyn Forcerport ACL Port Status
8001/8001 172.25.71.180 D N 62143 OK (10 ms)
8002/8002 (Unspecified) D N 0 UNKNOWN
8003/8003 (Unspecified) D N 0 UNKNOWN
8004/8004 (Unspecified) D N 0 UNKNOWN
SIPtrunk 10.18.1.41 N 5060 OK (4 ms)
gs102/gs102 (Unspecified) D N 0 UNKNOWN

vicidial*CLI>
== Using SIP RTP CoS mark 5
-- Executing [90212523293@default:1] AGI("SIP/8001-0000000e", "agi://127.0.0.1:4577/call_log") in new stack
-- <SIP/8001-0000000e>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing [90212523293@default:2] Set("SIP/8001-0000000e", "CALLERID(all)="+622180644300" <+622180646300>") in new stack
-- Executing [90212523293@default:3] Dial("SIP/8001-0000000e", "SIP/10.18.1.41/0212523293,,rTt") in new stack
== Using SIP RTP CoS mark 5
-- Called SIP/10.18.1.41/0212523293
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Spawn extension (default, 90212523293, 3) exited non-zero on 'SIP/8001-0000000e'
-- Executing [h@default:1] AGI("SIP/8001-0000000e", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------") in new stack
-- <SIP/8001-0000000e>AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
vicidial*CLI>
vicidial*CLI>

Please suggest what changes I need to make to get this working. If it helps this SIP trunk is located in Indonesia.
pargat
 
Posts: 54
Joined: Mon Jun 20, 2011 4:25 am

Re: SIP trunk Configuration issue

Postby williamconley » Fri Aug 14, 2015 9:06 pm

Remove the callerid line from the carrier configuration.

Callerid is set at the Campaign and/or Phone. It is NOT to be set at the Carrier.

In most systems you can set the CallerID NUMBER in this way, but never the NAME and never ALL. In some systems you also can not set the NUMBER.

More to the point: You do not need to set it in this fashion anyway, as that is why there is a callerid field in each campaign. LOL

Technical detail in case it helps: Vicidial is very old software. It uses the CalleriD NAME field as a tracking variable. The calls are routed and "switched/bridged/masqueraded/etc" in many ways. The ONLY usable field that could be used to "permatrack" an individual call when this system was built was ... the CallerID NAME field because it is completely ignored by US Telcos. Discarded. So it is integral to the operation of the Vicidial backbone for tracking and controlling calls.

8-)
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20258
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: SIP trunk Configuration issue

Postby boybawang » Sun Aug 16, 2015 7:26 am

Your dialplan seems correct, you can actually set the caller id on the campaign itself but you can also set that on the dialplan which works all the time but you would have to use that on that campaign specifically, now basing on the logs you have sent the call went through the sip server which is 10.18.1.41 (as you configured it), if the calls didnt go through then you would have to check that servers log files on why the call didnt go through.
Vicidial Installation + Configuration + Support + Custom Development
Download my ebook on installing vicidial for free http://download.vicidial.com/ubuntu/VIC ... 100331.pdf
skype: deodax.cordova@gmail.com
m: +639172063730
boybawang
 
Posts: 989
Joined: Sat Nov 14, 2009 1:18 pm
Location: Dumaguete City, Negros Oriental, Philippines

Re: SIP trunk Configuration issue

Postby williamconley » Thu Aug 27, 2015 9:57 pm

boybawang wrote:Your dialplan seems correct, you can actually set the caller id on the campaign itself but you can also set that on the dialplan which works all the time ...
Not true. Setting the callerid NAME breaks Vicidial. Test it. 8-)

You can (usually) set the callerid NUM, but never the NAME. And if you use the command that sets BOTH ( Set(CALLERID(all)= ), you've set NAME and broken Vicidial.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20258
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)


Return to Support

Who is online

Users browsing this forum: Google [Bot] and 118 guests