Toggle sidebar Toggle sidebar

Outbound calls from analog gateway

Status
Not open for further replies.

RoyB

Customer
Joined
Aug 2, 2018
Messages
4
Reaction score
0
Hi there,

I'm attempting to use an Adtran TA924 to provide a connection from some analog devices to the PSTN via a 3CX system. I have configured the device as a generic PSTN gateway, and with a little fiddling, have gotten inbound calls working well. I haven't been able to figure out outbound calls, though. Outbound calls from the analog devices are processed by 3CX as an inbound call, which I can't seem to manage to send out to the PSTN.

What am I missing here? Is this something that's handled by the custom configurations in officially supported gateways?

Relevant log clip below. Taken from Activity Log in the portal, so read from the bottom up.

Actors in log:
192.168.1.6: 3CX
192.168.1.7: Adtran
1009: User on Adtran making call
10001: ID for trunk between Adtran and 3CX
5: prefix for outbound rule to Adtran
59000/9000: Default route for Adtran trunk, a hunt group


Code: 
10/08/2018 2:14:26 AM - Route to L:576.2[Line:10001>>9000] sends Invite-OUT Send Req INVITE from 0.0.0.0:0 tid=006ab13d3fdef250 Call-ID=GpA2-g5l3RGRjuwmz5GqVw..:
INVITE sip:[email protected]:5160 SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---006ab13d3fdef250;rport
Max-Forwards: 70
Contact: <sip:192.168.1.6:5060>
To: <sip:[email protected]:5160>
From: "1009"<sip:192.168.1.6:5060>;tag=9bcb5e63
Call-ID: GpA2-g5l3RGRjuwmz5GqVw..
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
Content-Length: 286
v=0
o=3cxPS 29713713279795200 25260179700318209 IN IP4 192.168.1.6
s=3cxPS Audio call
c=IN IP4 192.168.1.6
t=0 0
m=audio 8154 RTP/AVP 0 8 9 3 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=rtpmap:3 GSM/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
10/08/2018 2:14:26 AM - Outbound CID reformat rule for DN:10001 is disabled (<Rules />)
10/08/2018 2:14:26 AM - Outbound URI is used: sip:[email protected]:5160
10/08/2018 2:14:26 AM - SLA is globally disabled
10/08/2018 2:14:26 AM - Added leg L:576.2[Line:10001>>9000]
10/08/2018 2:14:26 AM - Remote SDP is set for leg L:576.1[Line:10001<<1009]
10/08/2018 2:14:26 AM - OnOffer from "1009"<sip:1009@{3cx fqdn}:5060;nf=e>
10/08/2018 2:14:26 AM - [Flow] Call(C:576): making call from L:576.1[Line:10001<<1009] to T:Line:10001>>9000@[Dev:sip:[email protected]:5160]
10/08/2018 2:14:26 AM - [CM503027]: Call(C:576): From: Line:10001<<1009 ("1009" <sip:1009@{3cx fqdn}:5060>)  to  T:Line:10001>>9000@[Dev:sip:[email protected]:5160]
10/08/2018 2:14:26 AM - [CM503004]: Call(C:576): Route 1: from L:576.1[Line:10001<<1009] to T:Line:10001>>9000@[Dev:sip:[email protected]:5160]
10/08/2018 2:14:26 AM - Outbound CID reformat rule for DN:10001 is disabled (<Rules />)
10/08/2018 2:14:26 AM - Line limit check: Current # of calls for line Lc:10001(@Adtran[<sip:[email protected]:5160>]) is 1; limit is 24
10/08/2018 2:14:26 AM - Call(C:576): Call from Line:10001<<1009 to 59000 matches outbound rule 'Bridge-FAX'
10/08/2018 2:14:26 AM - [Flow] Call(C:576): has built target endpoint: Out#:>>Rule{Bridge-FAX}>>59000 for call from L:576.1[Line:10001<<1009]
10/08/2018 2:14:26 AM - [Flow] Target endpoint for 59000 is Out#:>>Rule{Bridge-FAX}>>59000
10/08/2018 2:14:26 AM - Selected prefix: 5
10/08/2018 2:14:26 AM - Looking for outbound rule: dialed = [59000], processed: [59000]; from-ext:
10/08/2018 2:14:26 AM - [Flow] Building target endpoint to 59000 from "1009" <sip:1009@{3cx fqdn}:5060>
10/08/2018 2:14:26 AM - [CM503010]: Call(C:576): Making route(s) from Line:10001<<1009 to <sip:[email protected]:5060>
10/08/2018 2:14:26 AM - [CM505002]: Gateway:[Adtran] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [ADTRAN_Total_Access_924_2nd_Gen/R13.2.1.E] PBX contact: [sip:[email protected]:5060]
10/08/2018 2:14:26 AM - Remote SDP is set for leg L:576.1[Line:10001<<1009]
10/08/2018 2:14:26 AM - Inbound DID: ''; Phonebook Name: ''
10/08/2018 2:14:26 AM - [CM500002]: Call(C:576): Info on incoming INVITE from Line:10001<<1009:
Invite-IN Recv Req INVITE from 192.168.1.7:5160 tid=-95d09-24936c3d-4645ea47 [email protected]:
INVITE sip:{test number}@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.7:5160;branch=z9hG4bK-95d09-24936c3d-4645ea47
Max-Forwards: 70
Contact: <sip:[email protected]:5160;transport=UDP>
To: <sip:{test number}@192.168.1.6:5060>
From: "1009"<sip:[email protected]:5160;transport=UDP>;tag=323c3c8-7f000001-1428-95d09-2ba6e2a6-95d09
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
Content-Type: application/sdp
Proxy-Authorization: Digest username="{xxxxx}",realm="3CXPhoneSystem",nonce="{xxxxx}",uri="sip:{test number}@192.168.1.6:5060",response="00c4de3a226ec916c962bf73d8d10840",algorithm=MD5
Supported: 100rel, replaces
User-Agent: ADTRAN_Total_Access_924_2nd_Gen/R13.2.1.E
Content-Length: 206
v=0
o=- 1538979266 1 IN IP4 192.168.1.7
s=-
c=IN IP4 192.168.1.7
t=0 0
m=audio 10266 RTP/AVP 0 101
a=silenceSupp:eek:ff - - - -
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
10/08/2018 2:14:26 AM - [CM503001]: Call(C:576): Incoming call from Line:10001<<1009 to <sip:[email protected]:5060>
10/08/2018 2:14:26 AM - Line limit check: Current # of calls for line Lc:10001(@Adtran[<sip:[email protected]:5160>]) is 1; limit is 24
10/08/2018 2:14:26 AM - Blacklist check: number '1009', list: ''; result = false
10/08/2018 2:14:26 AM - Offer SDP arrived on Leg L:576.1[Line:10001<<1009];
OnOffer Recv Req INVITE from 192.168.1.7:5160 tid=-95d09-24936c3d-4645ea47 [email protected]:
INVITE sip:{test number}@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.7:5160;branch=z9hG4bK-95d09-24936c3d-4645ea47
Max-Forwards: 70
Contact: <sip:[email protected]:5160;transport=UDP>
To: <sip:{test number}@192.168.1.6:5060>
From: "1009"<sip:[email protected]:5160;transport=UDP>;tag=323c3c8-7f000001-1428-95d09-2ba6e2a6-95d09
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
Content-Type: application/sdp
Proxy-Authorization: Digest username="{xxxxx}",realm="3CXPhoneSystem",nonce="{xxxxx}",uri="sip:{test number}@192.168.1.6:5060",response="00c4de3a226ec916c962bf73d8d10840",algorithm=MD5
Supported: 100rel, replaces
User-Agent: ADTRAN_Total_Access_924_2nd_Gen/R13.2.1.E
Content-Length: 206
v=0
o=- 1538979266 1 IN IP4 192.168.1.7
s=-
c=IN IP4 192.168.1.7
t=0 0
m=audio 10266 RTP/AVP 0 101
a=silenceSupp:eek:ff - - - -
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
10/08/2018 2:14:26 AM - Outbound URI is used: sip:[email protected]:5160
10/08/2018 2:14:26 AM - Updating device Dev(570613509):[sip:[email protected]:5160 / 10001] by message: DevUpd Recv Req INVITE from 192.168.1.7:5160 tid=-95d09-24936c3d-4645ea47 [email protected]:
INVITE sip:{test number}@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.7:5160;branch=z9hG4bK-95d09-24936c3d-4645ea47
Max-Forwards: 70
Contact: <sip:[email protected]:5160;transport=UDP>
To: <sip:{test number}@192.168.1.6:5060>
From: "1009"<sip:[email protected]:5160;transport=UDP>;tag=323c3c8-7f000001-1428-95d09-2ba6e2a6-95d09
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
Content-Type: application/sdp
Proxy-Authorization: Digest username="{xxxxx}",realm="3CXPhoneSystem",nonce="{xxxxx}",uri="sip:{test number}@192.168.1.6:5060",response="00c4de3a226ec916c962bf73d8d10840",algorithm=MD5
Supported: 100rel, replaces
User-Agent: ADTRAN_Total_Access_924_2nd_Gen/R13.2.1.E
Content-Length: 206
v=0
o=- 1538979266 1 IN IP4 192.168.1.7
s=-
c=IN IP4 192.168.1.7
t=0 0
m=audio 10266 RTP/AVP 0 101
a=silenceSupp:eek:ff - - - -
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
10/08/2018 2:14:26 AM - [CM503012]: Inbound office hours rule (unnamed) for 10001 forwards to DN:59000
10/08/2018 2:14:26 AM - [Flow] No office hours set, office hours assumed
10/08/2018 2:14:26 AM - [Flow] Looking for inbound target: called={test number}; caller="1009" <sip:1009@:5060>
10/08/2018 2:14:26 AM - CallerNameAddr: "1009"<sip:1009;nf=e>
10/08/2018 2:14:26 AM - No inbound caller ID reformat rule for DN:10001 is defined, or it is disabled (<Rules />)
10/08/2018 2:14:26 AM - Line 10001 has been updated from DB
10/08/2018 2:14:26 AM - Failed to add outbound CID reformating rule for DN:10001: <Rules />
10/08/2018 2:14:26 AM - Source is identified as trunk Lc:10001(@Adtran[<sip:[email protected]:5160>])
10/08/2018 2:14:26 AM - IncomingCall: C:576 from <sip:[email protected]:5160> to <sip:{test number}@192.168.1.6:5060>
10/08/2018 2:14:26 AM - Added leg L:C:576.1[No endpoint yet]
10/08/2018 2:14:26 AM - Call from "1009"<sip:[email protected]:5160;transport=UDP>;tag=323c3c8-7f000001-1428-95d09-2ba6e2a6-95d09 to <sip:{test number}@192.168.1.6:5060>;tag=68d75f7f
10/08/2018 2:14:26 AM - Source is identified as trunk Lc:10001(@Adtran[<sip:[email protected]:5160>])
 
I also recreated this with a bridge configuration as well, with 3CX acting as master. Similar results.

I don't understand how to handle source identification on the bridge? What is 3CX expecting?



Code: 
10/08/2018 4:34:41 AM - [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
Invite-UNK Recv Req INVITE from 192.168.1.7:5160 tid=-97ddd-2513a7b3-4ace0920 [email protected]:
INVITE sip:{test phone}@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.7:5160;branch=z9hG4bK-97ddd-2513a7b3-4ace0920
Max-Forwards: 70
Contact: <sip:[email protected]:5160;transport=UDP>
To: <sip:{test phone}@192.168.1.6:5060>
From: "1009" <sip:[email protected]:5160;transport=UDP>;tag=3242d68-7f000001-1428-97ddd-62202fed-97ddd
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
Content-Type: application/sdp
Proxy-Authorization: Digest username="10001",realm="3CXPhoneSystem",nonce="414d53595bbb16a166:d385a04a9feed756e32b75dcc5cfda13",uri="sip:{test phone}@192.168.1.6:5060",response="d9dd23a189fb8060a4a0b41b80b8e8e1",algorithm=MD5
Supported: 100rel, replaces
User-Agent: ADTRAN_Total_Access_924_2nd_Gen/R13.2.1.E
Content-Length: 206
v=0
o=- 1538987681 1 IN IP4 192.168.1.7
s=-
c=IN IP4 192.168.1.7
t=0 0
m=audio 10388 RTP/AVP 0 101
a=silenceSupp:eek:ff - - - -
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
10/08/2018 4:34:41 AM - [CM302002]: Authentication failed due to unidentified source of: SipReq:  INVITE {test phone}@192.168.1.6:5060 tid=-97ddd-2513a7b3-4ace0920 cseq=2 INVITE [email protected]:5160 / 2 from(wire)
10/08/2018 4:34:41 AM - [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
Invite-UNK Recv Req INVITE from 192.168.1.7:5160 tid=-97ddd-2513a753-2c9b08db [email protected]:
INVITE sip:{test phone}@192.168.1.6:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.7:5160;branch=z9hG4bK-97ddd-2513a753-2c9b08db
Max-Forwards: 70
Contact: <sip:[email protected]:5160;transport=UDP>
To: <sip:{test phone}@192.168.1.6:5060>
From: "1009" <sip:[email protected]:5160;transport=UDP>;tag=3242d68-7f000001-1428-97ddd-62202fed-97ddd
Call-ID: [email protected]
CSeq: 1 INVITE
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
Content-Type: application/sdp
Supported: 100rel, replaces
User-Agent: ADTRAN_Total_Access_924_2nd_Gen/R13.2.1.E
Content-Length: 206
v=0
o=- 1538987681 1 IN IP4 192.168.1.7
s=-
c=IN IP4 192.168.1.7
t=0 0
m=audio 10388 RTP/AVP 0 101
a=silenceSupp:eek:ff - - - -
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
 
Bumping off page 3...
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,899
Messages
589,620
Members
164,765
Latest member
domi
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom