Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4220
Views
15
Helpful
14
Replies

Cisco2951 as Cube setup Clip No Screening/Diversion Header

Go to solution
Chris9811
Level 1
Level 1

‎01-27-2020 11:43 PM

Hello, 

we have the following setup and we try to achive a Clip No Screening/Diversion Header to our remote Destinations (mobile phones). Our SIP-Provider told us that they support the feature and that it is active on our SIP-Trunk.

 

And they gave us this as a help for setup: SipAddHeader(Diversion: <${ORIGEXTEN}@sipconnect.sipgate.de>) but this ist not for the "cisco world" this is only working for Asterisk in my opinion.

 

So maybe someone here can translate us this into cisco language for our Cube?

 

Anything else is working fine - the only thing what is not working ist the diversion header, so that we do not see the fallback trunk number (+498922222-0) but the original number of the caller (+492112345678).

If we call from an internal phone to another one and the remote destination is reached the number shows up correctly. But this is only working for internal calls and not for calls from external.

 

We use a Cisco 2951K9 with c2951-universalk9-mz.SPA.157-3.M5.bin IOS installed.

 

The Configuration looks like that:

 

 

voice-card 0
!
!
!
voice service voip
ip address trusted list
ipv4 XXXXX  255.255.255.255
ipv4 XXXXX 255.255.240.0
ipv4 XXXXX 255.255.240.0
ipv4 XXXXXX 255.255.224.0
mode border-element 
media statistics
allow-connections sip to sip
supplementary-service h450.12
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
h323
call service stop
sip
bind control source-interface GigabitEthernet0/1
bind media source-interface GigabitEthernet0/0
registrar server expires max 3600 min 1800
asserted-id ppi
early-offer forced
no silent-discard untrusted
midcall-signaling passthru
g729 annexb-all
sip-profiles 1
!
voice class codec 1
codec preference 1 g711alaw
codec preference 2 g722-64
codec preference 3 g711ulaw
codec preference 4 g729r8
codec preference 5 g726r32
!
!
voice class sip-profiles 1
request REGISTER sip-header From modify "(<.*:)(.*@)" "<sip:2XXXX146t7@" 
request ANY sip-header From modify "(<.*:)(.*@)" "<sip:2XXXX146t7@" 
request INVITE sip-header To modify "(<.*:)(.*@)" "<sip:2XXXX46t7@" 
request INVITE sip-header Diversion modify "(<.*:)(.*@)" "<sip:2XXXX146t7@"- !this is our try to achive the function!

voice translation-rule 3
 rule 1 /^0/ /0049/
 rule 2 /^0\(.*$\)/ /0049\1/
 rule 4 /^11\(.*$\)/ /004911\1/
!
voice translation-rule 4
 rule 1 /^\(78..$\)/ /493XX51139\1/
!
voice translation-rule 11
 rule 1 /^/ // type unknown unknown
 rule 2 /^/ /49/ type national national
 rule 3 /^/ /0049/ type international international
!
voice translation-rule 12
 rule 1 /^493XX51139\(....$\)/ /\1/
!
!
voice translation-profile INCOMING
 translate calling 11
 translate called 12
!
voice translation-profile OUTGOING
 translate calling 4
 translate called 3
!

If we debug the SIP-Messages with debug ccsip messages we see the following in the "invite":

Jan 28 07:33:17.876: //14592/71E3E2000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:+4917XX67XX72@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.16X.XX.254:5060;branch=z9hG4bKDF62337
From: "017XX69XX55" <sip:2XXXX146t7@217.10.68.150>;tag=E528F44-460
To: <sip:2XXXX146t7@217.10.68.150>
Date: Tue, 28 Jan 2020 07:33:17 GMT
Call-ID: 49325314-40D711EA-B746E80A-8109750A@192.16X.XX.254
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 1910759936-0000065536-0000000140-3360925888
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Timestamp: 1580196797
Contact: <sip:017XX69XX55@192.16X.XX.254:5060>
Expires: 180
Allow-Events: telephone-event
Proxy-Authorization: Digest username="2XXXX146t7",realm="sipconnect.sipgate.de",uri="sip:+4917XX7XX872@217.10.68.150:5060",response="1671b35c37f70979e2a6f79e5879e921",nonce="Xi/k6V4v473KfeUZJWYZl2D3Xh41A4mB",algorithm=md5
Max-Forwards: 64
P-Preferred-Identity: "0175XX9XX55" <sip:01752691155@192.16X.XX.254>
Diversion: "Christoph XXXX"<sip:2XXXX146t7@192.16X.XX.200>;privacy=off;reason=follow-me;screen=yes
Session-ID: 3bed17337ed9551aba3074f0fa5c2032;remote=00000000000000000000000000000000
Session-Expires:  1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 322
v=0
o=CiscoSystemsSIP-GW-UserAgent 7873 6417 IN IP4 192.16X.XX.254
s=SIP Call
c=IN IP4 24.XXX.12.XX5
t=0 0
m=audio 16480 RTP/AVP 0 8 18 101
c=IN IP4 24.XXX.12.XX5
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

So hopefully someone here can help us with the configuration of that. 

Thank you very much in advance.

 

 

 

 

0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Ayodeji Okanlawon
VIP Alumni
VIP Alumni
In response to Chris9811

‎02-04-2020 01:52 AM

You need to modify your sip profile to have the valid DDI of all your extensions.

So if your extensions are 0175269XXXX

Then configure your PPI as follows

 

request INVITE sip-header P-Preferred-Identity modify  "<sip:0175269(.*)@(.*)>" "<sip:49175269\1@\2>"

 

 
 

 

Please rate all useful posts

View solution in original post

14 Replies 14

Go to solution
Ayodeji Okanlawon
VIP Alumni
VIP Alumni

‎01-28-2020 07:59 AM

Hi Chris,

Do you want the diversion header to b e like this?

Diversion: "Christoph XXXX"<sip:2XXXX146t7@sipconnect.sipgate.de>
Please rate all useful posts
0 Helpful

Go to solution
Chris9811
Level 1
Level 1
In response to Ayodeji Okanlawon

‎01-28-2020 09:40 AM

Hi Ayodeji,

no i want that it is look like this: SipAddHeader(Diversion: <${ORIGEXTEN}@sipconnect.sipgate.de>) in "cisco cube language" because this is the only thing what my provider gave me. What is that <${ORIGEXTEN}? And how can i set this in my cube?

Thanks for your quick reply.

 

 

0 Helpful

Go to solution
Ayodeji Okanlawon
VIP Alumni
VIP Alumni
In response to Chris9811

‎01-29-2020 12:35 AM

This looks like a template...This is not what I think they want..

Diversion: <${ORIGEXTEN}@sipconnect.sipgate.de>)

You need to clarify with them.. do they want this..

Diversion: <$XXXXX@sipconnect.sipgate.de>, where XXX is the originating extension?

Please rate all useful posts
0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to Ayodeji Okanlawon

‎01-29-2020 01:16 AM

I agree I think you need to clarify with the carrier as to which number should appear in each header.   Can you post an example of what's currently been sent, if you want to keep your numbers confidential then overwrite with something like "XXX" for original calling number, "YYY" for your internal called number, with the divert in place and "ZZZ" for the final called number.   So

XXX calls YYY

YYY is call forwarded to ZZZ

If I understand you correctly you want the final caller ZZZ to see the call as coming from XXX

So we need to know on that outgoing Invite, which headers should show YYY and which should show XXX

 

0 Helpful

Go to solution
Chris9811
Level 1
Level 1
In response to TONY SMITH

‎01-29-2020 10:04 AM

Hello, 

 

i have clarified with my carrier that the number must be the originating extension.

The debugs for the "INVITE" messages will follow tomorrow. 

 

Thanks for your help.

0 Helpful

Go to solution
Chris9811
Level 1
Level 1
In response to Chris9811

‎01-30-2020 09:01 PM - edited ‎01-30-2020 09:05 PM

Hello together, 

here are the debugs for the whole call (also the INVITE), i have done nothing with the phone numbers and my private ip space - my public IP is - MY PUBLIC IP. 

The account number of my provider (22134146t7) is also not real but exat like the real one.

 

Jan 31 04:48:24.341: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
...
Jan 31 04:48:26.757: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
INVITE sip:49366511397811@192.168.83.254:5060 SIP/2.0
Record-Route: <sip:217.10.68.150;lr;ftag=as515c5d1b>
Record-Route: <sip:172.20.40.8;lr>
Record-Route: <sip:217.10.68.137;lr;ftag=as515c5d1b>
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKabe2.6e16c37dbd7ba2fc2171470ce5e65384.0
Via: SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKabe2.44392bf2e18ac48dcea5c8a129bd78b1.0
Via: SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKabe2.d7b6c299821b7a9feb70f1f89d50293c.0
Via: SIP/2.0/UDP 212.9.44.6:5060;branch=z9hG4bK1aa7f7c7
Max-Forwards: 67
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as515c5d1b
To: <sip:0049366511397811@sipconnect.sipgate.de>
Contact: <sip:01752691155@212.9.44.6:5060>
Call-ID: 3fac1308647e0b3c7fc7f7772110b074@sipconnect.sipgate.de
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Content-Type: application/sdp
Content-Length: 438

v=0
o=root 760698569 760698570 IN IP4 212.9.44.6
s=sipgate VoIP GW
c=IN IP4 212.9.44.174
t=0 0
m=audio 22184 RTP/AVP 8 0 3 97 18 112 101
a=silenceSupp:off - - - -
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:18 G729/8000
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:97 mode=30
a=fmtp:18 annexb=no
a=fmtp:101 0-16
a=sendrecv
a=rtcp:22185
a=ptime:20

Jan 31 04:48:26.761: //30096/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKabe2.6e16c37dbd7ba2fc2171470ce5e65384.0,SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKabe2.44392bf2e18ac48dcea5c8a129bd78b1.0,SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKabe2.d7b6c299821b7a9feb70f1f89d50293c.0,SIP/2.0/UDP 212.9.44.6:5060;branch=z9hG4bK1aa7f7c7
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as515c5d1b
To: <sip:0049366511397811@sipconnect.sipgate.de>
Date: Fri, 31 Jan 2020 04:48:26 GMT
Call-ID: 3fac1308647e0b3c7fc7f7772110b074@sipconnect.sipgate.de
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: 00000000000000000000000000000000;remote=c8bc479f6135556da489e31f503417e3
Content-Length: 0


Jan 31 04:48:26.765: //30097/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:7811@192.168.83.200:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C74988
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5620-131
To: <sip:22134146t7@192.168.83.200>
Date: Fri, 31 Jan 2020 04:48:26 GMT
Call-ID: C0E552EE-431B11EA-B2C7E80A-8109750A@192.168.83.254
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 3236174494-1125847530-2999052298-2164880650
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1580446106
Contact: <sip:01752691155@192.168.83.254:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 66
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.254>
Session-ID: c8bc479f6135556da489e31f503417e3;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 353

v=0
o=CiscoSystemsSIP-GW-UserAgent 9046 9635 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 192.168.83.254
t=0 0
m=audio 16924 RTP/AVP 8 0 18 98 101
c=IN IP4 192.168.83.254
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:98 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

Jan 31 04:48:26.769: //30097/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C74988
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5620-131
To: <sip:22134146t7@192.168.83.200>
Date: Fri, 31 Jan 2020 04:48:26 GMT
Call-ID: C0E552EE-431B11EA-B2C7E80A-8109750A@192.168.83.254
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0


Jan 31 04:48:26.781: //30097/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C74988
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5620-131
To: <sip:22134146t7@192.168.83.200>;tag=523495~badef395-9309-48d9-8bf8-030362ac44b2-23156887
Date: Fri, 31 Jan 2020 04:48:26 GMT
Call-ID: C0E552EE-431B11EA-B2C7E80A-8109750A@192.168.83.254
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Server: Cisco-CUCM12.0
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-ID: 00000000000000000000000000000000;remote=c8bc479f6135556da489e31f503417e3
P-Preferred-Identity: "Christoph" <sip:7811@192.168.83.200>
Privacy: none
Contact: <sip:7811@192.168.83.200:5060>
Content-Length: 0


Jan 31 04:48:26.785: //30096/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKabe2.6e16c37dbd7ba2fc2171470ce5e65384.0,SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKabe2.44392bf2e18ac48dcea5c8a129bd78b1.0,SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKabe2.d7b6c299821b7a9feb70f1f89d50293c.0,SIP/2.0/UDP 212.9.44.6:5060;branch=z9hG4bK1aa7f7c7
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as515c5d1b
To: <sip:0049366511397811@sipconnect.sipgate.de>;tag=1D2E5630-1A18
Date: Fri, 31 Jan 2020 04:48:26 GMT
Call-ID: 3fac1308647e0b3c7fc7f7772110b074@sipconnect.sipgate.de
CSeq: 103 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Preferred-Identity: "Christoph" <sip:7811@192.168.83.254>
Contact: <sip:49366511397811@192.168.83.254:5060>
Record-Route: <sip:217.10.68.150;lr;ftag=as515c5d1b>,<sip:172.20.40.8;lr>,<sip:217.10.68.137;lr;ftag=as515c5d1b>
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: 00000000000000000000000000000000;remote=c8bc479f6135556da489e31f503417e3
Content-Length: 0


Jan 31 04:48:28.789: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
INVITE sip:+491736749872@192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c34a51b389f7
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=523501~badef395-9309-48d9-8bf8-030362ac44b2-23156888
To: <sip:+491736749872@192.168.83.254>
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: ead37b80-e331b19c-1a237-c853a8c0@192.168.83.200
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM12.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=MIXED
Session-ID: c8bc479f6135556da489e31f503417e3;remote=00000000000000000000000000000000
Cisco-Guid: 3939728256-0000065536-0000000182-3360925888
Session-Expires:  1800
Diversion: "Christoph" <sip:7811@192.168.83.200>;reason=follow-me;privacy=off;screen=yes
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.200>
Privacy: none
Contact: <sip:01752691155@192.168.83.200:5060;transport=tcp>
Max-Forwards: 65
Content-Type: application/sdp
Content-Length: 312

v=0
o=CiscoSystemsCCM-SIP 523501 1 IN IP4 192.168.83.200
s=SIP Call
c=IN IP4 192.168.83.254
b=TIAS:64000
b=AS:64
t=0 0
m=audio 16924 RTP/AVP 0 8 18 101
a=ptime:20
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Jan 31 04:48:28.793: //30098/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c34a51b389f7
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=523501~badef395-9309-48d9-8bf8-030362ac44b2-23156888
To: <sip:+491736749872@192.168.83.254>
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: ead37b80-e331b19c-1a237-c853a8c0@192.168.83.200
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: 00000000000000000000000000000000;remote=c8bc479f6135556da489e31f503417e3
Content-Length: 0


Jan 31 04:48:28.797: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:+491736749872@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C75FAB
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 3939728256-0000065536-0000000182-3360925888
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1580446108
Contact: <sip:01752691155@192.168.83.254:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 64
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.254>
Diversion: "Christoph"<sip:7811@192.168.83.200>;privacy=off;reason=follow-me;screen=yes
Session-ID: c8bc479f6135556da489e31f503417e3;remote=00000000000000000000000000000000
Session-Expires:  1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 322

v=0
o=CiscoSystemsSIP-GW-UserAgent 7164 6371 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 MY-PUBLIC-IP
t=0 0
m=audio 16928 RTP/AVP 0 8 18 101
c=IN IP4 MY-PUBLIC-IP
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Jan 31 04:48:28.825: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY-PUBLIC-IP;branch=z9hG4bK1C75FAB
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>;tag=ca40b14695a455acdff6b4fb6f6d0a8e.0c69
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="sipconnect.sipgate.de", nonce="XjOyyF4zsZyT2zHPTaFkUZl2SvRVBu7V"
Content-Length: 0


Jan 31 04:48:28.825: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
ACK sip:+491736749872@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C75FAB
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>;tag=ca40b14695a455acdff6b4fb6f6d0a8e.0c69
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: c8bc479f6135556da489e31f503417e3;remote=956e8ef1da00587a95dd0894b77ce437
Content-Length: 0


Jan 31 04:48:28.829: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:+491736749872@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C761F74
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 3939728256-0000065536-0000000182-3360925888
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Timestamp: 1580446108
Contact: <sip:01752691155@192.168.83.254:5060>
Expires: 180
Allow-Events: telephone-event
Proxy-Authorization: Digest username="22134146t7",realm="sipconnect.sipgate.de",uri="sip:+491736749872@217.10.68.150:5060",response="06eb3f4b9c0542d4596fa658193ba22f",nonce="XjOyyF4zsZyT2zHPTaFkUZl2SvRVBu7V",algorithm=md5
Max-Forwards: 64
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.254>
Diversion: "Christoph"<sip:7811@192.168.83.200>;privacy=off;reason=follow-me;screen=yes
Session-ID: c8bc479f6135556da489e31f503417e3;remote=00000000000000000000000000000000
Session-Expires:  1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 322

v=0
o=CiscoSystemsSIP-GW-UserAgent 7164 6371 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 MY-PUBLIC-IP
t=0 0
m=audio 16928 RTP/AVP 0 8 18 101
c=IN IP4 MY-PUBLIC-IP
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Jan 31 04:48:28.881: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY-PUBLIC-IP;branch=z9hG4bK1C761F74
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
CSeq: 102 INVITE
Content-Length: 0


Jan 31 04:48:30.769: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY-PUBLIC-IP;branch=z9hG4bK1C761F74
Record-Route: <sip:172.20.40.7;lr>
Record-Route: <sip:217.10.68.150;lr;ftag=1D2E5E10-1395>
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>;tag=as26c7fc96
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Contact: <sip:190049D1241736749872@217.116.117.5:5060>
Content-Length: 0


Jan 31 04:48:30.773: //30098/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c34a51b389f7
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=523501~badef395-9309-48d9-8bf8-030362ac44b2-23156888
To: <sip:+491736749872@192.168.83.254>;tag=1D2E65C8-16D9
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: ead37b80-e331b19c-1a237-c853a8c0@192.168.83.200
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Preferred-Identity: <sip:+491736749872@192.168.83.254>
Contact: <sip:190049D1241736749872@192.168.83.254:5060;transport=tcp>
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: a6c14d1319955c388ab207ffef7f0005;remote=c8bc479f6135556da489e31f503417e3
Content-Length: 0


Jan 31 04:48:30.985: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY-PUBLIC-IP;branch=z9hG4bK1C761F74
Record-Route: <sip:172.20.40.7;lr>
Record-Route: <sip:217.10.68.150;lr;ftag=1D2E5E10-1395>
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>;tag=as26c7fc96
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Contact: <sip:190049D1241736749872@217.116.117.5:5060>
Content-Type: application/sdp
Content-Length: 345

v=0
o=root 1396495072 1396495072 IN IP4 217.116.117.5
s=sipgate VoIP GW
c=IN IP4 217.10.77.146
t=0 0
m=audio 28558 RTP/AVP 8 0 18 101
a=silenceSupp:off - - - -
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:18 annexb=no
a=fmtp:101 0-16
a=sendrecv
a=rtcp:28559
a=ptime:20

Jan 31 04:48:30.989: //30098/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c34a51b389f7
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=523501~badef395-9309-48d9-8bf8-030362ac44b2-23156888
To: <sip:+491736749872@192.168.83.254>;tag=1D2E65C8-16D9
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: ead37b80-e331b19c-1a237-c853a8c0@192.168.83.200
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Preferred-Identity: <sip:+491736749872@192.168.83.254>
Contact: <sip:190049D1241736749872@192.168.83.254:5060;transport=tcp>
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: a6c14d1319955c388ab207ffef7f0005;remote=c8bc479f6135556da489e31f503417e3
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 253

v=0
o=CiscoSystemsSIP-GW-UserAgent 1181 7556 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 192.168.83.254
t=0 0
m=audio 16926 RTP/AVP 8 101
c=IN IP4 192.168.83.254
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

Jan 31 04:48:31.117: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY-PUBLIC-IP;branch=z9hG4bK1C761F74
Record-Route: <sip:172.20.40.7;lr>
Record-Route: <sip:217.10.68.150;lr;ftag=1D2E5E10-1395>
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>;tag=as26c7fc96
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Contact: <sip:190049D1241736749872@217.116.117.5:5060>
Content-Type: application/sdp
Content-Length: 345

v=0
o=root 1396495072 1396495073 IN IP4 217.116.117.5
s=sipgate VoIP GW
c=IN IP4 217.10.77.146
t=0 0
m=audio 28558 RTP/AVP 8 0 18 101
a=silenceSupp:off - - - -
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:18 annexb=no
a=fmtp:101 0-16
a=sendrecv
a=rtcp:28559
a=ptime:20

Jan 31 04:48:31.121: //30098/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c34a51b389f7
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=523501~badef395-9309-48d9-8bf8-030362ac44b2-23156888
To: <sip:+491736749872@192.168.83.254>;tag=1D2E65C8-16D9
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: ead37b80-e331b19c-1a237-c853a8c0@192.168.83.200
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Preferred-Identity: <sip:+491736749872@192.168.83.254>
Contact: <sip:+491736749872@192.168.83.254:5060;transport=tcp>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: a6c14d1319955c388ab207ffef7f0005;remote=c8bc479f6135556da489e31f503417e3
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 253

v=0
o=CiscoSystemsSIP-GW-UserAgent 1181 7556 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 192.168.83.254
t=0 0
m=audio 16926 RTP/AVP 8 101
c=IN IP4 192.168.83.254
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

Jan 31 04:48:31.121: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
ACK sip:190049D1241736749872@217.116.117.5:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C772667
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>;tag=as26c7fc96
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
Route: <sip:217.10.68.150;lr;ftag=1D2E5E10-1395>,<sip:172.20.40.7;lr>
Max-Forwards: 70
CSeq: 102 ACK
Proxy-Authorization: Digest username="22134146t7",realm="sipconnect.sipgate.de",uri="sip:+491736749872@217.10.68.150:5060",response="06eb3f4b9c0542d4596fa658193ba22f",nonce="XjOyyF4zsZyT2zHPTaFkUZl2SvRVBu7V",algorithm=md5
Allow-Events: telephone-event
Content-Length: 0


Jan 31 04:48:31.125: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
ACK sip:+491736749872@192.168.83.254:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c34bd44fe54
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=523501~badef395-9309-48d9-8bf8-030362ac44b2-23156888
To: <sip:+491736749872@192.168.83.254>;tag=1D2E65C8-16D9
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: ead37b80-e331b19c-1a237-c853a8c0@192.168.83.200
User-Agent: Cisco-CUCM12.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Privacy: none
Content-Length: 0


Jan 31 04:48:31.133: //30097/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C74988
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5620-131
To: <sip:22134146t7@192.168.83.200>;tag=523495~badef395-9309-48d9-8bf8-030362ac44b2-23156887
Date: Fri, 31 Jan 2020 04:48:26 GMT
Call-ID: C0E552EE-431B11EA-B2C7E80A-8109750A@192.168.83.254
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Supported: replaces
Server: Cisco-CUCM12.0
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=MIXED
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires:  1800;refresher=uas
Require:  timer
Session-ID: a6c14d1319955c388ab207ffef7f0005;remote=c8bc479f6135556da489e31f503417e3
P-Preferred-Identity: "Christoph" <sip:7811@192.168.83.200>
Privacy: none
Contact: <sip:7811@192.168.83.200:5060>
Content-Type: application/sdp
Content-Length: 241

v=0
o=CiscoSystemsCCM-SIP 523495 1 IN IP4 192.168.83.200
s=SIP Call
c=IN IP4 192.168.83.254
b=TIAS:64000
b=AS:64
t=0 0
m=audio 16926 RTP/AVP 8 101
a=ptime:20
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Jan 31 04:48:31.137: //30097/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Sent: 
ACK sip:7811@192.168.83.200:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C78FD1
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5620-131
To: <sip:22134146t7@192.168.83.200>;tag=523495~badef395-9309-48d9-8bf8-030362ac44b2-23156887
Date: Fri, 31 Jan 2020 04:48:26 GMT
Call-ID: C0E552EE-431B11EA-B2C7E80A-8109750A@192.168.83.254
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: c8bc479f6135556da489e31f503417e3;remote=a6c14d1319955c388ab207ffef7f0005
Content-Length: 0


Jan 31 04:48:31.141: //30096/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKabe2.6e16c37dbd7ba2fc2171470ce5e65384.0,SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKabe2.44392bf2e18ac48dcea5c8a129bd78b1.0,SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKabe2.d7b6c299821b7a9feb70f1f89d50293c.0,SIP/2.0/UDP 212.9.44.6:5060;branch=z9hG4bK1aa7f7c7
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as515c5d1b
To: <sip:0049366511397811@sipconnect.sipgate.de>;tag=1D2E5630-1A18
Date: Fri, 31 Jan 2020 04:48:26 GMT
Call-ID: 3fac1308647e0b3c7fc7f7772110b074@sipconnect.sipgate.de
CSeq: 103 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Preferred-Identity: "Christoph" <sip:7811@192.168.83.254>
Contact: <sip:49366511397811@192.168.83.254:5060>
Record-Route: <sip:217.10.68.150;lr;ftag=as515c5d1b>,<sip:172.20.40.8;lr>,<sip:217.10.68.137;lr;ftag=as515c5d1b>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: a6c14d1319955c388ab207ffef7f0005;remote=c8bc479f6135556da489e31f503417e3
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 194

v=0
o=CiscoSystemsSIP-GW-UserAgent 4633 997 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 MY-PUBLIC-IP
t=0 0
m=audio 16922 RTP/AVP 8
c=IN IP4 MY-PUBLIC-IP
a=rtpmap:8 PCMA/8000
a=ptime:20

Jan 31 04:48:31.169: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
ACK sip:49366511397811@192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKabe2.0f143a4bccfd321925b1e9ce480be4c1.0
Via: SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKabe2.282b31287103176291178da1ae564515.0
Via: SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKabe2.1c4b85c874a47aed66a544bc57c72a4e.0
Via: SIP/2.0/UDP 212.9.44.6:5060;branch=z9hG4bK29e744ad
Max-Forwards: 67
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as515c5d1b
To: <sip:0049366511397811@sipconnect.sipgate.de>;tag=1D2E5630-1A18
Contact: <sip:01752691155@212.9.44.6:5060>
Call-ID: 3fac1308647e0b3c7fc7f7772110b074@sipconnect.sipgate.de
CSeq: 103 ACK
Content-Length: 0


Jan 31 04:48:33.738: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
OPTIONS sip:192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c3544b16d127
From: <sip:192.168.83.200>;tag=1856700166
To: <sip:192.168.83.254>
Date: Fri, 31 Jan 2020 04:48:33 GMT
Call-ID: edce6c00-e331b1a1-1a23b-c853a8c0@192.168.83.200
User-Agent: Cisco-CUCM12.0
CSeq: 101 OPTIONS
Contact: <sip:192.168.83.200:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Jan 31 04:48:33.742: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c3544b16d127
From: <sip:192.168.83.200>;tag=1856700166
To: <sip:192.168.83.254>;tag=1D2E715C-176F
Date: Fri, 31 Jan 2020 04:48:33 GMT
Call-ID: edce6c00-e331b1a1-1a23b-c853a8c0@192.168.83.200
Server: Cisco-SIPGateway/IOS-15.7.3.M5
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 376

v=0
o=CiscoSystemsSIP-GW-UserAgent 1719 9356 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 MY-PUBLIC-IP
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15
c=IN IP4 MY-PUBLIC-IP
m=image 0 udptl t38
c=IN IP4 MY-PUBLIC-IP
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

Jan 31 04:48:35.626: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
BYE sip:49366511397811@192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bK7be2.c52f818bd36fa84936005d0fe2306e33.0
Via: SIP/2.0/UDP 172.20.40.8;branch=z9hG4bK7be2.0dd2fd5499652edce8bf9ce2fda237b0.0
Via: SIP/2.0/UDP 217.10.68.137;branch=z9hG4bK7be2.2fd542f61e8ff5c468f38ef398b0903a.0
Via: SIP/2.0/UDP 212.9.44.6:5060;branch=z9hG4bK66a5ffee
Max-Forwards: 67
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as515c5d1b
To: <sip:0049366511397811@sipconnect.sipgate.de>;tag=1D2E5630-1A18
Call-ID: 3fac1308647e0b3c7fc7f7772110b074@sipconnect.sipgate.de
CSeq: 104 BYE
Reason: Q.850;cause=16
Content-Length: 0


Jan 31 04:48:35.630: //30096/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bK7be2.c52f818bd36fa84936005d0fe2306e33.0,SIP/2.0/UDP 172.20.40.8;branch=z9hG4bK7be2.0dd2fd5499652edce8bf9ce2fda237b0.0,SIP/2.0/UDP 217.10.68.137;branch=z9hG4bK7be2.2fd542f61e8ff5c468f38ef398b0903a.0,SIP/2.0/UDP 212.9.44.6:5060;branch=z9hG4bK66a5ffee
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as515c5d1b
To: <sip:0049366511397811@sipconnect.sipgate.de>;tag=1D2E5630-1A18
Date: Fri, 31 Jan 2020 04:48:35 GMT
Call-ID: 3fac1308647e0b3c7fc7f7772110b074@sipconnect.sipgate.de
Server: Cisco-SIPGateway/IOS-15.7.3.M5
CSeq: 104 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=225,OS=36000,PR=204,OR=32640,PL=0,JI=0,LA=0,DU=4
Session-ID: a6c14d1319955c388ab207ffef7f0005;remote=c8bc479f6135556da489e31f503417e3
Content-Length: 0


Jan 31 04:48:35.630: //30097/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Sent: 
BYE sip:7811@192.168.83.200:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C793FB
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5620-131
To: <sip:22134146t7@192.168.83.200>;tag=523495~badef395-9309-48d9-8bf8-030362ac44b2-23156887
Date: Fri, 31 Jan 2020 04:48:26 GMT
Call-ID: C0E552EE-431B11EA-B2C7E80A-8109750A@192.168.83.254
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Max-Forwards: 70
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.254>
Timestamp: 1580446115
CSeq: 102 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=204,OS=32640,PR=225,OR=36000,PL=0,JI=0,LA=0,DU=4
Session-ID: c8bc479f6135556da489e31f503417e3;remote=a6c14d1319955c388ab207ffef7f0005
Content-Length: 0


Jan 31 04:48:35.634: //30097/C0E41A9EB2C1/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C793FB
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5620-131
To: <sip:22134146t7@192.168.83.200>;tag=523495~badef395-9309-48d9-8bf8-030362ac44b2-23156887
Date: Fri, 31 Jan 2020 04:48:35 GMT
Call-ID: C0E552EE-431B11EA-B2C7E80A-8109750A@192.168.83.254
Server: Cisco-CUCM12.0
CSeq: 102 BYE
Content-Length: 0


Jan 31 04:48:35.634: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
BYE sip:+491736749872@192.168.83.254:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c35536ad06e
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=523501~badef395-9309-48d9-8bf8-030362ac44b2-23156888
To: <sip:+491736749872@192.168.83.254>;tag=1D2E65C8-16D9
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: ead37b80-e331b19c-1a237-c853a8c0@192.168.83.200
User-Agent: Cisco-CUCM12.0
Max-Forwards: 70
Privacy: none
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.200>
CSeq: 102 BYE
Reason: Q.850;cause=16
Session-ID: c8bc479f6135556da489e31f503417e3;remote=a6c14d1319955c388ab207ffef7f0005
Content-Length: 0


Jan 31 04:48:35.638: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1c35536ad06e
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=523501~badef395-9309-48d9-8bf8-030362ac44b2-23156888
To: <sip:+491736749872@192.168.83.254>;tag=1D2E65C8-16D9
Date: Fri, 31 Jan 2020 04:48:35 GMT
Call-ID: ead37b80-e331b19c-1a237-c853a8c0@192.168.83.200
Server: Cisco-SIPGateway/IOS-15.7.3.M5
CSeq: 102 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=232,OS=37120,PR=204,OR=32640,PL=0,JI=0,LA=0,DU=4
Session-ID: a6c14d1319955c388ab207ffef7f0005;remote=c8bc479f6135556da489e31f503417e3
Content-Length: 0


Jan 31 04:48:35.638: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Sent: 
BYE sip:190049D1241736749872@217.116.117.5:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK1C7A20CA
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>;tag=as26c7fc96
Date: Fri, 31 Jan 2020 04:48:28 GMT
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Max-Forwards: 70
Route: <sip:217.10.68.150;lr;ftag=1D2E5E10-1395>,<sip:172.20.40.7;lr>
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.254>
Timestamp: 1580446115
CSeq: 103 BYE
Proxy-Authorization: Digest username="22134146t7",realm="sipconnect.sipgate.de",uri="sip:190049D1241736749872@217.116.117.5:5060",response="b5d863993d188ef62e7138c0af8e463d",nonce="XjOyyF4zsZyT2zHPTaFkUZl2SvRVBu7V",algorithm=md5
Reason: Q.850;cause=16
P-RTP-Stat: PS=204,OS=32640,PR=232,OR=37120,PL=0,JI=0,LA=0,DU=4
Session-ID: c8bc479f6135556da489e31f503417e3;remote=a6c14d1319955c388ab207ffef7f0005
Content-Length: 0


Jan 31 04:48:35.666: //30099/EAD37B800000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY-PUBLIC-IP;branch=z9hG4bK1C7A20CA
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=1D2E5E10-1395
To: <sip:22134146t7@217.10.68.150>;tag=as26c7fc96
Call-ID: C21B6986-431B11EA-B2CDE80A-8109750A@192.168.83.254
CSeq: 103 BYE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Content-Length: 0

u
Jan 31 04:48:38.606: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: MY-PUBLIC-IP  

 

0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to Chris9811

‎01-31-2020 03:23 AM

To make sure we're clear it appears that in this example ...

01752691155 is the original caller

He called 0049366511397811 which internally routes to extension 7811

7811 diverts to +491736749872 

And as I understand it your problem relates to what the final called party +491736749872 sees as a the calling number.   

Is that all correct?  If so then what does the final called party see, and what do you want them to see.

Was that debug taken with the configuration exactly as shown before?  The reason I ask it that your profile does not appear to have affected the outgoing Diversion header which still shows the number 7811 as sent by CUCM.

 

0 Helpful

Go to solution
Chris9811
Level 1
Level 1
In response to TONY SMITH

‎01-31-2020 07:11 AM

Yes that is all correct.

The final called party see: +4936651139780 (fallback number from our SIP-TRUNK) and i want them to see +491752691155 (original caller).

No the debug was not made with the config shown above. We have now brought the config back up to the state from above.

Do we need another debug?

 

Thank you very much for your help.

0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to Chris9811

‎01-31-2020 08:09 AM

Yes, paste up another debug.  If I follow your configuration correctly you should see the number in P-Asserted-Identity changed by your SIP profile.

0 Helpful

Go to solution
Chris9811
Level 1
Level 1
In response to TONY SMITH

‎02-01-2020 12:03 AM

Here is another debug with the config from above:

Feb  1 07:59:07.248: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
INVITE sip:49366511397811@192.168.83.254:5060 SIP/2.0
Record-Route: <sip:217.10.68.150;lr;ftag=as2555b591>
Record-Route: <sip:172.20.40.8;lr>
Record-Route: <sip:217.10.68.137;lr;ftag=as2555b591>
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKc1a4.b990f1805556486a60ef5dc4029e14e3.0
Via: SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKc1a4.5e1fc4ee20c0782184fc0cd77e60e289.0
Via: SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKc1a4.58f8500896bf3e3d60ed149fd4ab5bd0.0
Via: SIP/2.0/UDP 217.10.67.11:5060;branch=z9hG4bK2e76d6c4
Max-Forwards: 67
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as2555b591
To: <sip:0049366511397811@sipconnect.sipgate.de>
Contact: <sip:01752691155@217.10.67.11:5060>
Call-ID: 7fd1eae14a1f94a35df8beb31a57a33e@sipconnect.sipgate.de
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Content-Type: application/sdp
Content-Length: 442

v=0
o=root 2036942571 2036942572 IN IP4 217.10.67.11
s=sipgate VoIP GW
c=IN IP4 212.9.44.164
t=0 0
m=audio 16788 RTP/AVP 8 0 3 97 18 112 101
a=silenceSupp:off - - - -
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:18 G729/8000
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:97 mode=30
a=fmtp:18 annexb=no
a=fmtp:101 0-16
a=sendrecv
a=rtcp:16789
a=ptime:20

Feb  1 07:59:07.256: //36132/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKc1a4.b990f1805556486a60ef5dc4029e14e3.0,SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKc1a4.5e1fc4ee20c0782184fc0cd77e60e289.0,SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKc1a4.58f8500896bf3e3d60ed149fd4ab5bd0.0,SIP/2.0/UDP 217.10.67.11:5060;branch=z9hG4bK2e76d6c4
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as2555b591
To: <sip:0049366511397811@sipconnect.sipgate.de>
Date: Sat, 01 Feb 2020 07:59:07 GMT
Call-ID: 7fd1eae14a1f94a35df8beb31a57a33e@sipconnect.sipgate.de
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: 00000000000000000000000000000000;remote=5ef89e0f7af051a486054e00b7492dfd
Content-Length: 0


Feb  1 07:59:07.260: //36133/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:7811@192.168.77.201:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220914BA
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=23031D84-240B
To: <sip:22134146t7@192.168.77.201>
Date: Sat, 01 Feb 2020 07:59:07 GMT
Call-ID: 8E5F8C67-43FF11EA-89B8E80A-8109750A@192.168.83.254
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 2388586559-1140789738-2310203402-2164880650
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1580543947
Contact: <sip:01752691155@192.168.83.254:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 66
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.254>
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 352


Cisco2951#
Cisco2951#
Cisco2951#v=0
o=CiscoSystemsSIP-GW-UserAgent 186 1020 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 192.168.83.254
t=0 0
m=audio 17000 RTP/AVP 8 0 18 98 101
c=IN IP4 192.168.83.254
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:98 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

Feb  1 07:59:07.308: //36133/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220914BA
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=23031D84-240B
To: <sip:22134146t7@192.168.77.201>
Date: Sat, 01 Feb 2020 07:59:07 GMT
Call-ID: 8E5F8C67-43FF11EA-89B8E80A-8109750A@192.168.83.254
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0


Feb  1 07:59:07.356: //36133/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220914BA
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=23031D84-240B
To: <sip:22134146t7@192.168.77.201>;tag=111403~badef395-9309-48d9-8bf8-030362ac44b2-55015452
Date: Sat, 01 Feb 2020 07:59:07 GMT
Call-ID: 8E5F8C67-43FF11EA-89B8E80A-8109750A@192.168.83.254
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Server: Cisco-CUCM12.0
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-ID: 00000000000000000000000000000000;remote=5ef89e0f7af051a486054e00b7492dfd
P-Preferred-Identity: "Christoph" <sip:7811@192.168.77.201>
Privacy: none
Contact: <sip:7811@192.168.77.201:5060>
Content-Length: 0


Feb  1 07:59:07.360: //36132/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKc1a4.b990f1805556486a60ef5dc4029e14e3.0,SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKc1a4.5e1fc4ee20c0782184fc0cd77e60e289.0,SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKc1a4.58f8500896bf3e3d60ed149fd4ab5bd0.0,SIP/2.0/UDP 217.10.67.11:5060;branch=z9hG4bK2e76d6c4
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as2555b591
To: <sip:0049366511397811@sipconnect.sipgate.de>;tag=23031DE8-43D
Date: Sat, 01 Feb 2020 07:59:07 GMT
Call-ID: 7fd1eae14a1f94a35df8beb31a57a33e@sipconnect.sipgate.de
CSeq: 103 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Preferred-Identity: "Christoph" <sip:7811@192.168.83.254>
Contact: <sip:49366511397811@192.168.83.254:5060>
Record-Route: <sip:217.10.68.150;lr;ftag=as2555b591>,<sip:172.20.40.8;lr>,<sip:217.10.68.137;lr;ftag=as2555b591>
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: 00000000000000000000000000000000;remote=5ef89e0f7af051a486054e00b7492dfd
Content-Length: 0


Feb  1 08:59:08 CET: %FW-6-DROP_PKT: Dropping tcp session 93.174.93.33:59487 MY PUBLIC IP:33911 on zone-pair Internet_to_Router class class-default due to  DROP action found in policy-map with ip ident 34820 
Feb  1 07:59:09.373: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
INVITE sip:+491736749872@192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae149cff53b
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=551504~badef395-9309-48d9-8bf8-030362ac44b2-55015453
To: <sip:+491736749872@192.168.83.254>
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: b89b4a00-e3512fcd-1b8cc-c853a8c0@192.168.83.200
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM12.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=MIXED
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=00000000000000000000000000000000
Cisco-Guid: 3097184768-0000065536-0000000190-3360925888
Session-Expires:  1800
Diversion: "Christoph" <sip:7811@192.168.83.200>;reason=follow-me;privacy=off;screen=yes
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.200>
Privacy: none
Contact: <sip:01752691155@192.168.83.200:5060;transport=tcp>
Max-Forwards: 65
Content-Type: application/sdp
Content-Length: 312

v=0
o=CiscoSystemsCCM-SIP 551504 1 IN IP4 192.168.83.200
s=SIP Call
c=IN IP4 192.168.83.254
b=TIAS:64000
b=AS:64
t=0 0
m=audio 17000 RTP/AVP 0 8 18 101
a=ptime:20
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Feb  1 07:59:09.381: //36134/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae149cff53b
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=551504~badef395-9309-48d9-8bf8-030362ac44b2-55015453
To: <sip:+491736749872@192.168.83.254>
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: b89b4a00-e3512fcd-1b8cc-c853a8c0@192.168.83.200
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: 00000000000000000000000000000000;remote=5ef89e0f7af051a486054e00b7492dfd
Content-Length: 0


Feb  1 07:59:09.385: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:+491736749872@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220A62F
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 3097184768-0000065536-0000000190-3360925888
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1580543949
Contact: <sip:01752691155@192.168.83.254:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 64
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.254>
Diversion: "Christoph"<sip:2XXXX146t7@192.168.83.200>;privacy=off;reason=follow-me;screen=yes
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=00000000000000000000000000000000
Session-Expires:  1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 322

v=0
o=CiscoSystemsSIP-GW-UserAgent 9085 3972 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 MY PUBLIC IP
t=0 0
m=audio 17004 RTP/AVP 0 8 18 101
c=IN IP4 MY PUBLIC IP
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Feb  1 07:59:09.413: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY PUBLIC IP;branch=z9hG4bK220A62F
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>;tag=ca40b14695a455acdff6b4fb6f6d0a8e.0c69
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="sipconnect.sipgate.de", nonce="XjUw+V41L83/VF5Iwn9ic4GKqjhGrFLY"
Content-Length: 0


Feb  1 07:59:09.413: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
ACK sip:+491736749872@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220A62F
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>;tag=ca40b14695a455acdff6b4fb6f6d0a8e.0c69
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=c40b8e41191b5d6f8553d73f4128be28
Content-Length: 0


Feb  1 07:59:09.413: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:+491736749872@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220BC34
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 3097184768-0000065536-0000000190-3360925888
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Timestamp: 1580543949
Contact: <sip:01752691155@192.168.83.254:5060>
Expires: 180
Allow-Events: telephone-event
Proxy-Authorization: Digest username="22134146t7",realm="sipconnect.sipgate.de",uri="sip:+491736749872@217.10.68.150:5060",response="4fffd602e51734c980c654cdc48500d3",nonce="XjUw+V41L83/VF5Iwn9ic4GKqjhGrFLY",algorithm=md5
Max-Forwards: 64
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.254>
Diversion: "Christoph"<sip:2XXXX146t7@192.168.83.200>;privacy=off;reason=follow-me;screen=yes
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=00000000000000000000000000000000
Session-Expires:  1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 322

v=0
o=CiscoSystemsSIP-GW-UserAgent 9085 3972 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 MY PUBLIC IP
t=0 0
m=audio 17004 RTP/AVP 0 8 18 101
c=IN IP4 MY PUBLIC IP
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Feb  1 07:59:09.469: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY PUBLIC IP;branch=z9hG4bK220BC34
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
CSeq: 102 INVITE
Content-Length: 0


Feb  1 07:59:11.413: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
...
Feb  1 07:59:11.929: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
OPTIONS sip:192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.77.201:5060;branch=z9hG4bK1ad954bdef367
From: <sip:192.168.77.201>;tag=1609743988
To: <sip:192.168.83.254>
Date: Sat, 01 Feb 2020 07:59:11 GMT
Call-ID: b9cc7700-e3512fcf-1acde-c94da8c0@192.168.77.201
User-Agent: Cisco-CUCM12.0
CSeq: 101 OPTIONS
Contact: <sip:192.168.77.201:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Feb  1 07:59:11.929: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.168.77.201:5060;branch=z9hG4bK1ad954bdef367
From: <sip:192.168.77.201>;tag=1609743988
To: <sip:192.168.83.254>;tag=23032FC0-F5F
Date: Sat, 01 Feb 2020 07:59:11 GMT
Call-ID: b9cc7700-e3512fcf-1acde-c94da8c0@192.168.77.201
Server: Cisco-SIPGateway/IOS-15.7.3.M5
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 376

v=0
o=CiscoSystemsSIP-GW-UserAgent 7585 5115 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 MY PUBLIC IP
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15
c=IN IP4 MY PUBLIC IP
m=image 0 udptl t38
c=IN IP4 MY PUBLIC IP
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

Feb  1 07:59:12.137: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY PUBLIC IP;branch=z9hG4bK220BC34
Record-Route: <sip:172.20.40.7;lr>
Record-Route: <sip:217.10.68.150;lr;ftag=230325CC-1921>
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>;tag=as6a0d7701
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Contact: <sip:190049D1241736749872@217.10.67.11:5060>
Content-Length: 0


Feb  1 07:59:12.141: //36134/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae149cff53b
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=551504~badef395-9309-48d9-8bf8-030362ac44b2-55015453
To: <sip:+491736749872@192.168.83.254>;tag=23033090-213D
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: b89b4a00-e3512fcd-1b8cc-c853a8c0@192.168.83.200
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Preferred-Identity: <sip:+491736749872@192.168.83.254>
Contact: <sip:190049D1241736749872@192.168.83.254:5060;transport=tcp>
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: 2ef0fca8f9245695ac8b187badc32b63;remote=5ef89e0f7af051a486054e00b7492dfd
Content-Length: 0


Feb  1 07:59:12.141: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY PUBLIC IP;branch=z9hG4bK220BC34
Record-Route: <sip:172.20.40.7;lr>
Record-Route: <sip:217.10.68.150;lr;ftag=230325CC-1921>
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>;tag=as6a0d7701
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Contact: <sip:190049D1241736749872@217.10.67.11:5060>
Content-Type: application/sdp
Content-Length: 343

v=0
o=root 1459374857 1459374857 IN IP4 217.10.67.11
s=sipgate VoIP GW
c=IN IP4 212.9.44.186
t=0 0
m=audio 23522 RTP/AVP 8 0 18 101
a=silenceSupp:off - - - -
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:18 annexb=no
a=fmtp:101 0-16
a=sendrecv
a=rtcp:23523
a=ptime:20

Feb  1 07:59:12.145: //36134/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 183 Session Progress
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae149cff53b
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=551504~badef395-9309-48d9-8bf8-030362ac44b2-55015453
To: <sip:+491736749872@192.168.83.254>;tag=23033090-213D
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: b89b4a00-e3512fcd-1b8cc-c853a8c0@192.168.83.200
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Preferred-Identity: <sip:+491736749872@192.168.83.254>
Contact: <sip:190049D1241736749872@192.168.83.254:5060;transport=tcp>
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Session-ID: 2ef0fca8f9245695ac8b187badc32b63;remote=5ef89e0f7af051a486054e00b7492dfd
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 252

v=0
o=CiscoSystemsSIP-GW-UserAgent 220 9067 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 192.168.83.254
t=0 0
m=audio 17002 RTP/AVP 8 101
c=IN IP4 192.168.83.254
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

Feb  1 07:59:13.237: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
OPTIONS sip:192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae238647b18
From: <sip:192.168.83.200>;tag=492971018
To: <sip:192.168.83.254>
Date: Sat, 01 Feb 2020 07:59:13 GMT
Call-ID: bafda400-e3512fd1-1b8cd-c853a8c0@192.168.83.200
User-Agent: Cisco-CUCM12.0
CSeq: 101 OPTIONS
Contact: <sip:192.168.83.200:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


Feb  1 07:59:13.241: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae238647b18
From: <sip:192.168.83.200>;tag=492971018
To: <sip:192.168.83.254>;tag=230334DC-239A
Date: Sat, 01 Feb 2020 07:59:13 GMT
Call-ID: bafda400-e3512fd1-1b8cd-c853a8c0@192.168.83.200
Server: Cisco-SIPGateway/IOS-15.7.3.M5
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 376

v=0
o=CiscoSystemsSIP-GW-UserAgent 6441 9159 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 MY PUBLIC IP
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15
c=IN IP4 MY PUBLIC IP
m=image 0 udptl t38
c=IN IP4 MY PUBLIC IP
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

Feb  1 07:59:13.977: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
CANCEL sip:49366511397811@192.168.83.254:5060 SIP/2.0
Record-Route: <sip:217.10.68.150;lr;ftag=as2555b591>
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKc1a4.b990f1805556486a60ef5dc4029e14e3.0
Via: SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKc1a4.5e1fc4ee20c0782184fc0cd77e60e289.0
Max-Forwards: 67
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as2555b591
To: <sip:0049366511397811@sipconnect.sipgate.de>
Call-ID: 7fd1eae14a1f94a35df8beb31a57a33e@sipconnect.sipgate.de
CSeq: 103 CANCEL
Content-Length: 0


Feb  1 07:59:13.981: //36132/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKc1a4.b990f1805556486a60ef5dc4029e14e3.0,SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKc1a4.5e1fc4ee20c0782184fc0cd77e60e289.0
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as2555b591
To: <sip:0049366511397811@sipconnect.sipgate.de>
Date: Sat, 01 Feb 2020 07:59:13 GMT
Call-ID: 7fd1eae14a1f94a35df8beb31a57a33e@sipconnect.sipgate.de
CSeq: 103 CANCEL
Session-ID: 00000000000000000000000000000000;remote=5ef89e0f7af051a486054e00b7492dfd
Content-Length: 0


Feb  1 07:59:13.981: //36133/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Sent: 
CANCEL sip:7811@192.168.77.201:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220914BA
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=23031D84-240B
To: <sip:7811@192.168.77.201>
Date: Sat, 01 Feb 2020 07:59:07 GMT
Call-ID: 8E5F8C67-43FF11EA-89B8E80A-8109750A@192.168.83.254
CSeq: 101 CANCEL
Max-Forwards: 70
Timestamp: 1580543953
Reason: Q.850;cause=16
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=00000000000000000000000000000000
Content-Length: 0


Feb  1 07:59:13.981: //36132/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKc1a4.b990f1805556486a60ef5dc4029e14e3.0,SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKc1a4.5e1fc4ee20c0782184fc0cd77e60e289.0,SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKc1a4.58f8500896bf3e3d60ed149fd4ab5bd0.0,SIP/2.0/UDP 217.10.67.11:5060;branch=z9hG4bK2e76d6c4
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as2555b591
To: <sip:0049366511397811@sipconnect.sipgate.de>;tag=23031DE8-43D
Date: Sat, 01 Feb 2020 07:59:13 GMT
Call-ID: 7fd1eae14a1f94a35df8beb31a57a33e@sipconnect.sipgate.de
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Reason: Q.850;cause=16
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=00000000000000000000000000000000
Content-Length: 0


Feb  1 07:59:14.009: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
ACK sip:49366511397811@192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/UDP 217.10.68.150;branch=z9hG4bKc1a4.b990f1805556486a60ef5dc4029e14e3.0
Via: SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKc1a4.5e1fc4ee20c0782184fc0cd77e60e289.0
Max-Forwards: 67
From: "01752691155" <sip:01752691155@sipconnect.sipgate.de>;tag=as2555b591
To: <sip:0049366511397811@sipconnect.sipgate.de>;tag=23031DE8-43D
Call-ID: 7fd1eae14a1f94a35df8beb31a57a33e@sipconnect.sipgate.de
CSeq: 103 ACK
Content-Length: 0


Feb  1 07:59:14.033: //36133/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220914BA
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=23031D84-240B
To: <sip:22134146t7@192.168.77.201>
Date: Sat, 01 Feb 2020 07:59:14 GMT
Call-ID: 8E5F8C67-43FF11EA-89B8E80A-8109750A@192.168.83.254
Server: Cisco-CUCM12.0
CSeq: 101 CANCEL
Content-Length: 0


Feb  1 07:59:14.033: //36133/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220914BA
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=23031D84-240B
To: <sip:22134146t7@192.168.77.201>;tag=111403~badef395-9309-48d9-8bf8-030362ac44b2-55015452
Date: Sat, 01 Feb 2020 07:59:14 GMT
Call-ID: 8E5F8C67-43FF11EA-89B8E80A-8109750A@192.168.83.254
CSeq: 101 INVITE
Allow-Events: presence
Server: Cisco-CUCM12.0
Content-Length: 0


Feb  1 07:59:14.033: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
CANCEL sip:+491736749872@192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae149cff53b
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=551504~badef395-9309-48d9-8bf8-030362ac44b2-55015453
To: <sip:+491736749872@192.168.83.254>
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: b89b4a00-e3512fcd-1b8cc-c853a8c0@192.168.83.200
User-Agent: Cisco-CUCM12.0
CSeq: 101 CANCEL
Max-Forwards: 70
Privacy: none
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=2ef0fca8f9245695ac8b187badc32b63
Content-Length: 0


Feb  1 07:59:14.037: //36133/8E5EF03F89B2/SIP/Msg/ccsipDisplayMsg:
Sent: 
ACK sip:7811@192.168.77.201:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220914BA
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=23031D84-240B
To: <sip:22134146t7@192.168.77.201>;tag=111403~badef395-9309-48d9-8bf8-030362ac44b2-55015452
Date: Sat, 01 Feb 2020 07:59:07 GMT
Call-ID: 8E5F8C67-43FF11EA-89B8E80A-8109750A@192.168.83.254
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=00000000000000000000000000000000
Content-Length: 0


Feb  1 07:59:14.037: //36134/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae149cff53b
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=551504~badef395-9309-48d9-8bf8-030362ac44b2-55015453
To: <sip:+491736749872@192.168.83.254>
Date: Sat, 01 Feb 2020 07:59:14 GMT
Call-ID: b89b4a00-e3512fcd-1b8cc-c853a8c0@192.168.83.200
CSeq: 101 CANCEL
Session-ID: 2ef0fca8f9245695ac8b187badc32b63;remote=5ef89e0f7af051a486054e00b7492dfd
Content-Length: 0


Feb  1 07:59:14.041: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
CANCEL sip:+491736749872@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220BC34
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
CSeq: 102 CANCEL
Max-Forwards: 70
Timestamp: 1580543954
Reason: Q.850;cause=16
Content-Length: 0


Feb  1 07:59:14.041: //36134/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae149cff53b
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=551504~badef395-9309-48d9-8bf8-030362ac44b2-55015453
To: <sip:+491736749872@192.168.83.254>;tag=23033090-213D
Date: Sat, 01 Feb 2020 07:59:14 GMT
Call-ID: b89b4a00-e3512fcd-1b8cc-c853a8c0@192.168.83.200
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.7.3.M5
Reason: Q.850;cause=16
Session-ID: 2ef0fca8f9245695ac8b187badc32b63;remote=5ef89e0f7af051a486054e00b7492dfd
Content-Length: 0


Feb  1 07:59:14.045: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received: 
ACK sip:+491736749872@192.168.83.254:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.83.200:5060;branch=z9hG4bK1dae149cff53b
From: "01752691155" <sip:01752691155@192.168.83.200>;tag=551504~badef395-9309-48d9-8bf8-030362ac44b2-55015453
To: <sip:+491736749872@192.168.83.254>;tag=23033090-213D
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: b89b4a00-e3512fcd-1b8cc-c853a8c0@192.168.83.200
User-Agent: Cisco-CUCM12.0
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Privacy: none
Content-Length: 0


Feb  1 07:59:14.073: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 200 canceling
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY PUBLIC IP;branch=z9hG4bK220BC34
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>;tag=38f019e33a135542ca386fc4eada6cee-0c69
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
CSeq: 102 CANCEL
Content-Length: 0


Feb  1 07:59:14.073: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 192.168.83.254:5060;rport=64217;received=MY PUBLIC IP;branch=z9hG4bK220BC34
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>;tag=as6a0d7701
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces
Content-Length: 0


Feb  1 07:59:14.077: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
u allACK sip:+491736749872@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220BC34
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>;tag=as6a0d7701
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=2ef0fca8f9245695ac8b187badc32b63
Content-Length: 0
0 Helpful

Go to solution
TONY SMITH
Spotlight
Spotlight
In response to Chris9811

‎02-02-2020 04:10 AM

OK, so let's look at the Invite you're sending to the service provider for the diverted call leg.  Specifically the Diversion and P-Preferred-Identity.  We need to check firstly that your putting out the numbers that you intend, and secondly that the formatting an choice of optional headers matches the service providers requirements.

Diversion first.  You're presenting the number 2XXXX146t7 as the diverted number.  Is that correct?  I would not expect to see Xs in a phone number, and not sure the relevance of "t7" at the end either.  However this number complete with the t7 is what you have configured in your profile and I see some other settings forcing "t7" onto numbers.  I would have thought you'd want to show the original dialled number 49366511397811 to show it is a valid number being diverted.  However it depends on the service provider.

Secondly P-Preferred-Identity.  Has the SP specifically asked for this, it's not a default header so I guess somewhere you have explicitly enabled it.  I note the incoming invite from the SP doesn't use it.  Again to be confirmed with the SP, on a diverted call should this show the original calling number or the diverted number.

Maybe an idea to forward just this invite to the SP and ask them what's wrong with it.  Then we can work out how to accommodate their requirements.

 

Feb  1 07:59:09.385: //36135/B89B4A000000/SIP/Msg/ccsipDisplayMsg:
Sent: 
INVITE sip:+491736749872@217.10.68.150:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.83.254:5060;branch=z9hG4bK220A62F
From: "01752691155" <sip:22134146t7@217.10.68.150>;tag=230325CC-1921
To: <sip:22134146t7@217.10.68.150>
Date: Sat, 01 Feb 2020 07:59:09 GMT
Call-ID: 8FA3ACF8-43FF11EA-89BEE80A-8109750A@192.168.83.254
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 3097184768-0000065536-0000000190-3360925888
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1580543949
Contact: <sip:01752691155@192.168.83.254:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 64
P-Preferred-Identity: "01752691155" <sip:01752691155@192.168.83.254>
Diversion: "Christoph"<sip:2XXXX146t7@192.168.83.200>;privacy=off;reason=follow-me;screen=yes
Session-ID: 5ef89e0f7af051a486054e00b7492dfd;remote=00000000000000000000000000000000
Session-Expires:  1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 322

v=0
o=CiscoSystemsSIP-GW-UserAgent 9085 3972 IN IP4 192.168.83.254
s=SIP Call
c=IN IP4 MY PUBLIC IP
t=0 0
m=audio 17004 RTP/AVP 0 8 18 101
c=IN IP4 MY PUBLIC IP
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

Go to solution
Chris9811
Level 1
Level 1
In response to TONY SMITH

‎02-03-2020 11:47 PM

I have sent this INVITE to my Service Provider.

I will post the answer here and than i hope we can solve this problem.

Thank you for your help again. 

0 Helpful

Go to solution
Chris9811
Level 1
Level 1
In response to Chris9811

‎02-04-2020 01:09 AM - edited ‎02-04-2020 01:45 AM

So i  have a very fast provider. 

They answered me this:

You are sending the number in the P-Preferred-Identity header in the wrong format 01752691155:
P Preferred Identity: "01752691155" sip: 01752691155@192.168.83.254
The correct format would be 491752691155.

They also told me that they only need the correct P-Preferred-Identity header and than it has to work.

Am i correct if i say we dont need the diversion header?

How can i achive this and where i have to configure this? (CUCM or Cube)

 

We tested it with this change:

voice class sip-profiles 1
 request REGISTER sip-header From modify "(<.*:)(.*@)" "<sip:226XXX6t7@" 
 request ANY sip-header From modify "(<.*:)(.*@)" "<sip:226XXX6t7@" 
 request INVITE sip-header To modify "(<.*:)(.*@)" "<sip:226XXX6t7@" 
 request INVITE sip-header P-Preferred-Identity modify "(<.*:)(.*@)" "<sip:49366511234@"

This works! But we always see the same number 49366511234 on our mobile phones - so how can i get this working in dynamic mode?

0 Helpful

Go to solution
Ayodeji Okanlawon
VIP Alumni
VIP Alumni
In response to Chris9811

‎02-04-2020 01:52 AM

You need to modify your sip profile to have the valid DDI of all your extensions.

So if your extensions are 0175269XXXX

Then configure your PPI as follows

 

request INVITE sip-header P-Preferred-Identity modify  "<sip:0175269(.*)@(.*)>" "<sip:49175269\1@\2>"

 

 
 

 

Please rate all useful posts
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents