Page 1 of 1

Inbound issues

PostPosted: Sat Mar 15, 2014 10:32 am
by udfxrookie
Outbound works perfect, inbound not so much...
We have several DIDs with one company.
I have setup a carrier:
[DIDHostName]
host=DIDHostIP
type=friend
insecure=port,invite
context=trunkinbound

DialPlan Entry:
exten => _X.,1,Answer Answer the line
exten => _X.,2,AGI(agi-DID_route.agi)
exten => _X.,3,Hangup()

Server IP: MYServerIP

Then I have in INBOUND:
In-Group:
TestIN
Default Transfer Group: TestIN
Active: Y

Which in Campaign Test; Inbound is on and inbound group of 'TestIN' is checked

Also have DID in Ingroup setup:

DID Extension: 1TargetDIDCalling
DID Route: IN_GROUP
User Route Settings In-Group: Test
Active: Y

Yet I can not get the inbound call to make it in...


Here are the results:
Code: Select all
<--- SIP read from UDP:DIDHostIP:58681 --->
INVITE sip:1TargetDIDCalling@MYServerIP:5060 SIP/2.0
Via: SIP/2.0/UDP DIDHostIP:5060;x-route-tag="tgrp:PSTN";branch=z9hG4bK18D84018BB
From: <sip:MyCellPhone@DIDHostIP>;tag=4F0B7660-23C1
To: <sip:1TargetDIDCalling@MYServerIP>
Date: Sat, 15 Mar 2014 15:21:12 GMT
Call-ID: 46A2B38E-AB8C11E3-9527A736-64C8D30@DIDHostIP
Supported: 100rel,timer,replaces
Min-SE: 1800
Cisco-Guid: 1185027942-2878083555-2604335127-243156848
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Remote-Party-ID: <sip:MyCellPhone@DIDHostIP>;party=calling;screen=yes;privacy=off
Timestamp: 1394896872
Contact: <sip:MyCellPhone@DIDHostIP:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 316

v=0
o=CiscoSystemsSIP-GW-UserAgent 6769 6611 IN IP4 DIDHostIP
s=SIP Call
c=IN IP4 DIDHostIP
t=0 0
a=rtr
m=audio 16668 RTP/AVP 18 0 101 19
c=IN IP4 DIDHostIP
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=rtpmap:19 CN/8000
<------------->
[Mar 15 11:17:41] --- (20 headers 14 lines) ---
[Mar 15 11:17:41] Sending to DIDHostIP:58681 (NAT)
[Mar 15 11:17:41] Using INVITE request as basis request - 46A2B38E-AB8C11E3-9527A736-64C8D30@DIDHostIP
[Mar 15 11:17:41] No matching peer for 'MyCellPhone' from 'DIDHostIP:58681'
[Mar 15 11:17:41]
<--- Reliably Transmitting (NAT) to DIDHostIP:58681 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP DIDHostIP:5060;x-route-tag="tgrp:PSTN";branch=z9hG4bK18D84018BB;received=DIDHostIP;rport=58681
From: <sip:MyCellPhone@DIDHostIP>;tag=4F0B7660-23C1
To: <sip:1TargetDIDCalling@MYServerIP>;tag=as11c43272
Call-ID: 46A2B38E-AB8C11E3-9527A736-64C8D30@DIDHostIP
CSeq: 101 INVITE
Server: Asterisk PBX 1.8.26.0-vici
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="60761077"
Content-Length: 0


<------------>
[Mar 15 11:17:41] Scheduling destruction of SIP dialog '46A2B38E-AB8C11E3-9527A736-64C8D30@DIDHostIP' in 32000 ms (Method: INVITE)
[Mar 15 11:17:41]
<--- SIP read from UDP:DIDHostIP:5060 --->
ACK sip:1TargetDIDCalling@MYServerIP:5060 SIP/2.0
Via: SIP/2.0/UDP DIDHostIP:5060;x-route-tag="tgrp:PSTN";branch=z9hG4bK18D84018BB
From: <sip:MyCellPhone@DIDHostIP>;tag=4F0B7660-23C1
To: <sip:1TargetDIDCalling@MYServerIP>;tag=as11c43272
Date: Sat, 15 Mar 2014 15:21:12 GMT
Call-ID: 46A2B38E-AB8C11E3-9527A736-64C8D30@DIDHostIP
Max-Forwards: 70
CSeq: 101 ACK
Content-Length: 0

<------------->
[Mar 15 11:17:41] --- (9 headers 0 lines) ---


The only thing I really notice is the different ports other than 5060

Re: Inbound issues

PostPosted: Mon Mar 17, 2014 9:16 am
by striker
did u noticed this
[Mar 15 11:17:41] Using INVITE request as basis request - 46A2B38E-AB8C11E3-9527A736-64C8D30@DIDHostIP
[Mar 15 11:17:41] No matching peer for 'MyCellPhone' from 'DIDHostIP:58681'

make sure u have proper credentials in ur carrier setup.

also try insecure=invite

Re: Inbound issues

PostPosted: Mon Mar 17, 2014 10:29 am
by udfxrookie
Not sure if you noticed above... it is:
insecure=port,invite
or were you saying just try
insecure=invite
dropping port?

Re: Inbound issues

PostPosted: Mon Mar 17, 2014 10:37 am
by striker
can u post the actual carrier setup u have....

Re: Inbound issues

PostPosted: Mon Mar 17, 2014 11:44 am
by udfxrookie
please read the first post, it includes everything... including carrier setup.

Re: Inbound issues

PostPosted: Fri Mar 21, 2014 2:17 pm
by udfxrookie
I see them hitting me, here now:

Code: Select all
[Mar 21 15:14:22]     -- Executing [1inbounddid@trunkinbound:1] AGI("SIP/engagetela-00000167", "agi-DID_route.agi") in new stack
[Mar 21 15:14:22]     -- Launched AGI Script /usr/share/asterisk/agi-bin/agi-DID_route.agi
[Mar 21 15:14:22]     -- <SIP/engagetela-00000167>AGI Script agi-DID_route.agi completed, returning 0
[Mar 21 15:14:22]     -- Executing [9998811112@default:1] Wait("SIP/engagetela-00000167", "2") in new stack
[Mar 21 15:14:24]   == Manager 'sendcron' logged on from 127.0.0.1
[Mar 21 15:14:24]     -- Executing [h@default:1] AGI("Local/8600054@default-00000416;1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----33-----8") in new stack
[Mar 21 15:14:24]   == Manager 'sendcron' logged on from 127.0.0.1
[Mar 21 15:14:24]   == Spawn extension (default, 8600054, 1) exited non-zero on 'Local/8600054@default-00000416;2'
[Mar 21 15:14:24]     -- Executing [h@default:1] AGI("Local/8600054@default-00000416;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack


what am i missing to get it to call the proper inbound route?

Re: Inbound issues

PostPosted: Fri Mar 21, 2014 11:21 pm
by striker
as your DID showing as 1inbounddid, so its landing default DID route..

1.create new ingroup.
2. go to DID- Default- Set DID Route= ingroup and select the ingroup which you created as said above
3. create belended Campaign

Re: Inbound issues

PostPosted: Sat Mar 22, 2014 11:45 pm
by williamconley
you are masking the did with text in your posts. as a result, it is likely there is merely a slight mismatch between the DID and the Vicidial "DID" entry. Possibly a 1 in front of it or a + (or both).

we have a routine that runs in "trunkinbound" that strips off "+" and another that strips off "1" if the number is 11 digits and starts with 1. This tends to clean it up quite well.

but you don't really need to go to all that bother, you merely need to be sure that your DID entry in "Inbound ->DIDs" in Vicidial matches the actual number shown here: Executing [1inbounddid@trunkinbound:1] before the "@" symbol. If you do, the number will Match and the path will be decided by the configuration of that DID instead of "Default" as it is presently.

Happy Hunting. 8-)