Toggle sidebar Toggle sidebar

Solved Not accepted here in outbpound call since v16 u6

Status
Not open for further replies.

A.Takacs

Bronze Partner
Joined
Apr 20, 2020
Messages
115
Reaction score
10
Hello

I have an issue with one of our instances where one of the user (with a Yealink T48 - he is the only one with that model) having an error "Not acceptable here" with outbound calls. As far as I can tell this concomitant with the deployment of v16 u6. From memory "not accepted here as a response" generally is points to a codec mis-match between both legs of the call but I guess it might be a different issue.

I have activated debug log and this is a capture at the moment of the call

Code: 
16/09/2020 11:31:39 - CSTA: on info success: CSTA Recv 200/INFO from *.*.*.*:5069 tid=2f50ee0017bb584a Call-ID=ashRr8wFfs0J_sGoeXfJ2g..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.40.251:5060;branch=z9hG4bK-524287-1---2f50ee0017bb584a;rport=5060
Contact: <sip:460@*.*.*.*:5069>
To: <sip:460@*.*.*.*:5069>;tag=4056301561
From: <sip:[email protected]>;tag=c894b513
Call-ID: ashRr8wFfs0J_sGoeXfJ2g..
CSeq: 368 INFO
Content-Type: application/csta+xml
User-Agent: Yealink SIP-T48S 66.85.0.5 805ec03a6b1d
Content-Length: 235

<?xml version="1.0" encoding="utf-8"?>
<SnapshotDeviceResponse xmlns="http://www.ecmainternational.org/standards/ecma-323/csta/ed5">
    <crossRefIDorSnapshotData>
        <snapshotData />
    </crossRefIDorSnapshotData>
</SnapshotDeviceResponse>
16/09/2020 11:31:39 - CSTA: onReadyToSend: CSTA Send Req INFO from 0.0.0.0:0 tid=9a35974775b39555 Call-ID=ashRr8wFfs0J_sGoeXfJ2g..:
INFO sip:460@*.*.*.*:5069 SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---9a35974775b39555;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:460@*.*.*.*:5069>;tag=4056301561
From: <sip:[email protected]>;tag=c894b513
Call-ID: ashRr8wFfs0J_sGoeXfJ2g..
CSeq: 368 INFO
Content-Type: application/csta+xml
Content-Length: 209

<?xml version="1.0" encoding="UTF-8"?>
<SnapshotDevice xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed5">
  <snapshotObject>sip:[email protected]:5060</snapshotObject>
</SnapshotDevice>
16/09/2020 11:31:32 - Dev(342028174):[sip:460@*.*.*.*:5069 / 460]: PBX contact is resolved to public IP: <sip:[email protected]:5060/UDP>
16/09/2020 11:31:32 - Updating device Dev(342028174):[sip:460@*.*.*.*:5069 / 460] by message: DevUpd Recv Req REGISTER from *.*.*.*:5069 tid=1821397591 [email protected]:
REGISTER sip:domain.com:5060 SIP/2.0
Via: SIP/2.0/UDP *.*.*.*:5069;branch=z9hG4bK1821397591;rport=5069
Max-Forwards: 70
Contact: <sip:460@*.*.*.*:5069>
To: "Some User" <sip:[email protected]:5060>
From: "Some User"<sip:[email protected]:5060>;tag=3509207015
Call-ID: [email protected]
CSeq: 608 REGISTER
Expires: 120
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Proxy-Authorization: Digest username="something",realm="3CXPhoneSystem",nonce="414d53595f61db7381:9fdaf05d6c3d2a6c3b2813fa536c18ce",uri="sip:domain.com:5060",response="60dfd975eff4b4af317a3a4865a2bc4f",algorithm=MD5
User-Agent: Yealink SIP-T48S 66.85.0.5 805ec03a6b1d
Allow-Events: talk, hold, conference, refer, check-sync
Mac: 80:5e:c0:3a:6b:1d
Content-Length: 0

16/09/2020 11:30:39 - CSTA: on info success: CSTA Recv 200/INFO from *.*.*.*:5069 tid=d5bc036a664a4241 Call-ID=ashRr8wFfs0J_sGoeXfJ2g..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.40.251:5060;branch=z9hG4bK-524287-1---d5bc036a664a4241;rport=5060
Contact: <sip:460@*.*.*.*:5069>
To: <sip:460@*.*.*.*:5069>;tag=4056301561
From: <sip:[email protected]>;tag=c894b513
Call-ID: ashRr8wFfs0J_sGoeXfJ2g..
CSeq: 367 INFO
Content-Type: application/csta+xml
User-Agent: Yealink SIP-T48S 66.85.0.5 805ec03a6b1d
Content-Length: 235

<?xml version="1.0" encoding="utf-8"?>
<SnapshotDeviceResponse xmlns="http://www.ecmainternational.org/standards/ecma-323/csta/ed5">
    <crossRefIDorSnapshotData>
        <snapshotData />
    </crossRefIDorSnapshotData>
</SnapshotDeviceResponse>
16/09/2020 11:30:39 - CSTA: onReadyToSend: CSTA Send Req INFO from 0.0.0.0:0 tid=23f4df39666a2e46 Call-ID=ashRr8wFfs0J_sGoeXfJ2g..:
INFO sip:460@*.*.*.*:5069 SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---23f4df39666a2e46;rport
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:460@*.*.*.*:5069>;tag=4056301561
From: <sip:[email protected]>;tag=c894b513
Call-ID: ashRr8wFfs0J_sGoeXfJ2g..
CSeq: 367 INFO
Content-Type: application/csta+xml
Content-Length: 209

<?xml version="1.0" encoding="UTF-8"?>
<SnapshotDevice xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed5">
  <snapshotObject>sip:[email protected]:5060</snapshotObject>
</SnapshotDevice>
16/09/2020 11:30:32 - Dev(342028174):[sip:460@*.*.*.*:5069 / 460]: PBX contact is resolved to public IP: <sip:[email protected]:5060/UDP>
16/09/2020 11:30:32 - Updating device Dev(342028174):[sip:460@*.*.*.*:5069 / 460] by message: DevUpd Recv Req REGISTER from *.*.*.*:5069 tid=3674624588 [email protected]:
REGISTER sip:domain.com:5060 SIP/2.0
Via: SIP/2.0/UDP *.*.*.*:5069;branch=z9hG4bK3674624588;rport=5069
Max-Forwards: 70
Contact: <sip:460@*.*.*.*:5069>
To: "Some User" <sip:[email protected]:5060>
From: "Some User"<sip:[email protected]:5060>;tag=3509207015
Call-ID: [email protected]
CSeq: 606 REGISTER
Expires: 120
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Proxy-Authorization: Digest username="something",realm="3CXPhoneSystem",nonce="414d53595f61db3772:c78b8ff930c2e40f4e2efe40721e0d50",uri="sip:domain.com:5060",response="f3fd1a1f8644f724ea67ba70321b7a15",algorithm=MD5
User-Agent: Yealink SIP-T48S 66.85.0.5 805ec03a6b1d
Allow-Events: talk, hold, conference, refer, check-sync
Mac: 80:5e:c0:3a:6b:1d
Content-Length: 0

16/09/2020 11:30:05 - Updating device Dev(969353775):[sip:[email protected]:5063;rinstance=136ca11bbf6ba955 / 90000] by message: DevUpd Recv Req REGISTER from 127.0.0.1:5063 tid=75a00e7562644b74 Call-ID=7I3_HIitCxjXNYovyST6Rg..:
REGISTER sip:127.0.0.1:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5063;branch=z9hG4bK-524287-1---75a00e7562644b74;rport=5063
Max-Forwards: 70
Contact: <sip:[email protected]:5063;rinstance=136ca11bbf6ba955>
To: <sip:[email protected]:5060>
From: <sip:[email protected]:5060>;tag=76741657
Call-ID: 7I3_HIitCxjXNYovyST6Rg..
CSeq: 666 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Proxy-Authorization: Digest username="90000",realm="3CXPhoneSystem",nonce="414d53595f61db1d63:2030456040b75a37aa460900ece5291b",uri="sip:127.0.0.1:5060",response="5526099af340aafeb6633268b8d717a1",algorithm=MD5
Supported: replaces
User-Agent: 3CX WebRTC proxy
Content-Length: 0

16/09/2020 11:29:58 - Updating device Dev(1581422517):[sip:[email protected]:5483;rinstance=6ea249324e77074e / QCB] by message: DevUpd Recv Req REGISTER from 127.0.0.1:5483 tid=0fae68486347b611 Call-ID=u0w0jp2etO-illUyO3LX_w..:
REGISTER sip:127.0.0.1:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5483;branch=z9hG4bK-524287-1---0fae68486347b611;rport=5483
Max-Forwards: 70
Contact: <sip:[email protected]:5483;rinstance=6ea249324e77074e>
To: "DRQCB:"<sip:[email protected]:5060>
From: "DRQCB:"<sip:[email protected]:5060>;tag=ca75e61b
Call-ID: u0w0jp2etO-illUyO3LX_w..
CSeq: 136 REGISTER
Expires: 300
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Proxy-Authorization: Digest username="QCB",realm="3CXPhoneSystem",nonce="414d53595f61db1682:2290994abae670d4608c1fac017cf8fc",uri="sip:127.0.0.1:5060",response="026b4e319feb5d32c8810aa4db5c4052",algorithm=MD5
Supported: replaces
User-Agent: 3CX QueueCallback
Content-Length: 0

Can anyone more experience than me pinpoint the issue ?
 
Does this user have an outbound caller ID set under his extension?
 
Yes - tried to remove it though without change
 
Is this for all extensions or just this one? Is the phone using default template?

who is your SIP provider? and wht is the caller ID youre sending under SIP Settings?

Check to see 3CX is sending what your SIP provider is looking for.
 
Is this for all extensions or just this one? Is the phone using default template?
Click to expand...

Apparently only this phone (but it is the only T48 we have - the other phone (T2xxx) seem to work fine. This one also worked until (it seems) u6.
Default template.

who is your SIP provider? and wht is the caller ID youre sending under SIP Settings?
Click to expand...

Unfortunately an unsupported SIP provider and one that is not willing to help

Check to see 3CX is sending what your SIP provider is looking for.
Click to expand...

Not sure what you mean here ?
 
Are you using the default template for the phone?

From your logs above it looks like your sending EXTNUMBER@ to your SIP provider

if you look at the log from a phone that works, what does the from say?

Also, what have you got in the From: User Part under Outbound Parameters in your SIP settings?
 
Doing further tests it works fine with 3cx softphone and from WebRTC Browser. So definitely specific to that phone.
 
I would try a factory reset and reprovision.

What is the codec order of your phone?

Have you got "disallow video calls" checked under SIP trunk options?
 
yup that did the trick (reprovisioning) ! thanks !
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,322
Messages
591,889
Members
165,470
Latest member
Robert Lee
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom