Weiterleitung zu Telekom-Handynummern funktionieren nicht

apoo

Silver Partner
Mitglied seit
9. April 2018
Beiträge
60
Hallo zusammen,

wir haben eine Call Queue welche so konfiguriert ist, dass diese nach 20 Sekunden einen "Forward to Outside Number" auf meine Handynummer macht.

Trage ich statt meiner Handynummer eine Handynummer von EPlus/O2 ein, funktioniert dies einwandfrei, trage ich eine beliebige Handynummer aus dem Telekom Netz ein, wird der Anruf aufgelegt sobald ich ran gehe.

Hat jemand eine Ahnung woran dies liegen könnte? Vor V15.5 lief dies einwandfrei, aber kann natürlich auch an etwas anderem liegen...

Viele Grüße,
Johnny


Hier noch das Activity Log von einem Anruf bei dem automatisch aufgelegt wird:
Code:
03/07/2019 4:30:15 PM - Leg L:377.1[Line:10000<<{{MyMobileNr}}] is terminated: Cause: BYE from local
03/07/2019 4:30:15 PM - [CM503008]: Call(C:377): Call is terminated
03/07/2019 4:30:15 PM - Leg L:377.4[Line:10000>>{{MyMobileNr}}] is terminated: Cause: BYE from {{IpFromSipProvider}}:5064
03/07/2019 4:30:15 PM - Leg L:377.3[Queue:8004] is terminated: Cause: BYE from 127.0.0.1:5488
03/07/2019 4:30:15 PM - [CM503007]: Call(C:377): Line:10000>>{{MyMobileNr}} has joined, contact <sip:004989{{OurOfficeNr}}@{{OurTrunkProvider}}:5064>
03/07/2019 4:30:15 PM - L:377.4[Line:10000>>{{MyMobileNr}}] has joined to L:377.1[Line:10000<<{{MyMobileNr}}]
03/07/2019 4:30:12 PM - Currently active calls - 1: [377]
03/07/2019 4:30:07 PM - [CM505003]: Provider:[{{TrunkName}}] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:004989{{OurOfficeNr}}@94.130.162.52:5060]
03/07/2019 4:30:07 PM - [CM503002]: Call(C:377): Alerting Line:10000>>{{MyMobileNr}} by contact <sip:004989{{OurOfficeNr}}@{{OurTrunkProvider}}:5064>
03/07/2019 4:30:05 PM - [CM503025]: Call(C:377): Calling T:Line:10000>>{{MyMobileNr}}@[Dev:sip:004989{{OurOfficeNr}}@{{OurTrunkProvider}}:5064] for L:377.1[Line:10000<<{{MyMobileNr}}]
03/07/2019 4:30:05 PM - [CM503027]: Call(C:377): From: Line:10000<<{{MyMobileNr}} (<sip:{{MyMobileNr}}@{{Our3cxFQDN}}:5060>)  to  T:Line:10000>>{{MyMobileNr}}@[Dev:sip:004989{{OurOfficeNr}}@{{OurTrunkProvider}}:5064]
03/07/2019 4:30:05 PM - [CM503004]: Call(C:377): Route 1: from L:377.1[Line:10000<<{{MyMobileNr}}] to T:Line:10000>>{{MyMobileNr}}@[Dev:sip:004989{{OurOfficeNr}}@{{OurTrunkProvider}}:5064]
03/07/2019 4:30:05 PM - Line limit check: Current # of calls for line Lc:10000(@{{TrunkName}}[<sip:004989{{OurOfficeNr}}@{{OurTrunkProvider}}:5064>]) is 1; limit is 100
03/07/2019 4:30:05 PM - Call(C:377): Call from Line:10000<<{{MyMobileNr}} to {{MyMobileNr}} matches outbound rule 'Outgoing'
03/07/2019 4:30:05 PM - [Flow] Call(C:377): has built target endpoint: Out#:>>Rule{Outgoing}>>{{MyMobileNr}} for call from L:377.1[Line:10000<<{{MyMobileNr}}]
03/07/2019 4:30:05 PM - [Flow] Target endpoint for {{MyMobileNr}} is Out#:>>Rule{Outgoing}>>{{MyMobileNr}}
03/07/2019 4:30:05 PM - [CM503010]: Call(C:377): Making route(s) from Line:10000<<{{MyMobileNr}} to <sip:{{MyMobileNr}}@127.0.0.1:5060>
 
Hallo Johnny,

Bekommst du vielleicht auch eine Fehlermeldung in den Ereignisprotokoll?
 
Nein, im Ereignisprotokoll steht nur der Lost Call, weil wir ja nicht ran gegangen sind damit umgeleitet wird

Im Verbose Log ist mir aber die folgende Stelle aufgefallen:
03/08/2019 8:44:04 AM - Blocking refers for the Call(C:387)
03/08/2019 8:44:04 AM - Call(C:387) is terminated
03/08/2019 8:44:04 AM - Leg L:387.3[Queue:8004] is terminated: Cause: BYE from 127.0.0.1:5488

Was heißt das?
Ist ansonsten vielleicht im Verbose Log zu sehen warum dies passiert?

03/08/2019 8:44:04 AM - Leg L:387.1[Line:10000<<{{CallerNr}}] is terminated: Cause: BYE from local
03/08/2019 8:44:04 AM - L:387.1[Line:10000<<{{CallerNr}}] got Terminated Send Req BYE from 0.0.0.0:0 tid=96328076254ca807 Call-ID=SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1:
BYE sip:3C06448F-5C821D1F000DCD9A-7D3D3700@{{TrunkProviderIp}}:5064;transport=udp SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---96328076254ca807;rport
Max-Forwards: 70
Contact: <sip:{{RedirectionNr}}@{{TkIp}}:5060>
To: <sip:{{CallerNr}}@{{TrunkProviderUrl}}>;tag=64BAF5C9-5C821D1F000DB8F2-5788A700
From: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}>;tag=d07c8920
Call-ID: SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1
CSeq: 6 BYE
User-Agent: 3CXPhoneSystem 15.5.15502.6 (15502)
Content-Length: 0

03/08/2019 8:44:04 AM - Terminated from <sip:{{CallerNr}}@{{TrunkProviderUrl}}>;tag=64BAF5C9-5C821D1F000DB8F2-5788A700 to <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}>;tag=d07c8920; reason: LocalBye
03/08/2019 8:44:04 AM - L:387.1[Line:10000<<{{CallerNr}}] Sending: OnSendReq Send Req BYE from 0.0.0.0:0 tid=2e0512126737ae4d Call-ID=SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1:
BYE sip:3C06448F-5C821D1F000DCD9A-7D3D3700@{{TrunkProviderIp}}:5064;transport=udp SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---2e0512126737ae4d;rport
Max-Forwards: 70
Contact: <sip:{{RedirectionNr}}@{{TkIp}}:5060>
To: <sip:{{CallerNr}}@{{TrunkProviderUrl}}>;tag=64BAF5C9-5C821D1F000DB8F2-5788A700
From: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}>;tag=d07c8920
Call-ID: SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1
CSeq: 6 BYE
Content-Length: 0

03/08/2019 8:44:04 AM - SendMsg from <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}>;tag=d07c8920 to <sip:{{CallerNr}}@{{TrunkProviderUrl}}>;tag=64BAF5C9-5C821D1F000DB8F2-5788A700
03/08/2019 8:44:04 AM - [CM503008]: Call(C:387): Call is terminated
03/08/2019 8:44:04 AM - Blocking refers for the Call(C:387)
03/08/2019 8:44:04 AM - Call(C:387) is terminated
03/08/2019 8:44:04 AM - Leg L:387.3[Queue:8004] is terminated: Cause: BYE from 127.0.0.1:5488
03/08/2019 8:44:04 AM - L:387.3[Queue:8004] got Terminated Recv Req BYE from 127.0.0.1:5488 tid=0a624c206964df23 Call-ID=U1bp6uFUISioRasOh3VNiA..:
BYE sip:{{CallerNr}}@127.0.0.1:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---0a624c206964df23;rport=5488
Max-Forwards: 70
Contact: <sip:[email protected]:5488;rinstance=d0403e624c991c0a>
To: <sip:{{CallerNr}}@127.0.0.1:5060;nf=e>;tag=ee5b1b6b
From: <sip:[email protected]>;tag=9a763a7a
Call-ID: U1bp6uFUISioRasOh3VNiA..
CSeq: 6 BYE
User-Agent: 3CX Queue Manager (q=8004)
Reason: SIP;text=User Hung Up
Content-Length: 0

03/08/2019 8:44:04 AM - Terminated from <sip:[email protected]>;tag=9a763a7a to <sip:{{CallerNr}}@127.0.0.1:5060;nf=e>;tag=ee5b1b6b; reason: RemoteBye
03/08/2019 8:44:04 AM - L:387.3[Queue:8004] Sending: OnSendResp Send 200/BYE from 0.0.0.0:0 tid=0a624c206964df23 Call-ID=U1bp6uFUISioRasOh3VNiA..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---0a624c206964df23;rport=5488
Contact: <sip:{{CallerNr}}@127.0.0.1:5060>
To: <sip:{{CallerNr}}@127.0.0.1:5060;nf=e>;tag=ee5b1b6b
From: <sip:[email protected]>;tag=9a763a7a
Call-ID: U1bp6uFUISioRasOh3VNiA..
CSeq: 6 BYE
Content-Length: 0

03/08/2019 8:44:04 AM - SendMsg from <sip:{{CallerNr}}@127.0.0.1:5060;nf=e>;tag=ee5b1b6b to <sip:[email protected]>;tag=9a763a7a
03/08/2019 8:44:04 AM - Default best-route IP is determined as {{LocaleIp}}
03/08/2019 8:44:04 AM - Leg L:387.4[Line:10000>>{{RedirectionNr}}] is terminated: Cause: BYE from {{TrunkProviderIp}}:5064
03/08/2019 8:44:04 AM - L:387.4[Line:10000>>{{RedirectionNr}}] got Terminated Recv Req BYE from {{TrunkProviderIp}}:5064 tid=FMdPraw7cU3W7 Call-ID=ft3qqyamaXv1dWgqp5ac0g..:
BYE sip:004989{{OurNumber}}@{{TkIp}}:5060 SIP/2.0
Via: SIP/2.0/UDP {{TrunkProviderIp}}:5064;branch=z9hG4bKFMdPraw7cU3W7;rport=5064
Max-Forwards: 67
To: "{{CallerNr}}" <sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
From: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700
Call-ID: ft3qqyamaXv1dWgqp5ac0g..
CSeq: 10 BYE
Reason: Q.850;cause=41, SIP;cause=503;text="Service Unavailable"
Content-Length: 0

03/08/2019 8:44:04 AM - Terminated from <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700 to "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09; reason: RemoteBye
03/08/2019 8:44:04 AM - L:387.4[Line:10000>>{{RedirectionNr}}] Sending: OnSendResp Send 200/BYE from 0.0.0.0:0 tid=FMdPraw7cU3W7 Call-ID=ft3qqyamaXv1dWgqp5ac0g..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP {{TrunkProviderIp}}:5064;branch=z9hG4bKFMdPraw7cU3W7;rport=5064
Contact: <sip:004989{{OurNumber}}@{{TkIp}}:5060>
To: "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
From: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700
Call-ID: ft3qqyamaXv1dWgqp5ac0g..
CSeq: 10 BYE
Content-Length: 0

03/08/2019 8:44:04 AM - SendMsg from "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09 to <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700
03/08/2019 8:44:03 AM - L:387.4[Line:10000>>{{RedirectionNr}}] Sending: OnSendReq Send Req ACK from 0.0.0.0:0 tid=a6014a16ee0baf5e Call-ID=ft3qqyamaXv1dWgqp5ac0g..:
ACK sip:52469044-5C821D3C00032C5B-28212700@{{TrunkProviderIp}}:5064;transport=udp SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---a6014a16ee0baf5e;rport
Max-Forwards: 70
Contact: <sip:004989{{OurNumber}}@{{TkIp}}:5060>
To: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700
From: "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
Call-ID: ft3qqyamaXv1dWgqp5ac0g..
CSeq: 2 ACK
Content-Type: application/sdp
Content-Length: 131

v=0
o=3cxPS 261607129088 264660582401 IN IP4 {{TkIp}}
s=3cxPS Audio call
c=IN IP4 {{TkIp}}
t=0 0
m=audio 0 RTP/AVP
03/08/2019 8:44:03 AM - SendMsg from "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09 to <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700
03/08/2019 8:44:03 AM - Providing SDP for Refer.Target
03/08/2019 8:44:03 AM - Reneg. from L:387.1[Line:10000<<{{CallerNr}}], answer
03/08/2019 8:44:03 AM - Remote SDP is set for leg L:387.1[Line:10000<<{{CallerNr}}]
03/08/2019 8:44:03 AM - Answer SDP arrived on Leg L:387.1[Line:10000<<{{CallerNr}}];
OnAnswer Recv 200/INVITE from {{TrunkProviderIp}}:5064 tid=ac0105291179f544 Call-ID=SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1:
SIP/2.0 200 OK
Via: SIP/2.0/UDP {{LocaleIp}}:5060;branch=z9hG4bK-524287-1---ac0105291179f544;rport=5060;received={{TkIp}}
Contact: <sip:3C06448F-5C821D1F000DCD9A-7D3D3700@{{TrunkProviderIp}}:5064;transport=udp>
To: <sip:{{CallerNr}}@{{TrunkProviderUrl}}>;tag=64BAF5C9-5C821D1F000DB8F2-5788A700
From: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}>;tag=d07c8920
Call-ID: SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1
CSeq: 5 INVITE
Content-Type: application/sdp
Content-Length: 218

v=0
o=- 36885944 36885948 IN IP4 {{TrunkProviderIp}}
s=-
c=IN IP4 {{TrunkProviderIp}}
t=0 0
m=audio 39712 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=direction:both
a=sendrecv
03/08/2019 8:44:03 AM - L:387.1[Line:10000<<{{CallerNr}}] Sending: OnSendReq Send Req ACK from 0.0.0.0:0 tid=f33dce624308f719 Call-ID=SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1:
ACK sip:3C06448F-5C821D1F000DCD9A-7D3D3700@{{TrunkProviderIp}}:5064;transport=udp SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---f33dce624308f719;rport
Max-Forwards: 70
Contact: <sip:{{RedirectionNr}}@{{TkIp}}:5060>
To: <sip:{{CallerNr}}@{{TrunkProviderUrl}}>;tag=64BAF5C9-5C821D1F000DB8F2-5788A700
From: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}>;tag=d07c8920
Call-ID: SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1
CSeq: 5 ACK
Content-Length: 0

03/08/2019 8:44:03 AM - SendMsg from <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}>;tag=d07c8920 to <sip:{{CallerNr}}@{{TrunkProviderUrl}}>;tag=64BAF5C9-5C821D1F000DB8F2-5788A700
03/08/2019 8:44:03 AM - Sending: OnSendReq Send Req NOTIFY from 0.0.0.0:0 tid=b75bc671bc502728 Call-ID=U1bp6uFUISioRasOh3VNiA..:
NOTIFY sip:[email protected]:5488;rinstance=d0403e624c991c0a SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---b75bc671bc502728;rport
Max-Forwards: 70
Contact: <sip:{{CallerNr}}@127.0.0.1:5060>
To: <sip:[email protected]>;tag=9a763a7a
From: <sip:{{CallerNr}}@127.0.0.1:5060;nf=e>;tag=ee5b1b6b
Call-ID: U1bp6uFUISioRasOh3VNiA..
CSeq: 3 NOTIFY
Content-Type: message/sipfrag
Subscription-State: terminated;reason=noresource
Event: refer;id=4
Content-Length: 18

SIP/2.0 200 OK

03/08/2019 8:44:03 AM - [CM503007]: Call(C:387): Line:10000>>{{RedirectionNr}} has joined, contact <sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>
03/08/2019 8:44:03 AM - ~Target=VoIPline:{{RedirectionNr}}@(Ln.10000@{{TrunkName}})
03/08/2019 8:44:03 AM - L:387.1[Line:10000<<{{CallerNr}}] Sending: OnSendReq Send Req INVITE from 0.0.0.0:0 tid=8b3f1f6d70098b12 Call-ID=SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1:
INVITE sip:3C06448F-5C821D1F000DCD9A-7D3D3700@{{TrunkProviderIp}}:5064;transport=udp SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---8b3f1f6d70098b12;rport
Max-Forwards: 70
Contact: <sip:{{RedirectionNr}}@{{TkIp}}:5060>
To: <sip:{{CallerNr}}@{{TrunkProviderUrl}}>;tag=64BAF5C9-5C821D1F000DB8F2-5788A700
From: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}>;tag=d07c8920
Call-ID: SBCsnlh924l7h9n5h95qh1aels75he7a5sr@SoftX3000_b2b-1
CSeq: 5 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 15.5.15502.6 (15502)
Content-Length: 250

v=0
o=3cxPS 368981311488 305227890693 IN IP4 {{TkIp}}
s=3cxPS Audio call
c=IN IP4 {{TkIp}}
t=0 0
m=audio 9538 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
03/08/2019 8:44:03 AM - SendMsg from <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}>;tag=d07c8920 to <sip:{{CallerNr}}@{{TrunkProviderUrl}}>;tag=64BAF5C9-5C821D1F000DB8F2-5788A700
03/08/2019 8:44:03 AM - Outbound CID reformat rule for DN:10000 is disabled (<Rules />)
03/08/2019 8:44:03 AM - ~Route=Dev:sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064
03/08/2019 8:44:03 AM - L:387.4[Line:10000>>{{RedirectionNr}}] has joined to L:387.1[Line:10000<<{{CallerNr}}]
03/08/2019 8:44:03 AM - OnOffer from <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>
03/08/2019 8:44:03 AM - L:387.4[Line:10000>>{{RedirectionNr}}] got Connected.UAC Recv 200/INVITE from {{TrunkProviderIp}}:5064 tid=6f79e337d317a86d Call-ID=ft3qqyamaXv1dWgqp5ac0g..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP {{LocaleIp}}:5060;branch=z9hG4bK-524287-1---6f79e337d317a86d;rport=5060;received={{TkIp}}
Contact: <sip:52469044-5C821D3C00032C5B-28212700@{{TrunkProviderIp}}:5064;transport=udp>
To: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700
From: "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
Call-ID: ft3qqyamaXv1dWgqp5ac0g..
CSeq: 2 INVITE
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Allow: INVITE, ACK, CANCEL, BYE, REGISTER, SUBSCRIBE, NOTIFY, PRACK, UPDATE, OPTIONS, MESSAGE, PUBLISH
Content-Type: application/sdp
Content-Length: 202

v=0
o=- 962403 335179 IN IP4 {{TrunkProviderIp}}
s=-
c=IN IP4 {{TrunkProviderIp}}
t=0 0
m=audio 39042 RTP/AVP 100
a=rtpmap:100 telephone-event/8000
a=fmtp:100 0-15
a=direction:both
a=sendrecv
a=ptime:20
03/08/2019 8:44:03 AM - Connected(UAC) from <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700 to "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
03/08/2019 8:44:03 AM - Remote SDP is set for leg L:387.4[Line:10000>>{{RedirectionNr}}]
03/08/2019 8:44:03 AM - Offer SDP arrived on Leg L:387.4[Line:10000>>{{RedirectionNr}}];
OnOffer Recv 200/INVITE from {{TrunkProviderIp}}:5064 tid=6f79e337d317a86d Call-ID=ft3qqyamaXv1dWgqp5ac0g..:
SIP/2.0 200 OK
Via: SIP/2.0/UDP {{LocaleIp}}:5060;branch=z9hG4bK-524287-1---6f79e337d317a86d;rport=5060;received={{TkIp}}
Contact: <sip:52469044-5C821D3C00032C5B-28212700@{{TrunkProviderIp}}:5064;transport=udp>
To: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700
From: "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
Call-ID: ft3qqyamaXv1dWgqp5ac0g..
CSeq: 2 INVITE
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Allow: INVITE, ACK, CANCEL, BYE, REGISTER, SUBSCRIBE, NOTIFY, PRACK, UPDATE, OPTIONS, MESSAGE, PUBLISH
Content-Type: application/sdp
Content-Length: 202

v=0
o=- 962403 335179 IN IP4 {{TrunkProviderIp}}
s=-
c=IN IP4 {{TrunkProviderIp}}
t=0 0
m=audio 39042 RTP/AVP 100
a=rtpmap:100 telephone-event/8000
a=fmtp:100 0-15
a=direction:both
a=sendrecv
a=ptime:20
03/08/2019 8:44:01 AM - Currently active calls - 1: [387]
03/08/2019 8:44:01 AM - L:387.4[Line:10000>>{{RedirectionNr}}] got Provisional Recv 183/INVITE from {{TrunkProviderIp}}:5064 tid=6f79e337d317a86d Call-ID=ft3qqyamaXv1dWgqp5ac0g..:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP {{LocaleIp}}:5060;branch=z9hG4bK-524287-1---6f79e337d317a86d;rport=5060;received={{TkIp}}
Contact: <sip:52469044-5C821D3C00032C5B-28212700@{{TrunkProviderIp}}:5064;transport=udp>
To: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700
From: "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
Call-ID: ft3qqyamaXv1dWgqp5ac0g..
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, BYE, REGISTER, SUBSCRIBE, NOTIFY, PRACK, UPDATE, OPTIONS, MESSAGE, PUBLISH
Content-Length: 0

03/08/2019 8:44:01 AM - Provisional(183) from <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700 to "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
03/08/2019 8:43:58 AM - Updating device Dev(2034203768):[sip:[email protected]:5483;rinstance=d0163ab6a59c5a61 / 7000] by message: DevUpd Recv Req REGISTER from 127.0.0.1:5483 tid=274f4821d4311518 Call-ID=Sl1CkIAKnI3kV2QYb9KRSA..:
REGISTER sip:127.0.0.1:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5483;branch=z9hG4bK-524287-1---274f4821d4311518;rport=5483
Max-Forwards: 70
Contact: <sip:[email protected]:5483;rinstance=d0163ab6a59c5a61>
To: "Conference Room7000:"<sip:[email protected]:5060>
From: "Conference Room7000:"<sip:[email protected]:5060>;tag=4613fc5f
Call-ID: Sl1CkIAKnI3kV2QYb9KRSA..
CSeq: 36170 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Proxy-Authorization: Digest username="7000",realm="3CXPhoneSystem",nonce="414d535c1292ae3e46:f8f43778c61e49b75ebab530493886e2",uri="sip:127.0.0.1:5060",response="2d26c354c5fbe0a95e0298e4b101c5fd",algorithm=MD5
Supported: replaces
User-Agent: 3CX Conference Room
Content-Length: 0

03/08/2019 8:43:57 AM - L:387.4[Line:10000>>{{RedirectionNr}}] got Provisional Recv 183/INVITE from {{TrunkProviderIp}}:5064 tid=6f79e337d317a86d Call-ID=ft3qqyamaXv1dWgqp5ac0g..:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP {{LocaleIp}}:5060;branch=z9hG4bK-524287-1---6f79e337d317a86d;rport=5060;received={{TkIp}}
Contact: <sip:52469044-5C821D3C00032C5B-28212700@{{TrunkProviderIp}}:5064;transport=udp>
To: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700
From: "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
Call-ID: ft3qqyamaXv1dWgqp5ac0g..
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, BYE, REGISTER, SUBSCRIBE, NOTIFY, PRACK, UPDATE, OPTIONS, MESSAGE, PUBLISH
Content-Length: 0

03/08/2019 8:43:57 AM - Provisional(183) from <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700 to "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
03/08/2019 8:43:57 AM - [CM505003]: Provider:[{{TrunkName}}] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:004989{{OurNumber}}@{{TkIp}}:5060]
03/08/2019 8:43:57 AM - [CM503002]: Call(C:387): Alerting Line:10000>>{{RedirectionNr}} by contact <sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>
03/08/2019 8:43:57 AM - Answer from <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>;tag=7E2DA73C-5C821D3C000493CA-4CF23700 to "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
03/08/2019 8:43:56 AM - [CM503025]: Call(C:387): Calling T:Line:10000>>{{RedirectionNr}}@[Dev:sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064] for L:387.1[Line:10000<<{{CallerNr}}]
03/08/2019 8:43:56 AM - Route to L:387.4[Line:10000>>{{RedirectionNr}}] sends Invite-OUT Send Req INVITE from 0.0.0.0:0 tid=444cec61f340cd47 Call-ID=ft3qqyamaXv1dWgqp5ac0g..:
INVITE sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064 SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---444cec61f340cd47;rport
Max-Forwards: 70
Contact: <sip:004989{{OurNumber}}@{{TkIp}}:5060>
To: <sip:{{RedirectionNr}}@{{TrunkProviderUrl}}:5064>
From: "{{CallerNr}}"<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>;tag=14229d09
Call-ID: ft3qqyamaXv1dWgqp5ac0g..
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Supported: replaces, timer
Content-Length: 0

03/08/2019 8:43:56 AM - Outbound CID reformat rule for DN:10000 is disabled (<Rules />)
03/08/2019 8:43:56 AM - Outbound CID reformat rule for DN:10000 is disabled (<Rules />)
03/08/2019 8:43:56 AM - Dev(1137261301):[sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064 / 004989{{OurNumber}}]: PBX contact is public IP: <sip:004989{{OurNumber}}@{{TkIp}}:5060>
03/08/2019 8:43:56 AM - Outbound URI is used: sip:004989{{OurNumber}}@{{TrunkProviderIp}}:5064
03/08/2019 8:43:56 AM - SLA is globally disabled
03/08/2019 8:43:56 AM - Added leg L:387.4[Line:10000>>{{RedirectionNr}}]
03/08/2019 8:43:56 AM - Sending: OnSendReq Send Req NOTIFY from 0.0.0.0:0 tid=26513d6e19334e79 Call-ID=U1bp6uFUISioRasOh3VNiA..:
NOTIFY sip:[email protected]:5488;rinstance=d0403e624c991c0a SIP/2.0
Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---26513d6e19334e79;rport
Max-Forwards: 70
Contact: <sip:{{CallerNr}}@127.0.0.1:5060>
To: <sip:[email protected]>;tag=9a763a7a
From: <sip:{{CallerNr}}@127.0.0.1:5060;nf=e>;tag=ee5b1b6b
Call-ID: U1bp6uFUISioRasOh3VNiA..
CSeq: 2 NOTIFY
Content-Type: message/sipfrag
Subscription-State: init;expires=60
Event: refer;id=4
Content-Length: 22

SIP/2.0 100 Trying

03/08/2019 8:43:56 AM - Sending: OnSendResp Send 202/REFER from 0.0.0.0:0 tid=4568850da8177b6e Call-ID=U1bp6uFUISioRasOh3VNiA..:
SIP/2.0 202 OK
Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---4568850da8177b6e;rport=5488
Contact: <sip:{{CallerNr}}@127.0.0.1:5060>
To: <sip:{{CallerNr}}@127.0.0.1:5060;nf=e>;tag=ee5b1b6b
From: <sip:[email protected]>;tag=9a763a7a
Call-ID: U1bp6uFUISioRasOh3VNiA..
CSeq: 4 REFER
Expires: 60
Content-Length: 0

03/08/2019 8:43:56 AM - [Flow] Call(C:387): making call from L:387.1[Line:10000<<{{CallerNr}}] to T:Line:10000>>{{RedirectionNr}}@[Dev:sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064]
03/08/2019 8:43:56 AM - [CM503027]: Call(C:387): From: Line:10000<<{{CallerNr}} (<sip:{{CallerNr}}@{{Our3cxFQDN}}:5060>) to T:Line:10000>>{{RedirectionNr}}@[Dev:sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064]
03/08/2019 8:43:56 AM - [CM503004]: Call(C:387): Route 1: from L:387.1[Line:10000<<{{CallerNr}}] to T:Line:10000>>{{RedirectionNr}}@[Dev:sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064]
03/08/2019 8:43:56 AM - Outbound CID reformat rule for DN:10000 is disabled (<Rules />)
03/08/2019 8:43:56 AM - Line limit check: Current # of calls for line Lc:10000(@{{TrunkName}}[<sip:004989{{OurNumber}}@{{TrunkProviderUrl}}:5064>]) is 1; limit is 100
03/08/2019 8:43:56 AM - Call(C:387): Call from Line:10000<<{{CallerNr}} to {{RedirectionNr}} matches outbound rule 'Outgoing'
03/08/2019 8:43:56 AM - [Flow] Call(C:387): has built target endpoint: Out#:>>Rule{Outgoing}>>{{RedirectionNr}} for call from L:387.1[Line:10000<<{{CallerNr}}]
03/08/2019 8:43:56 AM - [Flow] Target endpoint for {{RedirectionNr}} is Out#:>>Rule{Outgoing}>>{{RedirectionNr}}
03/08/2019 8:43:56 AM - Looking for outbound rule: dialed = [{{RedirectionNr}}], processed: [{{RedirectionNr}}]; from-ext:
03/08/2019 8:43:56 AM - [Flow] Building target endpoint to {{RedirectionNr}} from <sip:{{CallerNr}}@{{Our3cxFQDN}}:5060>
03/08/2019 8:43:56 AM - [CM503010]: Call(C:387): Making route(s) from Line:10000<<{{CallerNr}} to <sip:{{RedirectionNr}}@127.0.0.1:5060>
03/08/2019 8:43:56 AM - L:387.1[Line:10000<<{{CallerNr}}]: Updated OutCID: '004989{{OurNumber}}00' and DNName: ''
03/08/2019 8:43:56 AM - Call(C:387): Referred(i): src=<sip:{{CallerNr}}@{{Our3cxFQDN}}:5060;nf=e>; dst=<sip:[email protected]:5060>
03/08/2019 8:43:56 AM - [Flow] Refer: RefTo=<sip:{{RedirectionNr}}@127.0.0.1:5060>; was call from=<sip:[email protected]:5060> to=<sip:{{CallerNr}}@127.0.0.1:5060>
03/08/2019 8:43:56 AM - Call transfer requested on Leg L:387.3[Queue:8004]; subscr. ID=Refer.SrvSubscr(297561){[email protected]}
Refer Recv Req REFER from 127.0.0.1:5488 tid=4568850da8177b6e Call-ID=U1bp6uFUISioRasOh3VNiA..:
REFER sip:{{CallerNr}}@127.0.0.1:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5488;branch=z9hG4bK-524287-1---4568850da8177b6e;rport=5488
Max-Forwards: 70
Contact: <sip:[email protected]:5488;rinstance=d0403e624c991c0a>
To: <sip:{{CallerNr}}@127.0.0.1:5060;nf=e>;tag=ee5b1b6b
From: <sip:[email protected]>;tag=9a763a7a
Call-ID: U1bp6uFUISioRasOh3VNiA..
CSeq: 4 REFER
User-Agent: 3CX Queue Manager (q=8004)
Refer-To: <sip:{{RedirectionNr}}@127.0.0.1:5060>
Referred-By: <sip:[email protected]>
Content-Length: 0
 
Zuletzt bearbeitet:
Wir haben mit unserem Provider Easybell weiter Troubleshooted und es sieht so aus, als hätte die 3cx hier einen Bug.

Sobald man in der TK Anlage den G722 Codec als primären definiert hat und man von einer Call Queue aus nach extern Weiterleitet, dann sendet die 3cx einen leeren Invite (ohne Codec Auswahl), weshalb das Gespräch abgebrochen wird.

Hier der direkte Anruf welcher die Codecs mitgibt:
direkt.png

Hier der Anruf wenn er aus der Call Queue weitergeleitet wird, aber die Codecs fehlen:
WL_nicht_ok.png

@ilias_3CX können wir 3cx noch weiter irgendwie unterstützen diesen Fehler/Bug zu erkennen? Wie können wir mit 3cx direkt in Kontakt treten um den Fehler bei uns auszumerzen? An die Partner-Mailadresse habe ich gerade geschrieben, dort haben wir in der Vergangenheit aber nie Antwort oder nur einen Standart-Block als Antwort bekommen.

Viele Grüße,
Johnny
 
Hallo Apoo,

Ich kann mir nicht vorstellen dass es ein Bug ist, da in diesem Fall du auch das Problem hättest mit allen anderen Rufnummern.

Kannst du mir Bitte ein Screenshot anhängen von dem ersten Invite Message Header und Message Body? Im Body können wir sehen ob die Codecs drinnen sind.

Ansonsten kannst du am besten ein Ticket im 3CX Support öffnen, damit der Support auch eine Analyse macht.
 
Wir konnten das Thema zwischenzeitlich durch viel „herumspielen“ lösen.

Das Ende vom Lied war: Im SIP Trunk die Funktion „Support Reinvite“ deaktivieren und schon sendet 3cx wieder die Codecs mit… Wieso auch immer…
 
OK, Vielen Dank für deine Rückmeldung!
 

Statistik des Forums

Themen
44.414
Beiträge
232.721
Mitglieder
78.331
Neuestes Mitglied
b2daniel