Toggle sidebar Toggle sidebar

Solved IP Phones cannot make outbound calls

Status
Not open for further replies.

TurabG

Free User
Joined
Jun 12, 2018
Messages
58
Reaction score
1
Hi,

We have been trying 3CX Standart version for about 10 days. I have registered 4 SIP trunks and was able to use both for inbound and outbound. As of yesterday, IP phones (all of the extensions) stopped making outbound calls. When you try to call an external number, you hear just the busy tone. The call is present in the call log as "not answered" but there's nothing about this call neither in event log nor in activity log.

Every other thing is working. Mobile clients can make outbound calls with the same extension being registered.

How can I diagnose this problem?
 
Hello @TurabG

Please navigate to Dashboard / Activity log / Settings and set the logging level to verbose. Then restart all services of the PBX and try to perform an outbound call. Check the Activity log after for any clues regarding the issue.
Also make sure that the IP phones are registered to the PBX. They should be visible under the phones tab.
Make sure that an outbound rule is used that includes the IP phones so they are able to call.
What IP phones are you using?
Are they provisioned as local, STUN or SBC devices?
 
Thank you @YiannisH_3CX ,

Phones are provisioned manually and locally; they are present in the phones list. Phones receive inbound calls and all of the phones can call any of the extensions; everything is working as they should.

We are using Gigaset C530 and Vtech VSP600, which are not supported by 3CX but were perfectly working until yesterday.

Here is the log after turning Verbose mode on;

07/10/2018 2:11:57 PM - Leg L:1.2[Line:10002>>05xxxxxxxx] is terminated: Cause: 487 Request Terminated/INVITE from 95.xxx.xxx.xxx:5060
 
Code: 
07/10/2018 2:19:14 PM - Updating device Dev(1872389884):[sip:[email protected]:5488;rinstance=f717e7e6d6acfd03 / 1016] by message: DevUpd Recv Req REGISTER from 127.0.0.1:5488 tid=fe77821534501161 Call-ID=I0vwPj9_lgh5kLSYvQykqA..:
REGISTER sip:xxxx.3cx.com SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---fe77821534501161;rport=5488
Max-Forwards: 70
Contact: <sip:[email protected]:5488;rinstance=f717e7e6d6acfd03>
To: "Push for 1016"<sip:[email protected]>
From: "Push for 1016"<sip:[email protected]>;tag=ab126735
Call-ID: I0vwPj9_lgh5kLSYvQykqA..
CSeq: 14 REGISTER
Expires: 120
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Proxy-Authorization: Digest username="teknik",realm="3CXPhoneSystem",nonce="414d535c1155273248:3440f2933b78640a65266982bde2c418",uri="sip:xxxx.3cx.com",response="6575dfc1fb8f8754a1e65689885595e4",algorithm=MD5
Supported: replaces
User-Agent: 3CX Push Service
Content-Length: 0

07/10/2018 2:19:14 PM - Updating device Dev(254761810):[sip:[email protected]:5488;rinstance=9c1052e8a86ca24b / 1022] by message: DevUpd Recv Req REGISTER from 127.0.0.1:5488 tid=f470e239a755ac16 Call-ID=tKAJl3vRGGRcCDZUdbXGwg..:
REGISTER sip:xxxx.3cx.com SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---f470e239a755ac16;rport=5488
Max-Forwards: 70
Contact: <sip:[email protected]:5488;rinstance=9c1052e8a86ca24b>
To: "Push for 1022"<sip:[email protected]>
From: "Push for 1022"<sip:[email protected]>;tag=8a047c1a
Call-ID: tKAJl3vRGGRcCDZUdbXGwg..
CSeq: 14 REGISTER
Expires: 120
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Proxy-Authorization: Digest username="sirri",realm="3CXPhoneSystem",nonce="414d535c1155273234:b5b15d734cb5a246e5d85f49c726dff5",uri="sip:xxxx.3cx.com",response="be7eb594a8ca03c0ab36fe74070c82be",algorithm=MD5
Supported: replaces
User-Agent: 3CX Push Service
Content-Length: 0

07/10/2018 2:19:14 PM - Updating device Dev(814638823):[sip:[email protected]:5488;rinstance=bad67abc44a26102 / 1023] by message: DevUpd Recv Req REGISTER from 127.0.0.1:5488 tid=fe28095f2828d22e Call-ID=nQzVnI90wuATCBBc_yZ7hQ..:
REGISTER sip:xxxx.3cx.com SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---fe28095f2828d22e;rport=5488
Max-Forwards: 70
Contact: <sip:[email protected]:5488;rinstance=bad67abc44a26102>
To: "Push for 1023"<sip:[email protected]>
From: "Push for 1023"<sip:[email protected]>;tag=6d7b5d6d
Call-ID: nQzVnI90wuATCBBc_yZ7hQ..
CSeq: 14 REGISTER
Expires: 120
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Proxy-Authorization: Digest username="firat",realm="3CXPhoneSystem",nonce="414d535c1155273239:c20fd92d371087fca2fdf8758c86ad01",uri="sip:xxxx.3cx.com",response="3d9f760aa15076032c5d344dfd84ab25",algorithm=MD5
Supported: replaces
User-Agent: 3CX Push Service
Content-Length: 0

07/10/2018 2:19:14 PM - Updating device Dev(38492253):[sip:[email protected]:5488;rinstance=a9db343bcd1b6e26 / 1020] by message: DevUpd Recv Req REGISTER from 127.0.0.1:5488 tid=e07ec54a0640a53c Call-ID=H2Gei-I9tw14VuBsmGQKbA..:
REGISTER sip:xxxx.3cx.com SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---e07ec54a0640a53c;rport=5488
Max-Forwards: 70
Contact: <sip:[email protected]:5488;rinstance=a9db343bcd1b6e26>
To: "Push for 1020"<sip:[email protected]>
From: "Push for 1020"<sip:[email protected]>;tag=952d5b28
Call-ID: H2Gei-I9tw14VuBsmGQKbA..
CSeq: 14 REGISTER
Expires: 120
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Proxy-Authorization: Digest username="xxx",realm="3CXPhoneSystem",nonce="414dxxx5c115xxxxxa49059bxxxxxb898cf0dd4fc",uri="sip:xxxx.3cx.com",response="d5xxxxxxxxxxxcc9fcd",algorithm=MD5
Supported: replaces
User-Agent: 3CX Push Service
Content-Length: 0

07/10/2018 2:19:14 PM - Updating device Dev(1547061503):[sip:[email protected]:5488;rinstance=a6b441d20a319b98 / DialCode] by message: DevUpd Recv Req REGISTER from 127.0.0.1:5488 tid=ae61d53f512d0470 Call-ID=UcQCVp8pU8lgFIhhgBV-Tg..:
REGISTER sip:xxxx.3cx.com SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---ae61d53f512d0470;rport=5488
Max-Forwards: 70
Contact: <sip:[email protected]:5488;rinstance=a6b441d20a319b98>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=d14f8705
Call-ID: UcQCVp8pU8lgFIhhgBV-Tg..
CSeq: 8 REGISTER
Expires: 120
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Proxy-Authorization: Digest username="DialCode",realm="3CXPhoneSystem",nonce="414d535c115524a915:0deaf8e0fb4362232fb40dd23c4024a0",uri="sip:xxxx.3cx.com",response="d80a77d1edd994508b6111636931a3bc",algorithm=MD5
Supported: replaces
User-Agent: 3CX DialCode Processor
Content-Length: 0

07/10/2018 2:19:13 PM - L:6.2[Line:10002>>0541xxxxxxx] got EarlyMedia Recv 183/INVITE from 95.xxx.xxx.xxx:5060 tid=d04e98767a29c604 Call-ID=dmwO0_EQa4qQJb28S_w4bQ..:
SIP/2.0 183 Progress
Via: SIP/2.0/UDP 10.1.3.147:5060;received=46.x.x.xxx;branch=z9hG4bK-524287-1---d04e98767a29c604;rport=5060
Record-Route: <sip:159.xxx.xxx.xxx;lr;did=e8.e17ff394>
Record-Route: <sip:95.xxx.xxx.xxx;lr;did=e8.1bd31b4>
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>;tag=4196215295-3893441156-380402111-2184942893
From: "90850xxxxxxx" <sip:[email protected]:5060>;tag=ee304f16
Call-ID: dmwO0_EQa4qQJb28S_w4bQ..
CSeq: 2 INVITE
Content-Type: application/sdp
Server: TS-v4.5.1-18fW
Content-Length: 477

v=0
o=- 1531221515 1531221515 IN IP4 82.151.xxx.xxx
s=-
c=IN IP4 95.xxx.xxx.xxx
t=0 0
m=audio 10530 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv
a=silenceSupp:off - - - -
m=audio 0 RTP/AVP 18 0 8 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=inactive
a=silenceSupp:off - - - -
07/10/2018 2:19:13 PM - EarlyMedia from <sip:[email protected]:5060>;tag=4196215295-3893441156-380402111-2184942893 to "90850xxxxxxx" <sip:[email protected]:5060>;tag=ee304f16
07/10/2018 2:19:13 PM - L:6.1[Extn:1020] Sending: OnSendResp Send 183/INVITE from 0.0.0.0:0 tid=dbf8b814a4cb2c52f5d0c2f4f66604ec Call-ID=2281195094@10_1_3_96:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 10.1.3.96:5060;branch=z9hG4bKdbf8b814a4cb2c52f5d0c2f4f66604ec;rport=5060
Contact: <sip:[email protected]:5060>
To: <sip:[email protected];user=phone>;tag=4e2c9a32
From: "Oxxxx Exxx"<sip:[email protected]>;tag=3822409536
Call-ID: 2281195094@10_1_3_96
CSeq: 3 INVITE
Content-Type: application/sdp
Content-Length: 267

v=0
o=3cxPS 130677735424 25400705025 IN IP4 10.1.3.147
s=3cxPS Audio call
c=IN IP4 10.1.3.147
t=0 0
m=audio 7018 RTP/AVP 8 0 9 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=sendrecv
 
Last edited:
Code: 
07/10/2018 2:19:13 PM - SendMsg from <sip:[email protected];user=phone>;tag=4e2c9a32 to "Oxxx Exxx"<sip:[email protected]>;tag=3822409536
07/10/2018 2:19:13 PM - Remote SDP is set for leg L:6.2[Line:10002>>0541xxxxxxx]
07/10/2018 2:19:13 PM - L:6.2[Line:10002>>0541xxxxxxx] got Provisional Recv 183/INVITE from 95.xxx.xxx.xxx:5060 tid=d04e98767a29c604 Call-ID=dmwO0_EQa4qQJb28S_w4bQ..:
SIP/2.0 183 Progress
Via: SIP/2.0/UDP 10.1.3.147:5060;received=46.x.x.xxx;branch=z9hG4bK-524287-1---d04e98767a29c604;rport=5060
Record-Route: <sip:159.xxx.xxx.xxx;lr;did=e8.e17ff394>
Record-Route: <sip:95.xxx.xxx.xxx;lr;did=e8.1bd31b4>
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>;tag=4196215295-3893441156-380402111-2184942893
From: "90850xxxxxxx" <sip:[email protected]:5060>;tag=ee304f16
Call-ID: dmwO0_EQa4qQJb28S_w4bQ..
CSeq: 2 INVITE
Content-Type: application/sdp
Server: TS-v4.5.1-18fW
Content-Length: 477

v=0
o=- 1531221515 1531221515 IN IP4 82.151.xxx.xxx
s=-
c=IN IP4 95.xxx.xxx.xxx
t=0 0
m=audio 10530 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv
a=silenceSupp:off - - - -
m=audio 0 RTP/AVP 18 0 8 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=inactive
a=silenceSupp:off - - - -
07/10/2018 2:19:13 PM - Provisional(183) from <sip:[email protected]:5060>;tag=4196215295-3893441156-380402111-2184942893 to "90850xxxxxxx" <sip:[email protected]:5060>;tag=ee304f16
07/10/2018 2:19:13 PM - [CM505003]: Provider:[Bulutfon 90850xxxxxxx] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [TS-v4.5.1-18fW] PBX contact: [sip:[email protected]:5060]
07/10/2018 2:19:13 PM - [CM503002]: Call(C:6): Alerting Line:10002>>0541xxxxxxx by contact <sip:[email protected]:5060>
07/10/2018 2:19:13 PM - Answer from <sip:[email protected]:5060>;tag=4196215295-3893441156-380402111-2184942893 to "90850xxxxxxx" <sip:[email protected]:5060>;tag=ee304f16
07/10/2018 2:19:12 PM - [CM503025]: Call(C:6): Calling T:Line:10002>>0541xxxxxxx@[Dev:sip:[email protected]:5060] for L:6.1[Extn:1020]
07/10/2018 2:19:12 PM - Route to L:6.2[Line:10002>>0541xxxxxxx] sends Invite-OUT Send Req INVITE from 0.0.0.0:0 tid=b075bc174b27bd1e Call-ID=dmwO0_EQa4qQJb28S_w4bQ..:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---b075bc174b27bd1e;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>
From: "90850xxxxxxx"<sip:[email protected]:5060>;tag=ee304f16
Call-ID: dmwO0_EQa4qQJb28S_w4bQ..
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
Remote-Party-ID: "90850xxxxxxx"<sip:[email protected]:5060>;party=calling
Content-Length: 610

v=0
o=3cxPS 132321902592 42245029889 IN IP4 46.x.x.xxx
s=3cxPS Audio call
c=IN IP4 46.x.x.xxx
t=0 0
m=audio 9008 RTP/SAVP 18 0 8 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:7AeoqjShhQCybK5d1tmw91elwgdhCYOhNtn2AIA7
a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:U3nhbz+/tl3PYuujPoCBEr/Ldp3xjsx+VVLSZgXw
a=sendrecv
m=audio 9008 RTP/AVP 18 0 8 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
 
Code: 
07/10/2018 2:19:12 PM - Outbound CID reformat rule for DN:10002 is disabled (<Rules />)
07/10/2018 2:19:12 PM - Dev(1810899171):[sip:[email protected]:5060 / 90850xxxxxxx]: PBX contact is public IP: <sip:[email protected]:5060>
07/10/2018 2:19:12 PM - Outbound URI is used: sip:95.xxx.xxx.xxx;lr;did=45b.dab2be92
07/10/2018 2:19:12 PM - SLA is globally disabled
07/10/2018 2:19:12 PM - Added leg L:6.2[Line:10002>>0541xxxxxxx]
07/10/2018 2:19:12 PM - [Flow] Call(C:6): making call from L:6.1[Extn:1020] to T:Line:10003>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - [CM503027]: Call(C:6): From: Extn:1020 ("Oxxx Exxx" <sip:[email protected]:5060>)  to  T:Line:10003>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - [CM503004]: Call(C:6): Route 4: from L:6.1[Extn:1020] to T:Line:10003>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - Outbound CID reformat rule for DN:10003 is disabled (<Rules />)
07/10/2018 2:19:12 PM - Line limit check: Current # of calls for line Lc:10003(@Bulutfon 908508851895[<sip:[email protected]:5060>]) is 0; limit is 10
07/10/2018 2:19:12 PM - [Flow] Call(C:6): making call from L:6.1[Extn:1020] to T:Line:10000>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - [CM503027]: Call(C:6): From: Extn:1020 ("Oxxx Exxx" <sip:[email protected]:5060>)  to  T:Line:10000>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - [CM503004]: Call(C:6): Route 3: from L:6.1[Extn:1020] to T:Line:10000>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - Outbound CID reformat rule for DN:10000 is disabled (<Rules />)
07/10/2018 2:19:12 PM - Line limit check: Current # of calls for line Lc:10000(@Bulutfon 90850xxxxxxx[<sip:[email protected]:5060>]) is 0; limit is 10
07/10/2018 2:19:12 PM - [Flow] Call(C:6): making call from L:6.1[Extn:1020] to T:Line:10001>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - [CM503027]: Call(C:6): From: Extn:1020 ("Oxxx Exxx" <sip:[email protected]:5060>)  to  T:Line:10001>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - [CM503004]: Call(C:6): Route 2: from L:6.1[Extn:1020] to T:Line:10001>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - Outbound CID reformat rule for DN:10001 is disabled (<Rules />)
07/10/2018 2:19:12 PM - Line limit check: Current # of calls for line Lc:10001(@Bulutfon 90850xxxxxxx[<sip:[email protected]:5060>]) is 0; limit is 10
07/10/2018 2:19:12 PM - [Flow] Call(C:6): making call from L:6.1[Extn:1020] to T:Line:10002>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - [CM503027]: Call(C:6): From: Extn:1020 ("Oxxx Exxx" <sip:[email protected]:5060>)  to  T:Line:10002>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - [CM503004]: Call(C:6): Route 1: from L:6.1[Extn:1020] to T:Line:10002>>0541xxxxxxx@[Dev:sip:[email protected]:5060]
07/10/2018 2:19:12 PM - Outbound CID reformat rule for DN:10002 is disabled (<Rules />)
07/10/2018 2:19:12 PM - Line limit check: Current # of calls for line Lc:10002(@Bulutfon 90850xxxxxxx[<sip:[email protected]:5060>]) is 0; limit is 10
07/10/2018 2:19:12 PM - Call(C:6): Call from Extn:1020 to 0541xxxxxxx matches outbound rule 'Bulutfon Genel'
07/10/2018 2:19:12 PM - [Flow] Call(C:6): has built target endpoint: Out#:>>Rule{Bulutfon Genel}>>0541xxxxxxx for call from L:6.1[Extn:1020]
07/10/2018 2:19:12 PM - [Flow] Target endpoint for 0541xxxxxxx is Out#:>>Rule{Bulutfon Genel}>>0541xxxxxxx
07/10/2018 2:19:12 PM - Caller '1020' is found in the list of allowed extensions: 0000-9999
07/10/2018 2:19:12 PM - Looking for outbound rule: dialed = [0541xxxxxxx], processed: [0541xxxxxxx]; from-ext:
07/10/2018 2:19:12 PM - [Flow] Building target endpoint to 0541xxxxxxx from "Oxxx Exxx" <sip:[email protected]:5060>
07/10/2018 2:19:12 PM - [CM503010]: Call(C:6): Making route(s) from Extn:1020 to <sip:[email protected]:5060>
07/10/2018 2:19:12 PM - Remote SDP is set for leg L:6.1[Extn:1020]
07/10/2018 2:19:12 PM - OnOffer from "Oxxx Exxx"<sip:[email protected]>;tag=3822409536
07/10/2018 2:19:12 PM - [CM505001]: Endpoint Extn:1020: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [C530 IP/42.231.00.000.000] PBX contact: [sip:[email protected]:5060]
07/10/2018 2:19:12 PM - Inbound DID: ''; Phonebook Name: ''
07/10/2018 2:19:12 PM - [CM500002]: Call(C:6): Info on incoming INVITE from Extn:1020:
Invite-IN Recv Req INVITE from 10.1.3.96:5060 tid=dbf8b814a4cb2c52f5d0c2f4f66604ec Call-ID=2281195094@10_1_3_96:
INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/UDP 10.1.3.96:5060;branch=z9hG4bKdbf8b814a4cb2c52f5d0c2f4f66604ec;rport=5060
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected];user=phone>
From: "Oxxx Exxx"<sip:[email protected]>;tag=3822409536
Call-ID: 2281195094@10_1_3_96
CSeq: 3 INVITE
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY, REFER
Content-Type: application/sdp
Proxy-Authorization: Digest username="xxx",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:[email protected];user=phone",nonce="414dxxxx5273041:exxxxxxdb50cf1",response="13xxxxxx3827610a"
Supported: replaces
User-Agent: C530 IP/42.231.00.000.000
Allow-Events: message-summary, refer, ua-profile, talk, check-sync
Content-Length: 238

v=0
o=1020 5008 19 IN IP4 10.1.3.96
s=Mapping
c=IN IP4 10.1.3.96
t=0 0
m=audio 5008 RTP/AVP 8 0 9 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
07/10/2018 2:19:12 PM - [CM503001]: Call(C:6): Incoming call from Extn:1020 to <sip:[email protected]:5060>
07/10/2018 2:19:12 PM - Outbound URI is used: sip:[email protected]:5060
07/10/2018 2:19:12 PM - IncomingCall: C:6 from <sip:[email protected]:5060> to <sip:[email protected]:5060>
07/10/2018 2:19:12 PM - Added leg L:C:6.1[No endpoint yet]
07/10/2018 2:19:12 PM - Call from "Oxxx Exxx"<sip:[email protected]>;tag=3822409536 to <sip:[email protected];user=phone>;tag=4e2c9a32
07/10/2018 2:19:10 PM - Updating device Dev(584989696):[sip:[email protected]:5060 / 1414] by message: DevUpd Recv Req REGISTER from 10.1.3.98:5060 tid=741760457c0f3ce371ba3be49cae3876 Call-ID=2606847108@10_1_3_98:
REGISTER sip:10.1.3.147 SIP/2.0
Via: SIP/2.0/UDP 10.1.3.98:5060;branch=z9hG4bK741760457c0f3ce371ba3be49cae3876;rport=5060
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: "Mxxx Exxxx" <sip:[email protected]>
From: "Mxxx Exxx"<sip:[email protected]>;tag=801468544
Call-ID: 2606847108@10_1_3_98
CSeq: 23145 REGISTER
Expires: 180
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, SUBSCRIBE, NOTIFY, REFER
Proxy-Authorization: Digest username="xxx",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:10.1.3.147",nonce="414xxc11xxxxx72e61:07708ff1xxxxxx5450d2d50ec4f",response="d7b4c17d2xxxxx187dfaec7d316"
User-Agent: C530 IP/42.231.00.000.000
Content-Length: 0

By the way our SIP provider's IP is marked as 95.xxx.xxx.xxx. But I also see another IP like 159.xxx.xxx.xxx which I do not recognize. Why would be seeing it in here?
 
Last edited:
Now mobile clients can't do it either.
 
SIP INVITE is destined to itsp and you are getting 183 response but you are not hearing any ringback tone ? Have you asked the ITSP if they are seeing anything funny on their end? Have you tried maybe turning crypto off in your SDP and run plain RTP instead of negotiating SRTP?
 
I will agree with Robertos on this. Disable SRTP from the trunk settings and if you still face the issue contact your provider. They may be able to provide some insight as to why calls are failing
 
Could this be an outbound caller ID issue, and a change that your provider has made?

I'm seeing numbers with a leading 9 (90850xxxxxxx) throughout the logs you posted, and i'm guessing that normal dialling has a leading zero.
 
Last edited:
@Robertos and @YiannisH_3CX , I disabled SRTP and restarted services bu nothing has changed. (But I guess it might have happended after I enabled SRTP for testing recently) I am still waiting for the provider to return about their logs. But it's odd that there's literally nothing about these calls in 3CX logs..

@leejor , not it's not a outbound caller ID issue because it was perfectly working with those settings. In fact; there was a caller ID issue and I solved it with the way you see in the logs.
 
If the calls that you've sown in the logs are NOT, the ones you are having an issue with, then that suggests the call is not even leaving the set. In that case, I'd suspect an internal set dialplan that is preventing the digits from being sent to 3CX. That would also explain why calls from 3CX clients continued to work. Why they too failed, later...I don't know.
 
Last edited:
From the provider logs i assume that you have one outbound rule with multiple routes and i see the PBX trying to perform the call from all routes.
Please make sure that in trunk settings / Options the "Allow outbound calls" option is enabled.
You could also hit the "Enable all" button in the SIP trunks tab to make sure that everything is enabled.
If that does not work i would recommend running a wireshark capture and checking the communication with the provider.
Also do you have 4 trunks with the same number?
 
@leejor, it's not possible that call never leaves the handset. Because in the call log, I can see this call as "not answered". But in event log and activitiy log, there's nothing about it.

Oddly, now mobile applications respond all the same. Mobile applications were able to make outbound calls till yesterday, now they are gone too.

@YiannisH_3CX , Yes I have only one outbound rule to route all the calls to trunk and I set 4 of them to be backup of each other. There are 4 different SIP numbers registered as 4 SIP trunks. You just see them all the same because I masked them while sending the log in here. They all have outbound calls enabled; as you know mobile applications were able to make outbound calls already. (Though they can't do it now either.)
 
I solved the issue by setting all the options to default in SIP trunk "Outbound Parameters". I guess this must have been an outbound caller id conflict between the trunk and the extension. But I don't know how it had worked for about 10 days before it got broken suddenly without anything had changed.
 
Glad to see the issue has been resolved although i would not recommend setting all outbound parameters to default. You should either user a supported provider that has all parameters pre-configured in the included template or ask your provider for the correct settings so this does not happen again. SIP messages need to be structured correctly to ensure that the trunk behaves correctly.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,888
Messages
589,565
Members
164,753
Latest member
GemmaC
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom