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
779
Views
3
Helpful
15
Replies

video calls not working (cisco ip phones 8865) in cisco ISR 4431

Bothra Group
Level 1
Level 1

‎07-06-2025 10:19 PM

Dear Team,

video calls are not working on cisco cme (cisco isr 4431). we are using cisco 8865 phones and registered in cisco 4331 Voice gateway.

Please do the needful

Labels:
Preview file
31 KB
0 Helpful
15 Replies 15

Leonardo Lacerda
Level 1
Level 1

‎07-08-2025 03:18 AM

Hello, 

Did video calls work before? Is there a specific scenario where video calls don't work? 

0 Helpful

Bothra Group
Level 1
Level 1
In response to Leonardo Lacerda

‎07-08-2025 09:24 PM

No. First time we configured Video Phones in cisco 4331

0 Helpful

wajidhassan
Level 4
Level 4

‎07-08-2025 07:06 AM

Video calls on Cisco 8865 phones with ISR 4431 CME often don’t work due to a few key reasons:

  • Insufficient bandwidth or missing QoS settings for video traffic.

  • Unsupported or misconfigured video codecs (like H.264) on the ISR or CME.

  • Video calling not enabled or set up properly on phones or CME.

  • Firewalls or access controls blocking video signaling or media ports.

  • Outdated or incompatible IOS on ISR or phone firmware.

Verifying and addressing these areas typically resolves video call problems.

0 Helpful

Bothra Group
Level 1
Level 1
In response to wajidhassan

‎07-08-2025 09:26 PM

Thank you wajid for key reasons. where should i configure h264 codec. unable to assign in voice register pool.

0 Helpful

Roger Kallberg
VIP
VIP
In response to Bothra Group

‎07-08-2025 10:35 PM

You’ll need to use a codec list where you put all the codecs that you intend to use and then use that on the CME phone configuration instead of individual codecs.



Response Signature


0 Helpful

Bothra Group
Level 1
Level 1
In response to Roger Kallberg

‎07-14-2025 06:02 AM

Dear Roger sir,

Do I need to create a "voice class codec list"? And where should I apply in my config.

 

0 Helpful

Roger Kallberg
VIP
VIP
In response to Bothra Group

‎07-14-2025 06:15 AM

Yes you do. It should be assigned to the phone device configuration in CME.



Response Signature


Bothra Group
Level 1
Level 1
In response to Roger Kallberg

‎07-14-2025 09:51 PM

Dear Roger ji,

I have created a codec list and applied it in the voice register pool, but I'm not having any luck. Video calls are not working, only voice calls are working. below is the config.

voice class codec 1
codec preference 1 g711ulaw
video codec h264
!


voice register pool 78
busy-trigger-per-button 2
id mac 08CC.A785.3F3A
type 8865
number 1 dn 78
dtmf-relay cisco-rtp
voice-class codec 1
camera
video
!
voice register pool 79
busy-trigger-per-button 2
id mac 08CC.A785.5C2C
type 8865
number 1 dn 79
dtmf-relay cisco-rtp
voice-class codec 1
camera
video

 

0 Helpful

Bothra Group
Level 1
Level 1
In response to Bothra Group

‎07-14-2025 10:26 PM

Dear Roger,

Please find the attached debug ccsip messages output.

 

Preview file
312 KB
0 Helpful

Roger Kallberg
VIP
VIP
In response to Bothra Group

‎07-14-2025 11:16 PM

There is simply too much clutter in your debug output to make it easy to identify the called attempts. For example there is a bunch of phone registration and unregistration events that takes up a significant portion of your debug data. Please collect a clean output that contains just the call attempts and please outline the called, calling number and time of each call so we can easily identify each call attempt.

What I do see in the shared data is this.

Sent: SIP UDP message from 172.17.40.8:5060 to 172.17.40.95:5060
SIP/2.0 484 Address Incomplete
That would indicate that the dialed number is incomplete and more numbers needs to be entered on the keypad.



Response Signature


Bothra Group
Level 1
Level 1
In response to Roger Kallberg

‎07-15-2025 12:35 AM

Dear Roger,

Please find the clean output. called number 167, and the calling number is 168.

 

 

 

Jul 15 06:30:22.717: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:167@172.17.40.8;user=phone SIP/2.0
Via: SIP/2.0/UDP 172.17.40.177:5060;branch=z9hG4bK1df8d283
From: "vd-2" <sip:168@172.17.40.8>;tag=08cca7855c2c0049010fa70d-0c0a62ad
To: <sip:167@172.17.40.8>
Call-ID: 08cca785-5c2c0007-10d2a6b1-32b93f62@172.17.40.177
Max-Forwards: 70
Session-ID: 21b45ef100105000a00008cca7855c2c;remote=00000000000000000000000000000000
Date: Tue, 15 Jul 2025 06:30:21 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CP8865/14.1.1
Contact: <sip:3339B66C-20F5@172.17.40.177:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP08CCA7855C2C";video
Expires: 180
Accept: application/sdp
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "vd-2" <sip:168@172.17.40.8>;party=calling;id-type=subscriber;privacy=off;screen=yes
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Recv-Info: conference
Recv-Info: x-cisco-conference
Content-Length: 1176
Content-Type: application/sdp
Content-Disposition: session;handling=optional

v=0
o=Cisco-SIPUA 18417 0 IN IP4 172.17.40.177
s=SIP Call
b=AS:4064
t=0 0
m=audio 19372 RTP/AVP 0 8 116 18 101
c=IN IP4 172.17.40.177
b=TIAS:64000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:116 iLBC/8000
a=fmtp:116 mode=20
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
m=video 27780 RTP/AVP 100 126 97
c=IN IP4 172.17.40.177
b=TIAS:4000000
a=rtpmap:100 H264/90000
a=fmtp:100 profile-level-id=640C16;packetization-mode=1;level-asymmetry-allowed=1;max-mbps=108000;max-fs=3600;max-rcmd-nalu-size=256000
a=imageattr:* recv [x=800,y=480,q=0.60] [x=1280,y=720,q=0.50]
a=rtpmap:126 H264/90000
a=fmtp:126 profile-level-id=428016;packetization-mode=1;level-asymmetry-allowed=1;max-mbps=108000;max-fs=3600;max-rcmd-nalu-size=256000
a=imageattr:* recv [x=800,y=480,q=0.60] [x=1280,y=720,q=0.50]
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=428016;packetization-mode=0;level-asymmetry-allowed=1;max-mbps=108000;max-fs=3600;max-rcmd-nalu-size=256000
a=imageattr:* recv [x=800,y=480,q=0.60] [x=1280,y=720,q=0.50]
a=rtcp-fb:* nack pli
a=rtcp-fb:* ccm fir
a=rtcp-fb:* ccm tmmbr
a=sendrecv

Jul 15 06:30:22.724: //5984845/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.17.40.177:5060;branch=z9hG4bK1df8d283
--More--
From: "vd-2" <sip:168@172.17.40.8>;tag=08cca7855c2c0049010fa70d-0c0a62ad
To: <sip:167@172.17.40.8>
Date: Tue, 15 Jul 2025 06:30:22 GMT
Call-ID: 08cca785-5c2c0007-10d2a6b1-32b93f62@172.17.40.177
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-17.6.1a
Session-ID: 00000000000000000000000000000000;remote=21b45ef100105000a00008cca7855c2c
Content-Length: 0


Jul 15 06:30:22.733: //5984847/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:167@172.17.40.227:5060 SIP/2.0
Via: SIP/2.0/UDP 172.17.40.8:5060;branch=z9hG4bK3DE4D1220
Remote-Party-ID: "vd-2" <sip:168@ap.ims.airtel.in>;party=calling;screen=yes;privacy=off
From: "vd-2" <sip:168@ap.ims.airtel.in>;tag=7AB0342B-7DF
To: <sip:167@172.17.40.227>
Date: Tue, 15 Jul 2025 06:30:22 GMT
Call-ID: 5299BB9-607C11F0-9721A909-A8177645@ap.ims.airtel.in
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 0086482923-1618743792-2535172361-2820109893
User-Agent: Cisco-SIPGateway/IOS-17.6.1a
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1752561022
Contact: <sip:168@172.17.40.8:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-ID: 21b45ef100105000a00008cca7855c2c;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 329

v=0
o=CiscoSystemsSIP-GW-UserAgent 7384 4629 IN IP4 172.17.40.8
s=SIP Call
c=IN IP4 172.17.40.8
t=0 0
m=audio 32072 RTP/AVP 0 121 19
c=IN IP4 172.17.40.8
a=rtpmap:0 PCMU/8000
a=rtpmap:121 frf-dialed-digit/8000
a=fmtp:121 0-15
a=rtpmap:19 CN/8000
a=ptime:20
m=video 0 RTP/AVP 255
c=IN IP4 172.17.40.8
b=TIAS:512000

Jul 15 06:30:22.738: //5984847/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.17.40.8:5060;branch=z9hG4bK3DE4D1220
From: "vd-2" <sip:168@ap.ims.airtel.in>;tag=7AB0342B-7DF
To: <sip:167@172.17.40.227>
Call-ID: 5299BB9-607C11F0-9721A909-A8177645@ap.ims.airtel.in
Session-ID: 41e1309000105000a00008cca7853f3a;remote=21b45ef100105000a00008cca7855c2c
Date: Tue, 15 Jul 2025 06:30:22 GMT
CSeq: 101 INVITE
Server: Cisco-CP8865/11.0.1
Contact: <sip:33135A21-53@172.17.40.227:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP08CCA7853F3A";video
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
--More--
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Content-Length: 0
Recv-Info: conference
Recv-Info: x-cisco-conference


Jul 15 06:30:22.897: //5984847/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.17.40.8:5060;branch=z9hG4bK3DE4D1220
From: "vd-2" <sip:168@ap.ims.airtel.in>;tag=7AB0342B-7DF
To: <sip:167@172.17.40.227>;tag=08cca7853f3a00060b3efeb5-540df836
Call-ID: 5299BB9-607C11F0-9721A909-A8177645@ap.ims.airtel.in
Session-ID: 41e1309000105000a00008cca7853f3a;remote=21b45ef100105000a00008cca7855c2c
Date: Tue, 15 Jul 2025 06:30:22 GMT
CSeq: 101 INVITE
Server: Cisco-CP8865/11.0.1
Contact: <sip:33135A21-53@172.17.40.227:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP08CCA7853F3A";video
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "vd-1" <sip:167@172.17.40.8>;party=called;id-type=subscriber;privacy=off;screen=yes
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Content-Length: 0


Jul 15 06:30:22.899: //5984845/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.17.40.177:5060;branch=z9hG4bK1df8d283
From: "vd-2" <sip:168@172.17.40.8>;tag=08cca7855c2c0049010fa70d-0c0a62ad
To: <sip:167@172.17.40.8>;tag=7AB034D2-224E
Date: Tue, 15 Jul 2025 06:30:22 GMT
Call-ID: 08cca785-5c2c0007-10d2a6b1-32b93f62@172.17.40.177
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "vd-1" <sip:167@ap.ims.airtel.in>;party=called;screen=yes;privacy=off
Contact: <sip:33135A21-53@172.17.40.8:5060>
Server: Cisco-SIPGateway/IOS-17.6.1a
Session-ID: 41e1309000105000a00008cca7853f3a;remote=21b45ef100105000a00008cca7855c2c
Content-Length: 0

Jul 15 06:30:27.578: //5984847/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.17.40.8:5060;branch=z9hG4bK3DE4D1220
From: "vd-2" <sip:168@ap.ims.airtel.in>;tag=7AB0342B-7DF
To: <sip:167@172.17.40.227>;tag=08cca7853f3a00060b3efeb5-540df836
Call-ID: 5299BB9-607C11F0-9721A909-A8177645@ap.ims.airtel.in
Session-ID: 41e1309000105000a00008cca7853f3a;remote=21b45ef100105000a00008cca7855c2c
Date: Tue, 15 Jul 2025 06:30:26 GMT
CSeq: 101 INVITE
Server: Cisco-CP8865/11.0.1
Contact: <sip:33135A21-53@172.17.40.227:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP08CCA7853F3A";video
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "vd-1" <sip:167@172.17.40.8>;party=called;id-type=subscriber;privacy=off;screen=yes
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Recv-Info: conference
Recv-Info: x-cisco-conference
Content-Length: 206
Content-Type: application/sdp
Content-Disposition: session;handling=optional

v=0
o=Cisco-SIPUA 13932 0 IN IP4 172.17.40.227
s=SIP Call
t=0 0
m=audio 22280 RTP/AVP 0
c=IN IP4 172.17.40.227
b=TIAS:64000
a=rtpmap:0 PCMU/8000
a=sendrecv
m=video 0 RTP/AVP 255
c=IN IP4 0.0.0.0

Jul 15 06:30:27.582: //5984847/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:33135A21-53@172.17.40.227:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 172.17.40.8:5060;branch=z9hG4bK3DE4E191F
From: "vd-2" <sip:168@ap.ims.airtel.in>;tag=7AB0342B-7DF
To: <sip:167@172.17.40.227>;tag=08cca7853f3a00060b3efeb5-540df836
Date: Tue, 15 Jul 2025 06:30:22 GMT
Call-ID: 5299BB9-607C11F0-9721A909-A8177645@ap.ims.airtel.in
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: 21b45ef100105000a00008cca7855c2c;remote=41e1309000105000a00008cca7853f3a
Content-Length: 0


Jul 15 06:30:27.586: //5984845/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.17.40.177:5060;branch=z9hG4bK1df8d283
From: "vd-2" <sip:168@172.17.40.8>;tag=08cca7855c2c0049010fa70d-0c0a62ad
To: <sip:167@172.17.40.8>;tag=7AB034D2-224E
--More--
Date: Tue, 15 Jul 2025 06:30:22 GMT
Call-ID: 08cca785-5c2c0007-10d2a6b1-32b93f62@172.17.40.177
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "vd-1" <sip:167@ap.ims.airtel.in>;party=called;screen=yes;privacy=off
Contact: <sip:167@172.17.40.8:5060>
Supported: replaces
Server: Cisco-SIPGateway/IOS-17.6.1a
Session-ID: 41e1309000105000a00008cca7853f3a;remote=21b45ef100105000a00008cca7855c2c
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 248

v=0
o=CiscoSystemsSIP-GW-UserAgent 7456 7292 IN IP4 172.17.40.8
s=SIP Call
c=IN IP4 172.17.40.8
t=0 0
m=audio 32078 RTP/AVP 0
c=IN IP4 172.17.40.8
a=rtpmap:0 PCMU/8000
a=ptime:20
m=video 0 RTP/AVP 100
c=IN IP4 172.17.40.8
b=TIAS:512000

Jul 15 06:30:27.595: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:167@172.17.40.8:5060 SIP/2.0
Via: SIP/2.0/UDP 172.17.40.177:5060;branch=z9hG4bK195d1d16
From: "vd-2" <sip:168@172.17.40.8>;tag=08cca7855c2c0049010fa70d-0c0a62ad
To: <sip:167@172.17.40.8>;tag=7AB034D2-224E
Call-ID: 08cca785-5c2c0007-10d2a6b1-32b93f62@172.17.40.177
Max-Forwards: 70
Session-ID: 21b45ef100105000a00008cca7855c2c;remote=41e1309000105000a00008cca7853f3a
Date: Tue, 15 Jul 2025 06:30:26 GMT
CSeq: 101 ACK
User-Agent: Cisco-CP8865/14.1.1
Remote-Party-ID: "vd-2" <sip:168@172.17.40.8>;party=calling;id-type=subscriber;privacy=off;screen=yes
Content-Length: 0
Recv-Info: conference
Recv-Info: x-cisco-conference

Jul 15 06:30:38.867: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:167@172.17.40.8:5060 SIP/2.0
Via: SIP/2.0/UDP 172.17.40.177:5060;branch=z9hG4bK4816f7e4
From: "vd-2" <sip:168@172.17.40.8>;tag=08cca7855c2c0049010fa70d-0c0a62ad
To: <sip:167@172.17.40.8>;tag=7AB034D2-224E
Call-ID: 08cca785-5c2c0007-10d2a6b1-32b93f62@172.17.40.177
Max-Forwards: 70
Session-ID: 21b45ef100105000a00008cca7855c2c;remote=41e1309000105000a00008cca7853f3a
Date: Tue, 15 Jul 2025 06:30:38 GMT
CSeq: 102 BYE
User-Agent: Cisco-CP8865/14.1.1
Content-Length: 0


Jul 15 06:30:38.871: //5984845/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.17.40.177:5060;branch=z9hG4bK4816f7e4
From: "vd-2" <sip:168@172.17.40.8>;tag=08cca7855c2c0049010fa70d-0c0a62ad

To: <sip:167@172.17.40.8>;tag=7AB034D2-224E
Date: Tue, 15 Jul 2025 06:30:38 GMT
Call-ID: 08cca785-5c2c0007-10d2a6b1-32b93f62@172.17.40.177
Server: Cisco-SIPGateway/IOS-17.6.1a
CSeq: 102 BYE
Reason: Q.850;cause=16
Session-ID: 41e1309000105000a00008cca7853f3a;remote=21b45ef100105000a00008cca7855c2c
Content-Length: 0


Jul 15 06:30:38.871: //5984847/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:33135A21-53@172.17.40.227:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 172.17.40.8:5060;branch=z9hG4bK3DE4F135F
From: "vd-2" <sip:168@ap.ims.airtel.in>;tag=7AB0342B-7DF
To: <sip:167@172.17.40.227>;tag=08cca7853f3a00060b3efeb5-540df836
Date: Tue, 15 Jul 2025 06:30:22 GMT
Call-ID: 5299BB9-607C11F0-9721A909-A8177645@ap.ims.airtel.in
User-Agent: Cisco-SIPGateway/IOS-17.6.1a
Max-Forwards: 70
Timestamp: 1752561038
CSeq: 102 BYE

Reason: Q.850;cause=16
Session-ID: 21b45ef100105000a00008cca7855c2c;remote=41e1309000105000a00008cca7853f3a
Content-Length: 0

Jul 15 06:30:39.024: //5984847/05279FEB971B/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.17.40.8:5060;branch=z9hG4bK3DE4F135F
From: "vd-2" <sip:168@ap.ims.airtel.in>;tag=7AB0342B-7DF
To: <sip:167@172.17.40.227>;tag=08cca7853f3a00060b3efeb5-540df836
--More--
Call-ID: 5299BB9-607C11F0-9721A909-A8177645@ap.ims.airtel.in
Session-ID: 41e1309000105000a00008cca7853f3a;remote=21b45ef100105000a00008cca7855c2c
Date: Tue, 15 Jul 2025 06:30:38 GMT
CSeq: 102 BYE
Server: Cisco-CP8865/11.0.1
Content-Length: 0

Jul 15 06:30:50.715: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
REGISTER sip:172.17.40.8 SIP/2.0
Via: SIP/2.0/UDP 172.17.40.177:5060;branch=z9hG4bK6f656006
From: <sip:168@172.17.40.8>;tag=08cca7855c2c004a23b0a170-557df242
To: <sip:168@172.17.40.8>
Call-ID: 08cca785-5c2c0002-38423ac0-1ca1fca7@172.17.40.177
Max-Forwards: 70
Session-ID: 9980499f00105000a00008cca7855c2c;remote=00000000000000000000000000000000
Date: Tue, 15 Jul 2025 06:30:49 GMT
CSeq: 161 REGISTER
User-Agent: Cisco-CP8865/14.1.1
Contact: <sip:3339B66C-20F5@172.17.40.177:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-08cca7855c2c>";+u.sip!devicename.ccm.cisco.com="SEP08CCA7855C2C";+u.sip!model.ccm.cisco.com="36225";video
--More--
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Content-Length: 0
Expires: 3600


Jul 15 06:30:50.717: //5984862/15D7A1199735/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.17.40.177:5060;branch=z9hG4bK6f656006
From: <sip:168@172.17.40.8>;tag=08cca7855c2c004a23b0a170-557df242
To: <sip:168@172.17.40.8>;tag=7AB0A17B-69F
Date: Tue, 15 Jul 2025 06:30:50 GMT
Call-ID: 08cca785-5c2c0002-38423ac0-1ca1fca7@172.17.40.177
Server: Cisco-SIPGateway/IOS-17.6.1a
CSeq: 161 REGISTER
Supported: X-cisco-cme-sis-9.0.0
Supported: X-cisco-srtp-fallback
Contact: <sip:168@172.17.40.177:5060>;expires=120
Expires: 120
Content-Length: 0


VTZ_ISR_4331#

 

0 Helpful

Roger Kallberg
VIP
VIP
In response to Bothra Group

‎07-15-2025 07:05 AM - edited ‎07-15-2025 10:39 PM

For future reference, it’s so much easier to work on the debug text if you put the output in a text file rather than directly in the inline text in the reply. Even so I looked through the text and wonder what is 172.17.40.227? It looks like the call might have gone via PSTN?



Response Signature


Bothra Group
Level 1
Level 1
In response to Roger Kallberg

‎07-15-2025 09:09 PM

IP 172.17.40.227 is the VOIP phone (called no 167) IP address sir

0 Helpful

Bothra Group
Level 1
Level 1
In response to Bothra Group

‎07-21-2025 12:11 AM

please do the needful.

0 Helpful
Customers Also Viewed These Support Documents