Buy or Renew
Buy or Renew
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
1673
Views
0
Helpful
19
Replies

DTMF is not working from PSTN to CUC

ali nasser
Level 1
Level 1

‎11-19-2023 12:27 AM

Dears,

 

I'm having an issue with DTMF from the PSTN to CUC. I tried all the changes as per the community, but no luck. 

 

The integration is SIP between the CUC and CUCM.

 

Call Flow:

ISP---->CUBE(SIP)-----> CUCM(SIP)------>CUC (SIP).

here are the dial-peers;

dial-peer voice 110 voip
description Calls in primary CUCM
destination-pattern 2...
session protocol sipv2
session target ipv4:172.16.65.12
voice-class codec 1
dtmf-relay rtp-nte
no vad
!

dial-peer voice 11 voip
description outbound to STC
translation-profile outgoing PSTN-OUT
destination-pattern 905........
session protocol sipv2
session target dns:fmc.stc.com.sa:5060
voice-class sip dtmf-relay force rtp-nte
voice-class sip profiles 21
voice-class sip bind control source-interface GigabitEthernet0/1
voice-class sip bind media source-interface GigabitEthernet0/1
dtmf-relay rtp-nte
codec g711alaw
no vad
!
dial-peer voice 1 voip
description inbound from STC
translation-profile incoming PSTN-IN
session protocol sipv2
session target ipv4:10.154.15.25
incoming called-number +9661T
voice-class sip bind control source-interface GigabitEthernet0/1
voice-class sip bind media source-interface GigabitEthernet0/1
dtmf-relay rtp-nte
codec g711alaw
no vad

 

voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
h323
sip
localhost dns:fmc.stc.com.sa
midcall-signaling passthru
sip-profiles 21

 

BR

 

 

Labels:
0 Helpful
19 Replies 19

Roger Kallberg
VIP
VIP

‎11-19-2023 01:43 AM

A few things, on dial peer 1, that is by your description used for inbound from your service provider, you don’t need to have a session target as that’s used on a outbound dial peer. Also you don’t have any inbound dial peer for your CM side of the call legs. Add that and use information in the VIA header to match the dial peer. You should make the same change on the inbound service provider dial peer. Lastly you should add an interface bind statement to your CM dial peers, both the one you have and the one I suggested you to add. Have a look at this great document for about all the details on IOS call routing that you probably never even thought about needing. Explain Cisco IOS and IOS XE Call Routing 



Response Signature


0 Helpful

ali nasser
Level 1
Level 1
In response to Roger Kallberg

‎11-19-2023 02:07 AM

Please check the below changes. Also i remove the session target on the incoming dial-peer it wouldn't work. attached is the debug.

dial-peer voice 110 voip
description Calls in primary CUCM
destination-pattern 2...
session protocol sipv2
session target ipv4:172.16.65.12
voice-class codec 1
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte
no vad
!
dial-peer voice 111 voip
destination-pattern 2...
session target ipv4:172.16.65.13
voice-class codec 1
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte
no vad
!
dial-peer voice 112 voip
destination-pattern 2...
session target ipv4:172.16.65.11
voice-class codec 1
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte
no vad
!
dial-peer voice 11 voip
description outbound to STC
translation-profile outgoing PSTN-OUT
destination-pattern 905........
session protocol sipv2
session target dns:fmc.stc.com.sa:5060
voice-class sip dtmf-relay force rtp-nte
voice-class sip profiles 21
voice-class sip bind control source-interface GigabitEthernet0/1
voice-class sip bind media source-interface GigabitEthernet0/1
dtmf-relay rtp-nte
codec g711alaw
no vad
!
dial-peer voice 1 voip
description inbound from STC
translation-profile incoming PSTN-IN
session protocol sipv2
session target ipv4:10.154.15.25
incoming called-number .
voice-class sip bind control source-interface GigabitEthernet0/1
voice-class sip bind media source-interface GigabitEthernet0/1
dtmf-relay rtp-nte
codec g711alaw
no vad

 

 

Preview file
129 KB
0 Helpful

Roger Kallberg
VIP
VIP
In response to ali nasser

‎11-19-2023 03:04 AM - edited ‎11-19-2023 04:24 AM

You’re not doing what I suggested. Please change so that you have these four dial peers.

  • Inbound from service provider, use information in the VIA header to match 
  • Outbound to service provider 
  • Inbound from CM, use the VIA header to match 
  • Outbound to CM, use a server group if you have more than one CM

Also as @Carlo Poggiarelli wrote you are missing the SIPv2 command on a couple of dial peers. Without this they would be H323 dial peers.

Where is session target ipv4:10.154.15.25 pointing to? As you said it doesn’t work without it it would be helpful to know where this points.



Response Signature


0 Helpful

ali nasser
Level 1
Level 1
In response to Roger Kallberg

‎11-19-2023 03:30 AM

Can you please tell me whats VIA header, also, can you post an example of the dial-peer voice Inbound from CM.

session target ipv4:10.154.15.25 pointing to SP.

 

BR

0 Helpful

Roger Kallberg
VIP
VIP
In response to ali nasser

‎11-19-2023 04:22 AM - edited ‎11-19-2023 05:45 AM

The VIA header is in the SIP SDP. If you read the document that I linked to you will find out how to match it in the inbound direction. Please read through the document and if you still have questions please get back.

Why are you pointing to the service provider with an IP on the inbound dial peer? That doesn’t make sense at all.



Response Signature


0 Helpful

Roger Kallberg
VIP
VIP
In response to ali nasser

‎11-19-2023 03:22 AM

In the debug you have this error message.

*Nov 19 09:33:45.170: //122882/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 500 Server Internal Error
Via: SIP/2.0/UDP 10.170.63.242:5060;branch=z9hG4bK1F7917B2
Call-ID: EB428544-7ADC11EE-B0BBFEFC-A53443B8
From: <sip:+9661110114276@fmc.stc.com.sa>;tag=57FFCC00-DA0
To: <sip:+9661110114276@fmc.stc.com.sa>;tag=hjdubygf
CSeq: 6163 REGISTER
Warning: 399 03011.02646.A.005.401.227.23.12.02210.00000000 "PBX IP User conflict"
Content-Length: 0

Quite likely there is something wrong with your configuration for the service provider. 



Response Signature


0 Helpful

Carlo Poggiarelli
VIP
VIP

‎11-19-2023 02:54 AM - edited ‎11-19-2023 02:54 AM

Hi ,

To add a tip to what @Roger Kallberg  correctly mentioned, please check that all DP have "session protocol sipv2" because there is some mixing of h323 and sip commands configured on DP 111 and DP 112.

 

Please let us know

 

Cheers

 

Carlo

Please rate all helpful posts "The more you help the more you learn"
0 Helpful

Carlo Poggiarelli
VIP
VIP

‎11-19-2023 04:52 AM - edited ‎11-19-2023 04:57 AM

Hi,

Can you please also send a complete output of a debug ccsip message while trying to call in hitting the voice mail ?

Please send also the output of a show sip-ua registrar status.

 

Thanks

Regards

 

Carlo

Please rate all helpful posts "The more you help the more you learn"
0 Helpful

ali nasser
Level 1
Level 1
In response to Carlo Poggiarelli

‎11-19-2023 10:16 PM

Hi,

Please check the below debug ccsip.
*Nov 20 05:47:00.013: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+966126384999@fmc.stc.com.sa;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Record-Route: <sip:10.154.15.25:5060;lr;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=10572>
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>
CSeq: 1 INVITE
Accept: application/sdp,application/3gpp-ims+xml
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
Contact: <sip:10.154.15.25:5060;Dpt=ee9a-200;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Max-Forwards: 61
Supported: timer,100rel,gruu
User-Agent: SM-A536E-WI1 Samsung IMS 6.0
Session-Expires: 1800
Min-SE: 600
P-Early-Media: supported
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Content-Length: 258
Content-Type: application/sdp

v=0
o=- 652106723 652106723 IN IP4 10.154.15.33
s=SBC call
c=IN IP4 10.154.15.33
t=0 0
m=audio 56630 RTP/AVP 8 0 18
b=AS:80
a=rtpmap:8 PCMA/8000
a=sendrecv
a=ptime:20
a=maxptime:80
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no

*Nov 20 05:47:00.013: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
CSeq: 1 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0


*Nov 20 05:47:00.017: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:2788@172.16.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211115C6
Remote-Party-ID: <sip:+966555767324@fmc.stc.com.sa>;party=calling;screen=no;privacy=off
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 0247146174-2258571758-2879782652-2771665848
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1700459220
Contact: <sip:+966555767324@172.16.65.20:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 60
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247

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

*Nov 20 05:47:00.021: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211115C6
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>
Date: Mon, 20 Nov 2023 06:11:38 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0


*Nov 20 05:47:00.029: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211115C6
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 06:11:38 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
CSeq: 101 INVITE
Require: 100rel
RSeq: 762292530
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Server: Cisco-CUCM14.0
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-ID: d1b6ddab94ca1c2a91ce7cba18845290;remote=d17a17d48427060b82e7504ab2469441
P-Asserted-Identity: <sip:2784@172.16.65.11>
Remote-Party-ID: <sip:2784@172.16.65.11>;party=called;screen=yes;privacy=off
Contact: <sip:2788@172.16.65.11:5060>
Content-Length: 0


*Nov 20 05:47:00.033: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
PRACK sip:2788@172.16.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK21122422
From: <sip:+966555767324@fmc.stc.com.sa>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
CSeq: 102 PRACK
RAck: 762292530 101 INVITE
Allow-Events: telephone-event
Max-Forwards: 70
Content-Length: 0


*Nov 20 05:47:00.033: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
CSeq: 1 INVITE
Require: 100rel
RSeq: 4531
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:2784@fmc.stc.com.sa>;party=called;screen=yes;privacy=off
Contact: <sip:2788@10.170.63.242:5060>
Record-Route: <sip:10.154.15.25:5060;lr;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=10572>
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0


*Nov 20 05:47:00.033: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK21122422
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 06:11:38 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
Server: Cisco-CUCM14.0
CSeq: 102 PRACK
Content-Length: 0


*Nov 20 05:47:00.413: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:2788@10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKuj7sbc7swijf9ubyd7yub7hdy;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
From: <tel:0555767324;noa=national;srvattri=national;phone-context=+966>;tag=ya2xsvax
To: <sip:0126384999;phone-context=fmc.stc.com.sa@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
CSeq: 2 PRACK
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
Max-Forwards: 62
Supported: sec-agree
User-Agent: SM-A536E-WI1 Samsung IMS 6.0
RAck: 4531 1 INVITE
Content-Length: 0


*Nov 20 05:47:00.413: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKuj7sbc7swijf9ubyd7yub7hdy;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
Server: Cisco-SIPGateway/IOS-15.2.4.M5
CSeq: 2 PRACK
Content-Length: 0


*Nov 20 05:47:00.413: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211115C6
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 06:11:38 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Supported: replaces
Server: Cisco-CUCM14.0
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uas
Require: timer
Session-ID: d1b6ddab94ca1c2a91ce7cba18845290;remote=d17a17d48427060b82e7504ab2469441
P-Asserted-Identity: "VoiceMail" <sip:2784@172.16.65.11>
Remote-Party-ID: "VoiceMail" <sip:2784@172.16.65.11>;party=called;screen=yes;privacy=off
Contact: <sip:2788@172.16.65.11:5060>;isFocus
Content-Type: application/sdp
Content-Length: 247

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

*Nov 20 05:47:00.417: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:2788@172.16.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211321EB
From: <sip:+966555767324@fmc.stc.com.sa>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


*Nov 20 05:47:00.417: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "VoiceMail" <sip:2784@fmc.stc.com.sa>;party=called;screen=yes;privacy=off
Contact: <sip:+966126384999@10.170.63.242:5060>
Record-Route: <sip:10.154.15.25:5060;lr;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=10572>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Session-Expires: 1800;refresher=uas
Require: timer
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 194

v=0
o=CiscoSystemsSIP-GW-UserAgent 4647 3811 IN IP4 10.170.63.242
s=SIP Call
c=IN IP4 10.170.63.242
t=0 0
m=audio 22136 RTP/AVP 8
c=IN IP4 10.170.63.242
a=rtpmap:8 PCMA/8000
a=ptime:20

*Nov 20 05:47:00.917: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "VoiceMail" <sip:2784@fmc.stc.com.sa>;party=called;screen=yes;privacy=off
Contact: <sip:+966126384999@10.170.63.242:5060>
Record-Route: <sip:10.154.15.25:5060;lr;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=10572>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Session-Expires: 1800;refresher=uas
Require: timer
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 194

v=0
o=CiscoSystemsSIP-GW-UserAgent 4647 3811 IN IP4 10.170.63.242
s=SIP Call
c=IN IP4 10.170.63.242
t=0 0
m=audio 22136 RTP/AVP 8
c=IN IP4 10.170.63.242
a=rtpmap:8 PCMA/8000
a=ptime:20

*Nov 20 05:47:01.005: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+966126384999@10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKwuihhfwjgfsqdfbysjiwfwqyu;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
From: <tel:0555767324;noa=national;srvattri=national;phone-context=+966>;tag=ya2xsvax
To: <sip:0126384999;phone-context=fmc.stc.com.sa@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
CSeq: 1 ACK
Max-Forwards: 62
User-Agent: SM-A536E-WI1 Samsung IMS 6.0
Content-Length: 0


*Nov 20 05:47:02.833: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKhsibjqbsh97dufuyfqfi95sqq;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff;X-HwDim=4
Call-ID: yyy9yc57iyf75bfj5iychyfwfdsguwsf@10.154.15.25
From: <sip:10.154.15.25>;tag=yi579f9y
To: <sip:10.170.63.242>
CSeq: 1 OPTIONS
Contact: <sip:10.154.15.25;Hpt=13c4_16>;expires=65535
Accept: application/sdp
Max-Forwards: 70
Content-Length: 0


*Nov 20 05:47:02.833: //129294/10697107ABAC/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKhsibjqbsh97dufuyfqfi95sqq;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff;X-HwDim=4
From: <sip:10.154.15.25>;tag=yi579f9y
To: <sip:10.170.63.242>;tag=5C5699FC-1CA1
Date: Mon, 20 Nov 2023 05:47:02 GMT
Call-ID: yyy9yc57iyf75bfj5iychyfwfdsguwsf@10.154.15.25
Server: Cisco-SIPGateway/IOS-15.2.4.M5
CSeq: 1 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: 374

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

*Nov 20 05:47:09.217: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:+966126384999@10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKwy7djyswqgwqbiwifjwiyyhf7;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
From: <tel:0555767324;noa=national;srvattri=national;phone-context=+966>;tag=ya2xsvax
To: <sip:0126384999;phone-context=fmc.stc.com.sa@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
CSeq: 3 BYE
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
Max-Forwards: 62
Supported: sec-agree
User-Agent: SM-A536E-WI1 Samsung IMS 6.0
P-Asserted-Identity: <sip:+966555767324@fmc.stc.com.sa>
Content-Length: 0


*Nov 20 05:47:09.217: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKwy7djyswqgwqbiwifjwiyyhf7;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:09 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
Server: Cisco-SIPGateway/IOS-15.2.4.M5
CSeq: 3 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=440,OS=70400,PR=401,OR=64160,PL=0,JI=0,LA=0,DU=8
Content-Length: 0


*Nov 20 05:47:09.217: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:2788@172.16.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK21149F7
From: <sip:+966555767324@fmc.stc.com.sa>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Max-Forwards: 70
Timestamp: 1700459229
CSeq: 103 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=401,OS=64160,PR=440,OR=70400,PL=0,JI=0,LA=0,DU=8
Content-Length: 0


*Nov 20 05:47:09.221: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK21149F7
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 06:11:48 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
Server: Cisco-CUCM14.0
CSeq: 103 BYE
Content-Length: 0

 

SIP-UA is attached.

 

 

Preview file
7 KB
0 Helpful

ali nasser
Level 1
Level 1
In response to Carlo Poggiarelli

‎11-19-2023 10:54 PM

Hi,

SIP-ua Status.

SIP User Agent for TLS over TCP : ENABLED
SIP User Agent bind status(signaling): DISABLED
SIP User Agent bind status(media): DISABLED
SIP early-media for 180 responses with SDP: ENABLED
SIP max-forwards : 70
SIP DNS SRV version: 2 (rfc 2782)
NAT Settings for the SIP-UA
Role in SDP: NONE
Check media source packets: DISABLED
Maximum duration for a telephone-event in NOTIFYs: 2000 ms
SIP support for ISDN SUSPEND/RESUME: ENABLED
Redirection (3xx) message handling: ENABLED
Reason Header will override Response/Request Codes: DISABLED
Out-of-dialog Refer: DISABLED
Presence support is DISABLED
protocol mode is ipv4

SDP application configuration:
Version line (v=) required
Owner line (o=) required
Timespec line (t=) required
Media supported: audio video image
Network types supported: IN
Address types supported: IP4 IP6
Transport types supported: RTP/AVP udptl

debug ccsip

*Nov 20 05:47:00.013: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+966126384999@fmc.stc.com.sa;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Record-Route: <sip:10.154.15.25:5060;lr;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=10572>
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>
CSeq: 1 INVITE
Accept: application/sdp,application/3gpp-ims+xml
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
Contact: <sip:10.154.15.25:5060;Dpt=ee9a-200;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Max-Forwards: 61
Supported: timer,100rel,gruu
User-Agent: SM-A536E-WI1 Samsung IMS 6.0
Session-Expires: 1800
Min-SE: 600
P-Early-Media: supported
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Content-Length: 258
Content-Type: application/sdp

v=0
o=- 652106723 652106723 IN IP4 10.154.15.33
s=SBC call
c=IN IP4 10.154.15.33
t=0 0
m=audio 56630 RTP/AVP 8 0 18
b=AS:80
a=rtpmap:8 PCMA/8000
a=sendrecv
a=ptime:20
a=maxptime:80
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no

*Nov 20 05:47:00.013: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
CSeq: 1 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0


*Nov 20 05:47:00.017: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:2788@172.16.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211115C6
Remote-Party-ID: <sip:+966555767324@fmc.stc.com.sa>;party=calling;screen=no;privacy=off
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 0247146174-2258571758-2879782652-2771665848
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1700459220
Contact: <sip:+966555767324@172.16.65.20:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 60
Session-Expires: 1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247

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

*Nov 20 05:47:00.021: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211115C6
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>
Date: Mon, 20 Nov 2023 06:11:38 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0


*Nov 20 05:47:00.029: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211115C6
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 06:11:38 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
CSeq: 101 INVITE
Require: 100rel
RSeq: 762292530
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Server: Cisco-CUCM14.0
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-ID: d1b6ddab94ca1c2a91ce7cba18845290;remote=d17a17d48427060b82e7504ab2469441
P-Asserted-Identity: <sip:2784@172.16.65.11>
Remote-Party-ID: <sip:2784@172.16.65.11>;party=called;screen=yes;privacy=off
Contact: <sip:2788@172.16.65.11:5060>
Content-Length: 0


*Nov 20 05:47:00.033: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
PRACK sip:2788@172.16.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK21122422
From: <sip:+966555767324@fmc.stc.com.sa>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
CSeq: 102 PRACK
RAck: 762292530 101 INVITE
Allow-Events: telephone-event
Max-Forwards: 70
Content-Length: 0


*Nov 20 05:47:00.033: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
CSeq: 1 INVITE
Require: 100rel
RSeq: 4531
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:2784@fmc.stc.com.sa>;party=called;screen=yes;privacy=off
Contact: <sip:2788@10.170.63.242:5060>
Record-Route: <sip:10.154.15.25:5060;lr;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=10572>
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0


*Nov 20 05:47:00.033: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK21122422
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 06:11:38 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
Server: Cisco-CUCM14.0
CSeq: 102 PRACK
Content-Length: 0


*Nov 20 05:47:00.413: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:2788@10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKuj7sbc7swijf9ubyd7yub7hdy;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
From: <tel:0555767324;noa=national;srvattri=national;phone-context=+966>;tag=ya2xsvax
To: <sip:0126384999;phone-context=fmc.stc.com.sa@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
CSeq: 2 PRACK
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
Max-Forwards: 62
Supported: sec-agree
User-Agent: SM-A536E-WI1 Samsung IMS 6.0
RAck: 4531 1 INVITE
Content-Length: 0


*Nov 20 05:47:00.413: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKuj7sbc7swijf9ubyd7yub7hdy;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
Server: Cisco-SIPGateway/IOS-15.2.4.M5
CSeq: 2 PRACK
Content-Length: 0


*Nov 20 05:47:00.413: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211115C6
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 06:11:38 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Supported: replaces
Server: Cisco-CUCM14.0
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uas
Require: timer
Session-ID: d1b6ddab94ca1c2a91ce7cba18845290;remote=d17a17d48427060b82e7504ab2469441
P-Asserted-Identity: "VoiceMail" <sip:2784@172.16.65.11>
Remote-Party-ID: "VoiceMail" <sip:2784@172.16.65.11>;party=called;screen=yes;privacy=off
Contact: <sip:2788@172.16.65.11:5060>;isFocus
Content-Type: application/sdp
Content-Length: 247

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

*Nov 20 05:47:00.417: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:2788@172.16.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK211321EB
From: <sip:+966555767324@fmc.stc.com.sa>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


*Nov 20 05:47:00.417: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "VoiceMail" <sip:2784@fmc.stc.com.sa>;party=called;screen=yes;privacy=off
Contact: <sip:+966126384999@10.170.63.242:5060>
Record-Route: <sip:10.154.15.25:5060;lr;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=10572>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Session-Expires: 1800;refresher=uas
Require: timer
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 194

v=0
o=CiscoSystemsSIP-GW-UserAgent 4647 3811 IN IP4 10.170.63.242
s=SIP Call
c=IN IP4 10.170.63.242
t=0 0
m=audio 22136 RTP/AVP 8
c=IN IP4 10.170.63.242
a=rtpmap:8 PCMA/8000
a=ptime:20

*Nov 20 05:47:00.917: //129292/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKc5qjdqgw77uf5gis9y979bhqc;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "VoiceMail" <sip:2784@fmc.stc.com.sa>;party=called;screen=yes;privacy=off
Contact: <sip:+966126384999@10.170.63.242:5060>
Record-Route: <sip:10.154.15.25:5060;lr;Hpt=8e42_16;CxtId=4;TRC=ffffffff-ffffffff;X-HwB2bUaCookie=10572>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Session-Expires: 1800;refresher=uas
Require: timer
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 194

v=0
o=CiscoSystemsSIP-GW-UserAgent 4647 3811 IN IP4 10.170.63.242
s=SIP Call
c=IN IP4 10.170.63.242
t=0 0
m=audio 22136 RTP/AVP 8
c=IN IP4 10.170.63.242
a=rtpmap:8 PCMA/8000
a=ptime:20

*Nov 20 05:47:01.005: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+966126384999@10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKwuihhfwjgfsqdfbysjiwfwqyu;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
From: <tel:0555767324;noa=national;srvattri=national;phone-context=+966>;tag=ya2xsvax
To: <sip:0126384999;phone-context=fmc.stc.com.sa@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
CSeq: 1 ACK
Max-Forwards: 62
User-Agent: SM-A536E-WI1 Samsung IMS 6.0
Content-Length: 0


*Nov 20 05:47:02.833: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKhsibjqbsh97dufuyfqfi95sqq;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff;X-HwDim=4
Call-ID: yyy9yc57iyf75bfj5iychyfwfdsguwsf@10.154.15.25
From: <sip:10.154.15.25>;tag=yi579f9y
To: <sip:10.170.63.242>
CSeq: 1 OPTIONS
Contact: <sip:10.154.15.25;Hpt=13c4_16>;expires=65535
Accept: application/sdp
Max-Forwards: 70
Content-Length: 0


*Nov 20 05:47:02.833: //129294/10697107ABAC/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKhsibjqbsh97dufuyfqfi95sqq;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff;X-HwDim=4
From: <sip:10.154.15.25>;tag=yi579f9y
To: <sip:10.170.63.242>;tag=5C5699FC-1CA1
Date: Mon, 20 Nov 2023 05:47:02 GMT
Call-ID: yyy9yc57iyf75bfj5iychyfwfdsguwsf@10.154.15.25
Server: Cisco-SIPGateway/IOS-15.2.4.M5
CSeq: 1 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: 374

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

*Nov 20 05:47:09.217: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:+966126384999@10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKwy7djyswqgwqbiwifjwiyyhf7;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
From: <tel:0555767324;noa=national;srvattri=national;phone-context=+966>;tag=ya2xsvax
To: <sip:0126384999;phone-context=fmc.stc.com.sa@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
CSeq: 3 BYE
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
Max-Forwards: 62
Supported: sec-agree
User-Agent: SM-A536E-WI1 Samsung IMS 6.0
P-Asserted-Identity: <sip:+966555767324@fmc.stc.com.sa>
Content-Length: 0


*Nov 20 05:47:09.217: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bKwy7djyswqgwqbiwifjwiyyhf7;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
From: <sip:+966555767324@fmc.stc.com.sa>;tag=ya2xsvax
To: <sip:+966126384999@fmc.stc.com.sa;user=phone>;tag=5C568F08-138F
Date: Mon, 20 Nov 2023 05:47:09 GMT
Call-ID: asbci5x3ijma7sx3v5xdy333dssimdsa2mmi@10.208.12.17
Server: Cisco-SIPGateway/IOS-15.2.4.M5
CSeq: 3 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=440,OS=70400,PR=401,OR=64160,PL=0,JI=0,LA=0,DU=8
Content-Length: 0


*Nov 20 05:47:09.217: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:2788@172.16.65.11:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK21149F7
From: <sip:+966555767324@fmc.stc.com.sa>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 05:47:00 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Max-Forwards: 70
Timestamp: 1700459229
CSeq: 103 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=401,OS=64160,PR=440,OR=70400,PL=0,JI=0,LA=0,DU=8
Content-Length: 0


*Nov 20 05:47:09.221: //129293/0EBB26BEABA5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.65.20:5060;branch=z9hG4bK21149F7
From: <sip:.*@fmc.stc.com.sa;user=phone>;tag=5C568EFC-2103
To: <sip:2788@172.16.65.11>;tag=2469441~8fe2d7c1-e5f8-45c5-adab-62eec32a4c54-18845287
Date: Mon, 20 Nov 2023 06:11:48 GMT
Call-ID: EBBC2E6-869F11EE-ABABFEFC-A53443B8@fmc.stc.com.sa
Server: Cisco-CUCM14.0
CSeq: 103 BYE
Content-Length: 0


*Nov 20 05:47:14.257: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.16.65.20:5060 SIP/2.0
Via: SIP/2.0/TCP 172.16.65.11:5060;branch=z9hG4bK162d4c50bbd1c1
From: <sip:172.16.65.11>;tag=96712174
To: <sip:172.16.65.20>
Date: Mon, 20 Nov 2023 06:11:53 GMT
Call-ID: b1d0a000-1ef1a56e-1576ad-b4110ac@172.16.65.11
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:172.16.65.11:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


*Nov 20 05:47:14.257: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.16.65.11:5060;branch=z9hG4bK162d4c50bbd1c1
From: <sip:172.16.65.11>;tag=96712174
To: <sip:172.16.65.20>;tag=5C56C69C-2638
Date: Mon, 20 Nov 2023 05:47:14 GMT
Call-ID: b1d0a000-1ef1a56e-1576ad-b4110ac@172.16.65.11
Server: Cisco-SIPGateway/IOS-15.2.4.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: 373

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

*Nov 20 05:47:19.609: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.16.65.20:5060 SIP/2.0
Via: SIP/2.0/TCP 172.16.65.12:5060;branch=z9hG4bK263a981ed69b1c
From: <sip:172.16.65.12>;tag=1734356844
To: <sip:172.16.65.20>
Date: Mon, 20 Nov 2023 06:11:58 GMT
Call-ID: b4cb9080-1ef1a56e-18a03a-c4110ac@172.16.65.12
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:172.16.65.12:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


*Nov 20 05:47:19.609: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.16.65.12:5060;branch=z9hG4bK263a981ed69b1c
From: <sip:172.16.65.12>;tag=1734356844
To: <sip:172.16.65.20>;tag=5C56DB84-AF2
Date: Mon, 20 Nov 2023 05:47:19 GMT
Call-ID: b4cb9080-1ef1a56e-18a03a-c4110ac@172.16.65.12
Server: Cisco-SIPGateway/IOS-15.2.4.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: 374

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

*Nov 20 05:47:32.833: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bK9ghfqfsu979ywscjdfy5ihbq5;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff;X-HwDim=4
Call-ID: c7wcfgybjd5jwfcbwjydisc97c5b5qyb@10.154.15.25
From: <sip:10.154.15.25>;tag=jwfdqquu
To: <sip:10.170.63.242>
CSeq: 1 OPTIONS
Contact: <sip:10.154.15.25;Hpt=13c4_16>;expires=65535
Accept: application/sdp
Max-Forwards: 70
Content-Length: 0


*Nov 20 05:47:32.833: //129297/224B1407ABAF/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bK9ghfqfsu979ywscjdfy5ihbq5;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff;X-HwDim=4
From: <sip:10.154.15.25>;tag=jwfdqquu
To: <sip:10.170.63.242>;tag=5C570F2C-1D3F
Date: Mon, 20 Nov 2023 05:47:32 GMT
Call-ID: c7wcfgybjd5jwfcbwjydisc97c5b5qyb@10.154.15.25
Server: Cisco-SIPGateway/IOS-15.2.4.M5
CSeq: 1 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: 375

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

*Nov 20 05:47:32.849: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.16.65.20:5060 SIP/2.0
Via: SIP/2.0/TCP 172.16.65.13:5060;branch=z9hG4bK252417c22fc3b
From: <sip:172.16.65.13>;tag=584472458
To: <sip:172.16.65.20>
Date: Mon, 20 Nov 2023 06:12:11 GMT
Call-ID: bc8b3500-1ef1a56e-251fb-d4110ac@172.16.65.13
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:172.16.65.13:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


*Nov 20 05:47:32.849: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.16.65.13:5060;branch=z9hG4bK252417c22fc3b
From: <sip:172.16.65.13>;tag=584472458
To: <sip:172.16.65.20>;tag=5C570F3C-1ED8
Date: Mon, 20 Nov 2023 05:47:32 GMT
Call-ID: bc8b3500-1ef1a56e-251fb-d4110ac@172.16.65.13
Server: Cisco-SIPGateway/IOS-15.2.4.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: 374

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

*Nov 20 05:48:02.833: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:10.170.63.242:5060 SIP/2.0
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bK7bs7jyd5di99uc55fjw55cdyb;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff;X-HwDim=4
Call-ID: s75dh7wyucqq7ss7s9d9hsjw597cwguw@10.154.15.25
From: <sip:10.154.15.25>;tag=y7ssccqc
To: <sip:10.170.63.242>
CSeq: 1 OPTIONS
Contact: <sip:10.154.15.25;Hpt=13c4_16>;expires=65535
Accept: application/sdp
Max-Forwards: 70
Content-Length: 0


*Nov 20 05:48:02.833: //129300/342CB707ABB1/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.154.15.25:5060;branch=z9hG4bK7bs7jyd5di99uc55fjw55cdyb;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff;X-HwDim=4
From: <sip:10.154.15.25>;tag=y7ssccqc
To: <sip:10.170.63.242>;tag=5C57845C-E4A
Date: Mon, 20 Nov 2023 05:48:02 GMT
Call-ID: s75dh7wyucqq7ss7s9d9hsjw597cwguw@10.154.15.25
Server: Cisco-SIPGateway/IOS-15.2.4.M5
CSeq: 1 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: 375

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

*Nov 20 05:48:15.549: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.16.65.20:5060 SIP/2.0
Via: SIP/2.0/TCP 172.16.65.11:5060;branch=z9hG4bK162d565c214c89
From: <sip:172.16.65.11>;tag=983137516
To: <sip:172.16.65.20>
Date: Mon, 20 Nov 2023 06:12:54 GMT
Call-ID: d62c7c80-1ef1a56e-1576b7-b4110ac@172.16.65.11
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:172.16.65.11:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


*Nov 20 05:48:15.549: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.16.65.11:5060;branch=z9hG4bK162d565c214c89
From: <sip:172.16.65.11>;tag=983137516
To: <sip:172.16.65.20>;tag=5C57B608-241C
Date: Mon, 20 Nov 2023 05:48:15 GMT
Call-ID: d62c7c80-1ef1a56e-1576b7-b4110ac@172.16.65.11
Server: Cisco-SIPGateway/IOS-15.2.4.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: 372

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

*Nov 20 05:48:18.393: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:fmc.stc.com.sa:5060 SIP/2.0
Via: SIP/2.0/UDP 10.170.63.242:5060;branch=z9hG4bK2115157
From: <sip:+9661110114276@fmc.stc.com.sa>;tag=5C57C124-1140
To: <sip:+9661110114276@fmc.stc.com.sa>
Date: Mon, 20 Nov 2023 05:48:18 GMT
Call-ID: EB428544-7ADC11EE-B0BBFEFC-A53443B8
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M5
Max-Forwards: 70
Timestamp: 1700459298
CSeq: 6531 REGISTER
Contact: <sip:+9661110114276@10.170.63.242:5060>
Expires: 3600
Supported: path
Content-Length: 0


*Nov 20 05:48:18.421: //129299/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 500 Server Internal Error
Via: SIP/2.0/UDP 10.170.63.242:5060;branch=z9hG4bK2115157
Call-ID: EB428544-7ADC11EE-B0BBFEFC-A53443B8
From: <sip:+9661110114276@fmc.stc.com.sa>;tag=5C57C124-1140
To: <sip:+9661110114276@fmc.stc.com.sa>;tag=fquiy5w9
CSeq: 6531 REGISTER
Warning: 399 03011.02646.A.005.401.227.23.12.02210.00000000 "PBX IP User conflict"
Content-Length: 0


*Nov 20 05:48:21.353: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:172.16.65.20:5060 SIP/2.0
Via: SIP/2.0/TCP 172.16.65.12:5060;branch=z9hG4bK263aa23e481d9e
From: <sip:172.16.65.12>;tag=1992734035
To: <sip:172.16.65.20>
Date: Mon, 20 Nov 2023 06:13:00 GMT
Call-ID: d9c00380-1ef1a56e-18a044-c4110ac@172.16.65.12
User-Agent: Cisco-CUCM14.0
CSeq: 101 OPTIONS
Contact: <sip:172.16.65.12:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0


*Nov 20 05:48:21.353: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 172.16.65.12:5060;branch=z9hG4bK263aa23e481d9e
From: <sip:172.16.65.12>;tag=1992734035
To: <sip:172.16.65.20>;tag=5C57CCB4-2660
Date: Mon, 20 Nov 2023 05:48:21 GMT
Call-ID: d9c00380-1ef1a56e-18a044-c4110ac@172.16.65.12
Server: Cisco-SIPGateway/IOS-15.2.4.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: 374

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

0 Helpful

Nithin Eluvathingal
VIP
VIP

‎11-19-2023 07:47 PM - edited ‎11-19-2023 07:48 PM

Find out which dial-peer is used by the gateway for the incoming and outgoing call leg. According to your original post, the gateway to CUCM is using a SIP trunk. You should either remove or shut down your h323 dial-peer 111 and 112, which have the same destination pattern as dial-peer 110, which is SIP. And try.

Btw what DTMF have you choose on CUCM SIP trunk page.



Response Signature


0 Helpful

ali nasser
Level 1
Level 1
In response to Nithin Eluvathingal

‎11-19-2023 10:10 PM

Hi Nithin,

 

I reconfigure the dial-peer of 111 and 112 as below.

dial-peer voice 110 voip
description Calls in primary CUCM
destination-pattern 2...
session protocol sipv2
session target ipv4:172.16.65.12
voice-class codec 1
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte
no vad
!
dial-peer voice 111 voip
destination-pattern 2...
session protocol sipv2
session target ipv4:172.16.65.13
voice-class codec 1
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte
no vad
!
dial-peer voice 112 voip
destination-pattern 2...
session protocol sipv2
session target ipv4:172.16.65.11
voice-class codec 1
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte
no vad

for the DTMF on the CUCM pointing to the CUBE "no preference"

0 Helpful

Roger Kallberg
VIP
VIP
In response to ali nasser

‎11-20-2023 12:21 AM

I would suggest you to do these changes.

voice class uri CUCM sip
 host ipv4:172.16.65.11
 host ipv4:172.16.65.12
 host ipv4:172.16.65.13
!
voice class uri PSTN sip
 host ipv4:10.154.15.25
!
voice class server-group 1
 ipv4 172.16.65.12 preference 1
 ipv4 172.16.65.13 preference 2
 ipv4 172.16.65.11 preference 3
 description Inbound calls from PSTN to CUCM
 huntstop 1 resp-code 404 to 404 !Very likely you will not have this command based on that you're using a very old IOS version
!
voice class sip-options-keepalive 1
 description Used for Server Group SIP OPTIONS PING
!
ip name-server <DNS server 1> <DNS server 2> ! add as many as you want/need
ip domain lookup source-interface GigabitEthernet0/0
ip domain name <your domain>


dial-peer voice 110 voip
 description Inbound calls to CUCM subscribers
 destination-pattern 2...
 session protocol sipv2
 no session target ipv4:172.16.65.12
 session server-group 1
 voice-class sip options-keepalive profile 1
 voice-class codec 1
 voice-class sip bind control source-interface GigabitEthernet0/0
 voice-class sip bind media source-interface GigabitEthernet0/0
 dtmf-relay rtp-nte sip-kpml
 fax-relay ecm disable
 no vad
!
no dial-peer voice 111 voip
!
no dial-peer voice 112 voip
!
dial-peer voice 100 voip
 description Outbound calls from CUCM
 modem passthrough nse codec g711ulaw
 session protocol sipv2
 incoming uri via CUCM
 voice-class codec 1  
 voice-class sip bind control source-interface GigabitEthernet0/0
 voice-class sip bind media source-interface GigabitEthernet0/0
 dtmf-relay rtp-nte sip-kpml
 fax-relay ecm disable
 no vad
!
dial-peer voice 11 voip
 description Outbound to STC
 translation-profile outgoing PSTN-OUT
 destination-pattern 905........
 session protocol sipv2
 session target dns:fmc.stc.com.sa:5060
 voice-class sip dtmf-relay force rtp-nte
 voice-class sip profiles 21
 voice-class sip bind control source-interface GigabitEthernet0/1
 voice-class sip bind media source-interface GigabitEthernet0/1
 dtmf-relay rtp-nte
 no codec g711alaw
 voice-class codec 1
 no vad
!
dial-peer voice 1 voip
 description Inbound from STC
 translation-profile incoming PSTN-IN
 session protocol sipv2
 no session target ipv4:10.154.15.25
 no incoming called-number .
 incoming uri via PSTN
 voice-class sip bind control source-interface GigabitEthernet0/1
 voice-class sip bind media source-interface GigabitEthernet0/1
 dtmf-relay rtp-nte
 no codec g711alaw
 voice-class codec 1
 no vad


Response Signature


0 Helpful

Nithin Eluvathingal
VIP
VIP
In response to ali nasser

‎11-20-2023 12:38 AM

Btw, what DTMF your ISP use in band or OOB ?. And have you tried DTMF for an outbound call. You can try calling an outside  IVR number and check if its working.

What exactly you trying with CUC, an IVR running on CUC ? have you tried calling the IVR from internal Extensions ?

Here in oman, ISP use in band DTMF but RFC 2833 disabled. CUCM supports only RFC 2833 and OOB. To make DTMF working we use LTI transcoder on Cube.

Invoking MTP on the  Trunk might fix your issues but it will be unclear why DTMF didn't work without MTP.

 



Response Signature


0 Helpful
Customers Also Viewed These Support Documents