Patton SN-DTA ISDN Gateway not working

[quinti]

hi there,
i´m trying to connect a Patton SN-DTA as Gateway to a german Vodafone plusbox 340 with S0.
The patton is registering on 3cx as intended, green on 3cx. Debug from patton:

00:13:50  SIP_TR> [STACK] < 339 Stack: from 192.168.0.8
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.11.3:5060;branch=z9hG4bKc2d863d8c7ebcd1b8
Contact: <sip:[email protected]:5060>;expires=300
To: <sip:[email protected]>;tag=1bba7b64
From: <sip:[email protected]>;tag=7e606bc9d1
Call-ID: 5dbe0a979b4f5565
CSeq: 17526 REGISTER
User-Agent: 3CXPhoneSystem 18.0.8.939 (939)
Content-Length: 0

But we´re not able to make calls, neither inbound or outbound.
Inbound no debug messages on the Patton, no BRI LED blinking.

outbound we can see debug messages where the patton trys to establish a connection to S0, see attached file

3cx log:

01.10.2023 10:02:23 - Leg L:18.1[Extn:11] is terminated: Cause: BYE from PBX
01.10.2023 10:02:23 - [CM503020]: Call(C:18): Normal call termination. Call originator: Extn:11. Reason: Server Failure
01.10.2023 10:02:23 - L:18.1[Extn:11] failed to reach Line:10001>>004965165112, reason Server Failure
01.10.2023 10:02:23 - Leg L:18.2[Line:10001>>004965165112] is terminated: Cause: 503 Service Unavailable/INVITE from 192.168.11.3:5060
01.10.2023 10:02:23 - Call to T:Line:10001>>004965165112@[Dev:sip:[email protected]:5060] from L:18.1[Extn:11] failed, cause: Cause: 503 Service Unavailable/INVITE from 192.168.11.3:5060
01.10.2023 10:02:23 - [CM503003]: Call(C:18): Call to <sip:[email protected]:5060> has failed; Cause: 503 Service Unavailable/INVITE from 192.168.11.3:5060
01.10.2023 10:02:23 - [CM503025]: Call(C:18): Calling T:Line:10001>>004965165112@[Dev:sip:[email protected]:5060] for L:18.1[Extn:11]
01.10.2023 10:02:23 - [CM503027]: Call(C:18): From: Extn:11 ("Büro 11" <sip:[email protected]:5060>)  to  T:Line:10001>>004965165112@[Dev:sip:[email protected]:5060]
01.10.2023 10:02:23 - [CM503004]: Call(C:18): Route 1: from L:18.1[Extn:11] to T:Line:10001>>004965165112@[Dev:sip:[email protected]:5060]
01.10.2023 10:02:23 - Line limit check: Current # of calls for line Lc:10001(@Patton ISDN BRI[<sip:[email protected]:5060/UDP>]) is 0; limit is 2
01.10.2023 10:02:23 - Call(C:18): Call from Extn:11 to 65112 matches outbound rule 'Regional'
01.10.2023 10:02:23 - [Flow] Call(C:18): has built target endpoint: Out#:>>Rule{Regional}>>65112 for call from L:18.1[Extn:11]
01.10.2023 10:02:23 - [Flow] Target endpoint for 65112 is Out#:>>Rule{Regional}>>65112
01.10.2023 10:02:23 - [CM503010]: Call(C:18): Making route(s) from Extn:11 to <sip:[email protected]:5060/UDP>
01.10.2023 10:02:23 - [CM505001]: Endpoint Extn:11: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Yealink SIP-T58 58.86.0.39 805ec03d0fa1] PBX contact: [sip:[email protected]:5061]
01.10.2023 10:02:23 - [CM500002]: Call(C:18): Info on incoming INVITE from Extn:11:

Invite-IN Recv Req INVITE from 127.0.0.1:5080 tid=3199955470 [email protected]:

INVITE sip:[email protected]:5061;transport=UDP SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---3199955470;rport=5080

Via: SIP/2.0/UDP [::ffff:192.168.11.2]:45439;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=sbc.e69ce18d

Via: SIP/2.0/UDP 192.168.11.111:5060;branch=z9hG4bK3199955470

Max-Forwards: 68

Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.e69ce18d>

Record-Route: <sip:[email protected]:5060;user=proxy;tnlid=sbc.e69ce18d>

Contact: <sip:[email protected]:5060>

To: <sip:[email protected]:5060>

From: "Büro 11"<sip:[email protected]:5060>;tag=3199812131

Call-ID: [email protected]

CSeq: 2 INVITE

Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE

Content-Type: application/sdp

Proxy-Authorization: Digest username="2Ukk4y60ws",realm="3CXPhoneSystem",nonce="414d53596519278f10:22f611727942fe395b195f3efa45e6f5",uri="sip:[email protected]:5060",response="4853fc82ded7ff1b948fbc364d6fcbe0",algorithm=MD5

Supported: replaces

User-Agent: Yealink SIP-T58 58.86.0.39 805ec03d0fa1

Allow-Events: talk, hold, conference, refer, check-sync

Content-Length: 456



v=0

o=- 20042 20042 IN IP4 192.168.11.111

s=SDP data

c=IN IP4 192.168.11.111

t=0 0

m=audio 12252 RTP/AVP 0 8 9 18 112 101

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:112 opus/48000/2

a=fmtp:112 sprop-maxcapturerate=16000; maxaveragebitrate=20000; maxplaybackrate=48000; useylrtx=1; useinbandfec=1

a=ptime:20

a=sendrecv

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

01.10.2023 10:02:23 - [CM503001]: Call(C:18): Incoming call from Extn:11 to <sip:[email protected]:5060>
01.10.2023 10:02:22 - Make call request to number 65112 has been sent to device <sip:[email protected]:5060/UDP>

can anybody help?

 

[Alejandro_3CX]

Hi @quinti As first step please enter in contact with Patton so they can provide you assistance with that gateway.

Alternatively you can try with a supported VoIP Provider and check if you have the same issue or not.

The event log and activity log can also help you to get more information if the issue persists with a supported sip trunk.

Let us know how it goes!

 

[leejor]

In the first log I'm seeing IPs with two different subnets...192.168 0.X and 192.168.11.X . Is it supposed to be this way?