Toggle sidebar Toggle sidebar

Issues calling between two extensions.

qbitnetworking

qbitnetworking

Bronze Partner
Joined
Nov 28, 2020
Messages
138
Reaction score
30
I'm dealing with a strange issue where one particular extensions is not able to call another extension without the call being forwarded to voicemail. Calls in the reverse work. Checking the call log, it says the calls is being forwarded to voicemail because the extension is busy but I was onsite yesterday to test and it was definitely not busy. So far I've tried rebooting the server but that's about it. Any idea what could be causing this?
 
Is it just calls from one extension? Does it have a DID assigned, if so do those calls get through?
Could DND be enabled? I've heard of instances where it needs to be disabled via the dial code even though it is not obvious that it is enabled?
 
  • Like
Reactions: qbitnetworking
leejor said:
Is it just calls from one extension? Does it have a DID assigned, if so do those calls get through?
Could DND be enabled? I've heard of instances where it needs to be disabled via the dial code even though it is not obvious that it is enabled?
Click to expand...
It is just calls from one particular extension (well at least that we've discovered so far). No DID assigned. No status is set. I can see that the extension's status is in fact Available.
 
Is there any Exception configured on the extension Forwarding Rules?
 
TheodorosG_3CX said:
Is there any Exception configured on the extension Forwarding Rules?
Click to expand...
No exceptions configured. I believe this started happening after the most recent system update.
 
You say you've looked at the Call Log...do you have access to, and checked, the Activity Log?
 
leejor said:
You say you've looked at the Call Log...do you have access to, and checked, the Activity Log?
Click to expand...
Okay I just checked the activity log for anything at the last couple of times that user tried to call the extension and there is nothing out of the ordinary.
 
Did you set to Verbose, as that will show all the details of the call and hopefully why it goes to VM.

Could there be something set, on the called phone itself?
 
leejor said:
Did you set to Verbose, as that will show all the details of the call and hopefully why it goes to VM.

Could there be something set, on the called phone itself?
Click to expand...
Oh yes thank you. Now I just need to figure out how to read this lol. Here is what I see when I filter the log for the destination extension.

The calling extension is 115 and the destination is 124.

10/23/2024 2:35:58.252 PML:225.1[Extn:115{8e34413b0c6a}] from extn 124 (Extn:124); OutCID ''
10/23/2024 2:35:58.251 PML:225.3[Extn:124{4eef2138c46c}] detached from call; ads{140803}
10/23/2024 2:35:58.251 PML:225.3[Extn:124{4eef2138c46c}]: CONNECTION ID updated: 1591 => 0
10/23/2024 2:35:58.251 PMRemoving connected for L:225.3[Extn:124{4eef2138c46c}], terminate connected
10/23/2024 2:35:58.251 PML:225.3[Extn:124{4eef2138c46c}] is terminated
10/23/2024 2:35:58.251 PML:225.3[Extn:124{4eef2138c46c}] Outgoing handler: Terminated event: Busy Here
10/23/2024 2:35:58.251 PML:225.1[Extn:115{8e34413b0c6a}] has no segment with L:225.3[Extn:124{4eef2138c46c}]
10/23/2024 2:35:58.251 PML:225.1[Extn:115{8e34413b0c6a}] segment terminated (RouteBusy) to L:225.3[Extn:124{4eef2138c46c}]
10/23/2024 2:35:58.251 PMCall(C:225): request to stop call recording @ L:225.3[Extn:124{4eef2138c46c}]
10/23/2024 2:35:58.251 PML:225.3[Extn:124{4eef2138c46c}]: on terminated: 'Cause: BYE from PBX
10/23/2024 2:35:58.250 PMC:225 % RouteFailed Extn:124{4eef2138c46c}
10/23/2024 2:35:58.250 PML:225.3[Extn:124{4eef2138c46c}] changes event handler from Forked to Outgoing
10/23/2024 2:35:58.250 PMForked(1916538499)@C:225: OnFailure from L:225.3[Extn:124{4eef2138c46c}]; reason = Cause: 486 Busy Here/INVITE from 127.0.0.1:5080
10/23/2024 2:35:58.250 PML:225.3[Extn:124{4eef2138c46c}]: destroying MSEP([email protected]:5482@?)
10/23/2024 2:35:58.250 PML:225.3[Extn:124{4eef2138c46c}]: failure Cause: 486 Busy Here/INVITE from 127.0.0.1:5080
10/23/2024 2:35:58.098 PMBaseDest(1916538499)@C:225: Active connection update on L:225.3[Extn:124{4eef2138c46c}] (locked 0)
10/23/2024 2:35:58.098 PML:225.3[Extn:124{4eef2138c46c}]: CONNECTION ID updated: 0 => 1591
10/23/2024 2:35:58.098 PML:225.3[Extn:124{4eef2138c46c}] initiating call with InvOUT Send Req INVITE from 0.0.0.0:0 tid=e5c2f25ba0a7707e Call-ID=XmaJuSujNI6OAAGmBgdgqA..:INVITE sip:[email protected]:5060 SIP/2.0Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---e5c2f25ba0a7707e;rportMax-Forwards: 70Route: <sip:[email protected]:5080;user=proxy;uri=sbc.ea13cd2f>Route: <sip:[email protected]:5060;user=proxy;tnlid=sbc.ea13cd2f>Contact: <sip:[email protected]:5060>To: <sip:[email protected]>From: "Smith, John"<sip:[email protected]>;tag=59073740Call-ID: XmaJuSujNI6OAAGmBgdgqA..CSeq: 1 INVITEAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATEContent-Type: application/sdpSupported: replaces, timerContent-Length: 478v=0o=3cxPS 13208566479454208 11274114685730817 IN IP4 127.1.2.3s=3cxPS Audio callc=IN IP4 127.1.2.3b=AS:117t=0 0a=X-nat:0m=audio 648 RTP/AVP 0 8 9 18 125 101c=IN IP4 127.1.2.3b=TIAS:96000b=AS:117a=sendrecva=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:9 G722/8000a=rtpmap:18 G729/8000a=rtpmap:125 opus/48000/2a=fmtp:125 useinbandfec=1a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15a=rtcp:649m=video 0 RTP/AVP 31c=IN IP4 127.0.0.1
 
Here is what I see when I filter the log for the calling extension 115.

10/23/2024 2:35:58.423 PML:225.1[Extn:115{8e34413b0c6a}] changes event handler from Incoming to Connected
10/23/2024 2:35:58.423 PMC:225 Connected leg: L:225.1[Extn:115{8e34413b0c6a}]
10/23/2024 2:35:58.423 PML:225.1[Extn:115{8e34413b0c6a}] Incoming handler: Connected event
10/23/2024 2:35:58.423 PML:225.1[Extn:115{8e34413b0c6a}]: connected
10/23/2024 2:35:58.423 PMC:225 media is direct; checking media reneg conditions for L:225.1[Extn:115{8e34413b0c6a}] and L:225.4[VMail:999{98e3473ca828}]
10/23/2024 2:35:58.422 PMConnected: L:225.4[VMail:999{98e3473ca828}] => L:225.1[Extn:115{8e34413b0c6a}]
10/23/2024 2:35:58.421 PMSegm(1211): L:225.1[Extn:115{8e34413b0c6a}] segment answered at L:225.4[VMail:999{98e3473ca828}]
10/23/2024 2:35:58.421 PMSet connected: L:225.1[Extn:115{8e34413b0c6a}] <=> L:225.4[VMail:999{98e3473ca828}]
10/23/2024 2:35:58.421 PMCall(C:225): == Connected L:225.1[Extn:115{8e34413b0c6a}] and L:225.4[VMail:999{98e3473ca828}]
10/23/2024 2:35:58.421 PML:225.1[Extn:115{8e34413b0c6a}]: SDP events handler sehIncoming reset by sehIncoming
10/23/2024 2:35:58.421 PML:225.1[Extn:115{8e34413b0c6a}] onReadyToSend: Send Send 200/INVITE from 0.0.0.0:0 tid=PjJMHfjXvjSwLeqIyJ45sYxpVsYbMMN7At Call-ID=VujhNwhRoxssCPbdoaFj5vail1t8EJ8X:SIP/2.0 200 OKVia: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---PjJMHfjXvjSwLeqIyJ45sYxpVsYbMMN7At;rport=5080Via: SIP/2.0/UDP 68.117.141.23:57211;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.0-tkvmtxju1zyul4pzyrzi51gvza4xzebm_65293979Via: SIP/2.0/TCP 127.0.0.1:50195;rport;branch=z9hG4bKPjJMHfjXvjSwLeqIyJ45sYxpVsYbMMN7At;aliasRecord-Route: <sip:[email protected]:5080;user=proxy;uri=clnt.0-tkvmtxju1zyul4pzyrzi51gvza4xzebm_65293979>Require: timerContact: <sip:[email protected]:5060>To: <sip:[email protected];tag3cx=mrh7y5ig>;tag=3d3be55bFrom: "Smith, John"<sip:[email protected]>;tag=.i2vHgywKj50D2J3erjUVQYc2P2bWItECall-ID: VujhNwhRoxssCPbdoaFj5vail1t8EJ8XCSeq: 16121 INVITESession-Expires: 1800;refresher=uacAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATEContent-Type: application/sdpSupported: replaces, timerContent-Length: 389v=0o=3cxPS 14904000205815808 11053635727261697 IN IP4 127.1.2.3s=3cxPS Audio callc=IN IP4 127.1.2.3t=0 0m=audio 644 RTP/AVP 0 8 9 18 125 101a=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:9 G722/8000a=rtpmap:18 G729/8000a=rtpmap:125 opus/48000/2a=fmtp:125 useinbandfec=1a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15m=video 0 RTP/AVP 31c=IN IP4 127.0.0.1
10/23/2024 2:35:58.421 PML:225.1[Extn:115{8e34413b0c6a}]: state changed TookAnswer => Ready
10/23/2024 2:35:58.421 PML:225.1[Extn:115{8e34413b0c6a}] took local SDP for answer: v=0o=3cxPS 14904000205815808 11053635727261697 IN IP4 127.1.2.3s=3cxPS Audio callc=IN IP4 127.1.2.3t=0 0m=audio 644 RTP/AVP 0 8 9 18 125 101a=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:9 G722/8000a=rtpmap:18 G729/8000a=rtpmap:125 opus/48000/2a=fmtp:125 useinbandfec=1a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15m=video 0 RTP/AVP 31c=IN IP4 127.0.0.1
10/23/2024 2:35:58.420 PML:225.1[Extn:115{8e34413b0c6a}]: state changed SetOffer => TookAnswer
10/23/2024 2:35:58.420 PML:225.1[Extn:115{8e34413b0c6a}]: accepts INVITE; MSEP([email protected]:5482@[email protected]:5482)
10/23/2024 2:35:58.254 PML:225.1[Extn:115{8e34413b0c6a}] has no segment with L:225.2[Route:ROUTER@{}124{f4cc48770836}]
10/23/2024 2:35:58.254 PML:225.1[Extn:115{8e34413b0c6a}] segment terminated (UserTerminated) to L:225.2[Route:ROUTER@{}124{f4cc48770836}]
10/23/2024 2:35:58.254 PML:225.1[Extn:115{8e34413b0c6a}] has no segment with L:225.2[Route:ROUTER@{}124{f4cc48770836}]
10/23/2024 2:35:58.254 PML:225.1[Extn:115{8e34413b0c6a}] segment terminated (Ok) to L:225.2[Route:ROUTER@{}124{f4cc48770836}]
10/23/2024 2:35:58.252 PMC:225 create UAC leg, caller = L:225.1[Extn:115{8e34413b0c6a}]
10/23/2024 2:35:58.252 PMSingleDest(1434878824)@C:225 start, caller leg L:225.1[Extn:115{8e34413b0c6a}], ref-by-DN: ''
10/23/2024 2:35:58.252 PMSegm(1211): L:225.1[Extn:115{8e34413b0c6a}] divert from Segm(1210):
10/23/2024 2:35:58.252 PML:225.1[Extn:115{8e34413b0c6a}] from extn 124 (Extn:124); OutCID ''
10/23/2024 2:35:58.252 PML:225.1[Extn:115{8e34413b0c6a}] build target endpoint to VMail.124 on behalf of Route:ROUTER@{}124{f4cc48770836} using source "Smith, John"<sip:[email protected]>;tag=.i2vHgywKj50D2J3erjUVQYc2P2bWItE
10/23/2024 2:35:58.251 PML:225.1[Extn:115{8e34413b0c6a}] has no segment with L:225.3[Extn:124{4eef2138c46c}]
10/23/2024 2:35:58.251 PML:225.1[Extn:115{8e34413b0c6a}] segment terminated (RouteBusy) to L:225.3[Extn:124{4eef2138c46c}]
10/23/2024 2:35:58.096 PMC:225 create UAC leg, caller = L:225.1[Extn:115{8e34413b0c6a}]
10/23/2024 2:35:58.096 PMForked(1916538499)@C:225: start, caller leg L:225.1[Extn:115{8e34413b0c6a}], ref-by-DN: ''
10/23/2024 2:35:58.096 PML:225.1[Extn:115{8e34413b0c6a}] from extn 115 (Extn:115); OutCID ''
10/23/2024 2:35:58.096 PML:225.1[Extn:115{8e34413b0c6a}] build target endpoint to Extn.124 from Extn:115{8e34413b0c6a} using source "Smith, John"<sip:[email protected]>;tag=.i2vHgywKj50D2J3erjUVQYc2P2bWItE
10/23/2024 2:35:58.020 PMSegm(1210): L:225.1[Extn:115{8e34413b0c6a}] 1st segment updated with Route:ROUTER@{}124{f4cc48770836}
10/23/2024 2:35:58.020 PML:225.1[Extn:115{8e34413b0c6a}] onReadyToSend: Send Send 180/INVITE from 0.0.0.0:0 tid=PjJMHfjXvjSwLeqIyJ45sYxpVsYbMMN7At Call-ID=VujhNwhRoxssCPbdoaFj5vail1t8EJ8X:SIP/2.0 180 RingingVia: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---PjJMHfjXvjSwLeqIyJ45sYxpVsYbMMN7At;rport=5080Via: SIP/2.0/UDP 68.117.141.23:57211;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.0-tkvmtxju1zyul4pzyrzi51gvza4xzebm_65293979Via: SIP/2.0/TCP 127.0.0.1:50195;rport;branch=z9hG4bKPjJMHfjXvjSwLeqIyJ45sYxpVsYbMMN7At;aliasRecord-Route: <sip:[email protected]:5080;user=proxy;uri=clnt.0-tkvmtxju1zyul4pzyrzi51gvza4xzebm_65293979>Contact: <sip:[email protected]:5060>To: <sip:[email protected];tag3cx=mrh7y5ig>;tag=3d3be55bFrom: "Smith, John"<sip:[email protected]>;tag=.i2vHgywKj50D2J3erjUVQYc2P2bWItECall-ID: VujhNwhRoxssCPbdoaFj5vail1t8EJ8XCSeq: 16121 INVITEContent-Length: 0
10/23/2024 2:35:58.018 PMC:225 create UAC leg, caller = L:225.1[Extn:115{8e34413b0c6a}]
10/23/2024 2:35:58.018 PMSingleDest(2080502007)@C:225 start, caller leg L:225.1[Extn:115{8e34413b0c6a}], ref-by-DN: ''
10/23/2024 2:35:58.017 PM[IncRR](C:225): offer provided from L:225.1[Extn:115{8e34413b0c6a}]
10/23/2024 2:35:58.017 PML:225.1[Extn:115{8e34413b0c6a}] set remote offer SDP: v=0o=- 3938700957 3938700957 IN IP4 10.10.10.109s=pjmediab=AS:117t=0 0a=X-nat:0m=audio 10004 RTP/AVP 0 8 9 18 125 101c=IN IP4 10.10.10.109b=TIAS:96000b=AS:117a=rtcp:10005a=sendrecva=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:9 G722/8000a=rtpmap:18 G729/8000a=rtpmap:125 opus/48000/2a=fmtp:125 useinbandfec=1a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15m=video 0 RTP/AVP 31c=IN IP4 127.0.0.1
10/23/2024 2:35:58.017 PML:225.1[Extn:115{8e34413b0c6a}]MSEP([email protected]:5482@[email protected]:5482) set offer; joined
10/23/2024 2:35:58.017 PML:225.1[Extn:115{8e34413b0c6a}]: SDP events handler change from sehDefault to sehIncoming
10/23/2024 2:35:58.017 PMC:225: calling from L:225.1[Extn:115{8e34413b0c6a}] to Extn:124{b387d47ce2c3}
10/23/2024 2:35:58.017 PML:225.1[Extn:115{8e34413b0c6a}] from extn 115 (Extn:115); OutCID ''
10/23/2024 2:35:58.017 PML:225.1[Extn:115{8e34413b0c6a}] build target endpoint to Extn.124 from Extn:115{8e34413b0c6a} using source "Smith, John"<sip:[email protected]>;tag=.i2vHgywKj50D2J3erjUVQYc2P2bWItE
10/23/2024 2:35:58.017 PML:225.1[Extn:115{8e34413b0c6a}]: CONNECTION ID updated: 0 => 1589
10/23/2024 2:35:58.016 PML:225.1[Extn:115{8e34413b0c6a}]: created MSEP([email protected]:5482@[email protected]:5482) (unbound); joined, SRTP disabled
10/23/2024 2:35:58.016 PML:225.1[Extn:115{8e34413b0c6a}]: joined to MSCall(MSC([email protected]:5482))
10/23/2024 2:35:58.016 PML:225.1[Extn:115{8e34413b0c6a}]: Bridge endpoint: id = 123456; tunnel = clnt.0-tkvmtxju1zyul4pzyrzi51gvza4xzebm_65293979
 
  • Like
Reactions: a.almualla
I am going through the same issue after upgrading to V20, did you manage to resolve the issue?
 
  • Like
Reactions: qbitnetworking
a.almualla said:
I am going through the same issue after upgrading to V20, did you manage to resolve the issue?
Click to expand...
No this issue is still not resolved.
 
What is 124 registered to? Have you tried removing it and using web client for testing?
 
Alphabetic said:
What is 124 registered to? Have you tried removing it and using web client for testing?
Click to expand...
Ext 124 is registered to a Yealink T53. I haven't tried removing the phone, no.

I have tried using the web client and the mobile client to make the call from Ext 115 but still get the same result.
 
qbitnetworking said:
Ext 124 is registered to a Yealink T53. I haven't tried removing the phone, no.

I have tried using the web client and the mobile client to make the call from Ext 115 but still get the same result.
Click to expand...
humour me, delete the phone from the ext
 
You must log in or register to reply here.

Latest Posts

Forum statistics

Threads
111,962
Messages
589,980
Members
164,866
Latest member
swseabolt
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom