Zoom ATA revisited

[PaulN]

https://www.3cx.com/community/threads/zoom-ata-adapter.81690/#post-377673

Following on from the above post, I do now have an extension set up and registered on the ATA but there is at least 15 second delay before the attached analogue phone starts ringing.
I have tried dialling the extension number directly and there is the same delay setting up the call so it seems that it isn’t related to the call from the PSTN landline.I need to investigate further about why there’s such a big delay in the call setup

 

[leejor]

I would check the 3CX Activity Log to see if an INVITE is sent immediately to the ATA. (and it's going to the correct destination) If it is, then the delay may be the result of a setting in the ATA.

 

[PaulN]

I would check the 3CX Activity Log to see if an INVITE is sent immediately to the ATA. If it is, then the delay may be the result of a setting in the ATA.

Thanks I’ll check that later

 

[PaulN]

I would check the 3CX Activity Log to see if an INVITE is sent immediately to the ATA. (and it's going to the correct destination) If it is, then the delay may be the result of a setting in the ATA.

here is the activity log for a call placed from the 3cx app on a iPhone (extn 998) to the extension of the zoom ata (extension 160) there does seem to be a delay but without looking into the log in more detail I can’t be certain if there is a delay on the 3cx side, but from what I can identify the delay seems to be the time for the zoom to actually confirm that the extension is ringing.

If you see anything that I can’t see leejor please feel free to comment :-

05/26/2021 5:01:32 PM - Endpoint Extn:160 has refreshed contact <sip:[email protected]:5060/UDP>

05/26/2021 5:00:02 PM - Endpoint Extn:160 has refreshed contact <sip:[email protected]:5060/UDP>

05/26/2021 4:59:54 PM - L:103.2[Extn:160]: Terminating targets, reason: SIP ;cause=487 ;text="Invite request successfully cancelled."

05/26/2021 4:59:54 PM - Leg L:103.2[Extn:160] is terminated: Cause: 487 Invite request successfully cancelled./INVITE from 192.168.1.202:5060

05/26/2021 4:59:54 PM - Call(C:103), Extn:160 on entry: DlgInfo(103-9065/Terminated / R)

05/26/2021 4:59:54 PM - Notify dialog-info: Extn:160: sip:[email protected]:5060, Call(C:103)

05/26/2021 4:59:54 PM - L:103.2[Extn:160] got Terminated Recv 487/INVITE from 192.168.1.202:5060 tid=91064e047fd0a71f Call-ID=lrWfCLtJNdu2Ud9MKfgwpA..: SIP/2.0 487 Invite request successfully cancelled. Via: SIP/2.0/UDP 192.168.1.39:5060;branch=z9hG4bK-524287-1---91064e047fd0a71f;rport=5060;received=192.168.1.39 Contact: <sip:[email protected]:5060> To: <sip:[email protected]>;tag=22756099 From: "Paul"<sip:[email protected]>;tag=4bbf6a29 Call-ID: lrWfCLtJNdu2Ud9MKfgwpA.. CSeq: 1 INVITE User-Agent: Zoom 0.5.0 Content-Length: 0

05/26/2021 4:59:54 PM - L:103.2[Extn:160] got Failure: Failure Recv 487/INVITE from 192.168.1.202:5060 tid=91064e047fd0a71f Call-ID=lrWfCLtJNdu2Ud9MKfgwpA..: SIP/2.0 487 Invite request successfully cancelled. Via: SIP/2.0/UDP 192.168.1.39:5060;branch=z9hG4bK-524287-1---91064e047fd0a71f;rport=5060;received=192.168.1.39 Contact: <sip:[email protected]:5060> To: <sip:[email protected]>;tag=22756099 From: "Paul"<sip:[email protected]>;tag=4bbf6a29 Call-ID: lrWfCLtJNdu2Ud9MKfgwpA.. CSeq: 1 INVITE User-Agent: Zoom 0.5.0 Content-Length: 0

05/26/2021 4:59:54 PM - Session 187873 has failed in leg L:103.2[Extn:160] ; Cause: 487 Invite request successfully cancelled./INVITE from 192.168.1.202:5060

05/26/2021 4:59:54 PM - Stop call record for leg L:103.2[Extn:160]

05/26/2021 4:59:54 PM - Removing leg L:103.2[Extn:160]

05/26/2021 4:59:54 PM - L:103.2[Extn:160]: Terminating targets, reason: SIP ;cause=200 ;text="Call terminated on user request"

05/26/2021 4:59:54 PM - Call(C:103), Extn:160 on exit: DlgInfo(103-9065/Terminated / R)

05/26/2021 4:59:54 PM - Call(C:103), Extn:160 on entry: DlgInfo(103-9065/Early / R)

05/26/2021 4:59:54 PM - Notify dialog-info: Extn:160: sip:[email protected]:5060, Call(C:103)

05/26/2021 4:59:54 PM - Terminating L:103.2[Extn:160]

05/26/2021 4:59:54 PM - L:103.2[Extn:160]: Terminating route Dev:sip:[email protected]:5060

05/26/2021 4:59:51 PM - Provisional response arrived for session 187873 of Leg L:103.2[Extn:160]

05/26/2021 4:59:51 PM - L:103.2[Extn:160] got Provisional Recv 180/INVITE from 192.168.1.202:5060 tid=91064e047fd0a71f Call-ID=lrWfCLtJNdu2Ud9MKfgwpA..: SIP/2.0 180 Ringing... Via: SIP/2.0/UDP 192.168.1.39:5060;branch=z9hG4bK-524287-1---91064e047fd0a71f;rport=5060;received=192.168.1.39 Contact: <sip:[email protected]:5060> To: <sip:[email protected]>;tag=22756099 From: "Paul”<sip:[email protected]>;tag=4bbf6a29 Call-ID: lrWfCLtJNdu2Ud9MKfgwpA.. CSeq: 1 INVITE User-Agent: Zoom 0.5.0 Content-Length: 0

05/26/2021 4:59:51 PM - [CM505001]: Endpoint Extn:160: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Zoom 0.5.0] PBX contact: [sip:[email protected]:5060]

05/26/2021 4:59:51 PM - [CM503002]: Call(C:103): Alerting Extn:160 by contact <sip:[email protected]:5060/UDP>

05/26/2021 4:59:51 PM - Call(C:103), Extn:160 on exit: DlgInfo(103-9065/Early / R)

05/26/2021 4:59:51 PM - Call(C:103), Extn:160 on entry: DlgInfo(103-9065/Initial / R)

05/26/2021 4:59:51 PM - Notify dialog-info: Extn:160: sip:[email protected]:5060, Call(C:103)

05/26/2021 4:59:51 PM - UacSession 187873 has formed leg L:103.2[Extn:160]

05/26/2021 4:59:41 PM - [CM503025]: Call(C:103): Calling T:Extn:160@[Dev:sip:[email protected]:5060] for L:103.1[Extn:998]

05/26/2021 4:59:41 PM - Route to L:103.2[Extn:160] sends Invite-OUT Send Req INVITE from 0.0.0.0:0 tid=91064e047fd0a71f Call-ID=lrWfCLtJNdu2Ud9MKfgwpA..: INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---91064e047fd0a71f;rport Max-Forwards: 70 Contact: <sip:[email protected]:5060> To: <sip:[email protected]> From: "Paul”<sip:[email protected]:5060>;tag=4bbf6a29 Call-ID: lrWfCLtJNdu2Ud9MKfgwpA.. 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: 427 v=0 o=3cxPS 20217619911016448 24846802654068737 IN IP4 192.168.1.39 s=3cxPS Audio call c=IN IP4 192.168.1.39 t=0 0 m=audio 7664 RTP/AVP 0 8 9 3 18 112 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:3 GSM/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:112 opus/48000/2 a=fmtp:112 maxplaybackrate=16000;sprop-maxcapturerate=16000 a=rtpmap:101 telephone-event/8000 a=sendrecv

05/26/2021 4:59:41 PM - L:103.2[Extn:160]: device's outbound URI is used: 192.168.1.202

05/26/2021 4:59:41 PM - L:103.2[Extn:160]: SLA slot is acquired: 160#0 'idle'

05/26/2021 4:59:41 PM - Added leg L:103.2[Extn:160]

05/26/2021 4:59:41 PM - [Flow] Call(C:103): making call from L:103.1[Extn:998] to T:Extn:160@[Dev:sip:[email protected]:5060]

05/26/2021 4:59:41 PM - [CM503027]: Call(C:103): From: Extn:998 ("Paul" <sip:[email protected]:0>) to T:Extn:160@[Dev:sip:[email protected]:5060

05/26/2021 4:59:41 PM - [CM503004]: Call(C:103): Route 1: from L:103.1[Extn:998] to T:Extn:160@[Dev:sip:[email protected]:5060]

05/26/2021 4:59:41 PM - Found 1 contacts for 160

05/26/2021 4:59:41 PM - [Flow] Endpoint Extn:160 has no forwarding rule on reason 'All calls'

05/26/2021 4:59:41 PM - [Flow] Call(C:103): has built target endpoint: Extn:160 for call from L:103.1[Extn:998]

05/26/2021 4:59:41 PM - [Flow] Target endpoint for 160 is Extn:160

 

[leejor]

So, reading from the bottom up. Everything starts at 4:59:41, including the initial Invite

05/26/2021 4:59:41 PM - Route to L:103.2[Extn:160] sends Invite-OUT

10 seconds later, 3CX gets back a Ringing message.

05/26/2021 4:59:51 PM - L:103.2[Extn:160] got Provisional Recv 180/INVITE from 192.168.1.202:5060 tid=91064e047fd0a71f Call-ID=lrWfCLtJNdu2Ud9MKfgwpA..: SIP/2.0 180 Ringing...

This tells us that the ATA received the Invite and has indicated that it is ringing the set. But for some reason, it took 10 seconds to respond.

 

[PaulN]

So, reading from the bottom up. Everything starts at 4:59:41, including the initial Invite


10 seconds later, 3CX gets back a Ringing message.



This tells us that the ATA received the Invite and has indicated that it is ringing the set. But for some reason, it took 10 seconds to respond.

thanks lee that is what I suspected was the case too. I’ll dig deeper into the ATA and see what can discover on that side

 

[PaulN]

thanks lee that is what I suspected was the case too. I’ll dig deeper into the ATA and see what can discover on that side

I found the following referring to the SPA2102 which at some point was compatible with the zoom 5801.


I have tried transferring the settings to the zoom ata :-

Hope this might help suggest Any changes required

 

[leejor]

Normally those timer values can be left at the default with no issue. If your device was used previously, and a "factory reset" was not done before you began, then you might want to make note of the settings require by 3CX, and do one.

Have not used the Zoom ATA before, so I don't know if it has a log of some sort. If it does, it may help explain what is happening.

 

[PaulN]

Thanks lee, I did do a factory reset so will if there is a log on the zoom to give some insight to what is happening. I am pretty confident that 3CX is acting as it should be and the problem is on the ATA

 

[PaulN]

Hi Leejor. I’ve solved the issue. The ATA was doing a STUN lookup so I’ve disabled that and all is ok now

 

[leejor]

Great. STUN would probably only be nessirary if you were using the ATA remotely, although if the STUN settings were valid, it should not be taking that long and delaying an incoming call. But, every ATA has it's quirks.

 

[PaulN]

Thanks Lee, the STUN server address was the default factory setting, I thought it was disabled but it was enabled and that was never going to be good.

all is now good and can be marked as problem solved