<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: CME Conference  Display Name - 3rd party SIP Phones in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/cme-conference-display-name-3rd-party-sip-phones/m-p/4062982#M42632</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Just to add some debug info. After the SIP phone enters the conference, the conference reply with UPDATE&lt;/P&gt;&lt;P&gt;and&amp;nbsp;&lt;STRONG&gt;Remote-Party-ID: "Conference" &amp;lt;sip:192.168.6.11&amp;gt;;party=called;screen=no;privacy=off&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;as the new ID.. How can I remove, block or deny the update message? It is really annoying not to see the Conf. ID.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the same issue with both 3rd party SIP phones, and Cisco SIP phones.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;*Apr 9 16:06:52.011: //19/F59B530E801B/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt;Sent:&lt;BR /&gt;SIP/2.0 180 Ringing&lt;BR /&gt;Via: SIP/2.0/UDP 192.168.6.100:54380;rport;branch=z9hG4bKPjf0162dff81f146c9a411055c7c770ce7&lt;BR /&gt;From: "test3" &amp;lt;sip:503@192.168.6.11&amp;gt;;tag=27dbfb25e35148c2a2cbb40ebba0ec80&lt;BR /&gt;To: &amp;lt;sip:101@192.168.6.11&amp;gt;;tag=17C168-12D0&lt;BR /&gt;Date: Thu, 09 Apr 2020 16:06:51 GMT&lt;BR /&gt;Call-ID: 731adee5973440e5a087737a6d8e21af&lt;BR /&gt;CSeq: 12504 INVITE&lt;BR /&gt;Require: 100rel&lt;BR /&gt;RSeq: 8355&lt;BR /&gt;Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER&lt;BR /&gt;Allow-Events: telephone-event&lt;BR /&gt;Remote-Party-ID: "101 Conference-DUCT1" &amp;lt;sip:1001@192.168.6.11&amp;gt;;party=called;screen=no;privacy=off&lt;BR /&gt;Contact: &amp;lt;sip:101@192.168.6.11:5060&amp;gt;&lt;BR /&gt;Server: Cisco-SIPGateway/IOS-15.6.3.M4&lt;BR /&gt;Session-ID: d26722b774615f76bf51491f64f48ff1;remote=50a45820630d5fe2b5119b4968e1e4ab&lt;BR /&gt;Content-Length: 0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;*Apr 9 16:06:52.015: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt;Received:&lt;BR /&gt;PRACK sip:101@192.168.6.11:5060 SIP/2.0&lt;BR /&gt;Via: SIP/2.0/UDP 192.168.6.100:54380;rport;branch=z9hG4bKPj8128e05a97e24882bb52737b23b73e17&lt;BR /&gt;Max-Forwards: 70&lt;BR /&gt;From: "test3" &amp;lt;sip:503@192.168.6.11&amp;gt;;tag=27dbfb25e35148c2a2cbb40ebba0ec80&lt;BR /&gt;To: &amp;lt;sip:101@192.168.6.11&amp;gt;;tag=17C168-12D0&lt;BR /&gt;Call-ID: 731adee5973440e5a087737a6d8e21af&lt;BR /&gt;CSeq: 12505 PRACK&lt;BR /&gt;RAck: 8355 12504 INVITE&lt;BR /&gt;Content-Length: 0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;*Apr 9 16:06:52.015: //19/F59B530E801B/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt;Sent:&lt;BR /&gt;SIP/2.0 200 OK&lt;BR /&gt;Via: SIP/2.0/UDP 192.168.6.100:54380;rport;branch=z9hG4bKPj8128e05a97e24882bb52737b23b73e17&lt;BR /&gt;From: "test3" &amp;lt;sip:503@192.168.6.11&amp;gt;;tag=27dbfb25e35148c2a2cbb40ebba0ec80&lt;BR /&gt;To: &amp;lt;sip:101@192.168.6.11&amp;gt;;tag=17C168-12D0&lt;BR /&gt;Date: Thu, 09 Apr 2020 16:06:52 GMT&lt;BR /&gt;Call-ID: 731adee5973440e5a087737a6d8e21af&lt;BR /&gt;Server: Cisco-SIPGateway/IOS-15.6.3.M4&lt;BR /&gt;CSeq: 12505 PRACK&lt;BR /&gt;Session-ID: 50a45820630d5fe2b5119b4968e1e4ab;remote=d26722b774615f76bf51491f64f48ff1&lt;BR /&gt;Content-Length: 0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;*Apr 9 16:06:52.015: //19/F59B530E801B/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt;Sent:&lt;BR /&gt;UPDATE sip:503@192.168.6.100:54380;ob SIP/2.0&lt;BR /&gt;Via: SIP/2.0/UDP 192.168.6.11:5060;branch=z9hG4bK213F6&lt;BR /&gt;From: &amp;lt;sip:101@192.168.6.11&amp;gt;;tag=17C168-12D0&lt;BR /&gt;To: "test3" &amp;lt;sip:503@192.168.6.11&amp;gt;;tag=27dbfb25e35148c2a2cbb40ebba0ec80&lt;BR /&gt;Date: Thu, 09 Apr 2020 16:06:52 GMT&lt;BR /&gt;Call-ID: 731adee5973440e5a087737a6d8e21af&lt;BR /&gt;User-Agent: Cisco-SIPGateway/IOS-15.6.3.M4&lt;BR /&gt;Max-Forwards: 70&lt;BR /&gt;Supported: timer,resource-priority,replaces&lt;BR /&gt;Timestamp: 1586448412&lt;BR /&gt;Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER&lt;BR /&gt;CSeq: 101 UPDATE&lt;BR /&gt;Contact: &amp;lt;sip:101@192.168.6.11:5060&amp;gt;&lt;BR /&gt;Min-SE: 1800&lt;BR /&gt;&lt;STRONG&gt;Remote-Party-ID: "Conference" &amp;lt;sip:192.168.6.11&amp;gt;;party=called;screen=no;privacy=off&lt;/STRONG&gt;&lt;BR /&gt;Call-Info: &amp;lt;urn:x-cisco-remotecc:callinfo&amp;gt;; orientation=to; security= unknown&lt;BR /&gt;Session-ID: d26722b774615f76bf51491f64f48ff1;remote=50a45820630d5fe2b5119b4968e1e4ab&lt;BR /&gt;Content-Length: 0&lt;/P&gt;</description>
    <pubDate>Thu, 09 Apr 2020 18:20:05 GMT</pubDate>
    <dc:creator>p3tter123</dc:creator>
    <dc:date>2020-04-09T18:20:05Z</dc:date>
    <item>
      <title>CME Conference  Display Name - 3rd party SIP Phones</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cme-conference-display-name-3rd-party-sip-phones/m-p/4057055#M42519</link>
      <description>&lt;P&gt;&lt;BR /&gt;Hi,&lt;/P&gt;&lt;P&gt;I have configured a CME as a conference bridge and with 3rd Party SIP phones.&lt;/P&gt;&lt;P&gt;My problem is when any of the SIP phones dials in to a conference the display name only say "Conference" on the SIP Phone and not the actual name of the conference.&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;SIP config:

voice register global
mode cme
source-address 192.168.6.11 port 5060
max-dn 300
max-pool 200
authenticate register
authenticate realm all
time-format 24
date-format D/M/Y
file text
create profile sync 0420545391215174
camera
video
auto-register
!
!

voice register dn 1
number 501
allow watch
name A TEST 1
label A TEST 1
!

!
voice register pool 1
id mac EEEE.EEEE.E501
number 1 dn 1
username test1 password test1234
codec g711ulaw
!

Conference Config:



sccp local GigabitEthernet0/0
sccp ccm 192.168.6.11 identifier 5 version 7.0 
sccp
!
sccp ccm group 111
bind interface GigabitEthernet0/0
associate ccm 5 priority 1
associate profile 10 register hwconf1
!
!
!
dspfarm profile 10 conference 
codec g711ulaw
maximum conference-participants 32
maximum sessions 32
conference-join custom-cptone conf-join
associate application SCCP



!
telephony-service
sdspfarm units 10
sdspfarm tag 1 hwconf1
conference hardware
no auto-reg-ephone
max-ephones 200
max-dn 400
ip source-address 192.168.6.11 port 2000&amp;nbsp;
time-zone 12
max-conferences 32 gain -6
transfer-system full-blind
transfer-pattern 1..
transfer-pattern 2..
transfer-pattern 3..
create cnf-files version-stamp Jan 01 2002 00:00:00
!



ephone-dn 21 octo-line
number 101
name Conference-TEST1
conference meetme unlocked
preference 1
allow watch
no huntstop
!
!
ephone-dn 22 octo-line
number 102
name Conference-TEST2
conference meetme unlocked
preference 1
allow watch
no huntstop
!

&lt;/PRE&gt;</description>
      <pubDate>Wed, 01 Apr 2020 18:37:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cme-conference-display-name-3rd-party-sip-phones/m-p/4057055#M42519</guid>
      <dc:creator>p3tter123</dc:creator>
      <dc:date>2020-04-01T18:37:12Z</dc:date>
    </item>
    <item>
      <title>Re: CME Conference  Display Name - 3rd party SIP Phones</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cme-conference-display-name-3rd-party-sip-phones/m-p/4062982#M42632</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Just to add some debug info. After the SIP phone enters the conference, the conference reply with UPDATE&lt;/P&gt;&lt;P&gt;and&amp;nbsp;&lt;STRONG&gt;Remote-Party-ID: "Conference" &amp;lt;sip:192.168.6.11&amp;gt;;party=called;screen=no;privacy=off&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;as the new ID.. How can I remove, block or deny the update message? It is really annoying not to see the Conf. ID.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the same issue with both 3rd party SIP phones, and Cisco SIP phones.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;*Apr 9 16:06:52.011: //19/F59B530E801B/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt;Sent:&lt;BR /&gt;SIP/2.0 180 Ringing&lt;BR /&gt;Via: SIP/2.0/UDP 192.168.6.100:54380;rport;branch=z9hG4bKPjf0162dff81f146c9a411055c7c770ce7&lt;BR /&gt;From: "test3" &amp;lt;sip:503@192.168.6.11&amp;gt;;tag=27dbfb25e35148c2a2cbb40ebba0ec80&lt;BR /&gt;To: &amp;lt;sip:101@192.168.6.11&amp;gt;;tag=17C168-12D0&lt;BR /&gt;Date: Thu, 09 Apr 2020 16:06:51 GMT&lt;BR /&gt;Call-ID: 731adee5973440e5a087737a6d8e21af&lt;BR /&gt;CSeq: 12504 INVITE&lt;BR /&gt;Require: 100rel&lt;BR /&gt;RSeq: 8355&lt;BR /&gt;Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER&lt;BR /&gt;Allow-Events: telephone-event&lt;BR /&gt;Remote-Party-ID: "101 Conference-DUCT1" &amp;lt;sip:1001@192.168.6.11&amp;gt;;party=called;screen=no;privacy=off&lt;BR /&gt;Contact: &amp;lt;sip:101@192.168.6.11:5060&amp;gt;&lt;BR /&gt;Server: Cisco-SIPGateway/IOS-15.6.3.M4&lt;BR /&gt;Session-ID: d26722b774615f76bf51491f64f48ff1;remote=50a45820630d5fe2b5119b4968e1e4ab&lt;BR /&gt;Content-Length: 0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;*Apr 9 16:06:52.015: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt;Received:&lt;BR /&gt;PRACK sip:101@192.168.6.11:5060 SIP/2.0&lt;BR /&gt;Via: SIP/2.0/UDP 192.168.6.100:54380;rport;branch=z9hG4bKPj8128e05a97e24882bb52737b23b73e17&lt;BR /&gt;Max-Forwards: 70&lt;BR /&gt;From: "test3" &amp;lt;sip:503@192.168.6.11&amp;gt;;tag=27dbfb25e35148c2a2cbb40ebba0ec80&lt;BR /&gt;To: &amp;lt;sip:101@192.168.6.11&amp;gt;;tag=17C168-12D0&lt;BR /&gt;Call-ID: 731adee5973440e5a087737a6d8e21af&lt;BR /&gt;CSeq: 12505 PRACK&lt;BR /&gt;RAck: 8355 12504 INVITE&lt;BR /&gt;Content-Length: 0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;*Apr 9 16:06:52.015: //19/F59B530E801B/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt;Sent:&lt;BR /&gt;SIP/2.0 200 OK&lt;BR /&gt;Via: SIP/2.0/UDP 192.168.6.100:54380;rport;branch=z9hG4bKPj8128e05a97e24882bb52737b23b73e17&lt;BR /&gt;From: "test3" &amp;lt;sip:503@192.168.6.11&amp;gt;;tag=27dbfb25e35148c2a2cbb40ebba0ec80&lt;BR /&gt;To: &amp;lt;sip:101@192.168.6.11&amp;gt;;tag=17C168-12D0&lt;BR /&gt;Date: Thu, 09 Apr 2020 16:06:52 GMT&lt;BR /&gt;Call-ID: 731adee5973440e5a087737a6d8e21af&lt;BR /&gt;Server: Cisco-SIPGateway/IOS-15.6.3.M4&lt;BR /&gt;CSeq: 12505 PRACK&lt;BR /&gt;Session-ID: 50a45820630d5fe2b5119b4968e1e4ab;remote=d26722b774615f76bf51491f64f48ff1&lt;BR /&gt;Content-Length: 0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;*Apr 9 16:06:52.015: //19/F59B530E801B/SIP/Msg/ccsipDisplayMsg:&lt;BR /&gt;Sent:&lt;BR /&gt;UPDATE sip:503@192.168.6.100:54380;ob SIP/2.0&lt;BR /&gt;Via: SIP/2.0/UDP 192.168.6.11:5060;branch=z9hG4bK213F6&lt;BR /&gt;From: &amp;lt;sip:101@192.168.6.11&amp;gt;;tag=17C168-12D0&lt;BR /&gt;To: "test3" &amp;lt;sip:503@192.168.6.11&amp;gt;;tag=27dbfb25e35148c2a2cbb40ebba0ec80&lt;BR /&gt;Date: Thu, 09 Apr 2020 16:06:52 GMT&lt;BR /&gt;Call-ID: 731adee5973440e5a087737a6d8e21af&lt;BR /&gt;User-Agent: Cisco-SIPGateway/IOS-15.6.3.M4&lt;BR /&gt;Max-Forwards: 70&lt;BR /&gt;Supported: timer,resource-priority,replaces&lt;BR /&gt;Timestamp: 1586448412&lt;BR /&gt;Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER&lt;BR /&gt;CSeq: 101 UPDATE&lt;BR /&gt;Contact: &amp;lt;sip:101@192.168.6.11:5060&amp;gt;&lt;BR /&gt;Min-SE: 1800&lt;BR /&gt;&lt;STRONG&gt;Remote-Party-ID: "Conference" &amp;lt;sip:192.168.6.11&amp;gt;;party=called;screen=no;privacy=off&lt;/STRONG&gt;&lt;BR /&gt;Call-Info: &amp;lt;urn:x-cisco-remotecc:callinfo&amp;gt;; orientation=to; security= unknown&lt;BR /&gt;Session-ID: d26722b774615f76bf51491f64f48ff1;remote=50a45820630d5fe2b5119b4968e1e4ab&lt;BR /&gt;Content-Length: 0&lt;/P&gt;</description>
      <pubDate>Thu, 09 Apr 2020 18:20:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cme-conference-display-name-3rd-party-sip-phones/m-p/4062982#M42632</guid>
      <dc:creator>p3tter123</dc:creator>
      <dc:date>2020-04-09T18:20:05Z</dc:date>
    </item>
  </channel>
</rss>

