04-01-2020 11:37 AM
Hi,
I have configured a CME as a conference bridge and with 3rd Party SIP phones.
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.
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 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 !
04-09-2020 11:20 AM
Hi,
Just to add some debug info. After the SIP phone enters the conference, the conference reply with UPDATE
and Remote-Party-ID: "Conference" <sip:192.168.6.11>;party=called;screen=no;privacy=off
as the new ID.. How can I remove, block or deny the update message? It is really annoying not to see the Conf. ID.
I have the same issue with both 3rd party SIP phones, and Cisco SIP phones.
*Apr 9 16:06:52.011: //19/F59B530E801B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.6.100:54380;rport;branch=z9hG4bKPjf0162dff81f146c9a411055c7c770ce7
From: "test3" <sip:503@192.168.6.11>;tag=27dbfb25e35148c2a2cbb40ebba0ec80
To: <sip:101@192.168.6.11>;tag=17C168-12D0
Date: Thu, 09 Apr 2020 16:06:51 GMT
Call-ID: 731adee5973440e5a087737a6d8e21af
CSeq: 12504 INVITE
Require: 100rel
RSeq: 8355
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "101 Conference-DUCT1" <sip:1001@192.168.6.11>;party=called;screen=no;privacy=off
Contact: <sip:101@192.168.6.11:5060>
Server: Cisco-SIPGateway/IOS-15.6.3.M4
Session-ID: d26722b774615f76bf51491f64f48ff1;remote=50a45820630d5fe2b5119b4968e1e4ab
Content-Length: 0
*Apr 9 16:06:52.015: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:101@192.168.6.11:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.6.100:54380;rport;branch=z9hG4bKPj8128e05a97e24882bb52737b23b73e17
Max-Forwards: 70
From: "test3" <sip:503@192.168.6.11>;tag=27dbfb25e35148c2a2cbb40ebba0ec80
To: <sip:101@192.168.6.11>;tag=17C168-12D0
Call-ID: 731adee5973440e5a087737a6d8e21af
CSeq: 12505 PRACK
RAck: 8355 12504 INVITE
Content-Length: 0
*Apr 9 16:06:52.015: //19/F59B530E801B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.6.100:54380;rport;branch=z9hG4bKPj8128e05a97e24882bb52737b23b73e17
From: "test3" <sip:503@192.168.6.11>;tag=27dbfb25e35148c2a2cbb40ebba0ec80
To: <sip:101@192.168.6.11>;tag=17C168-12D0
Date: Thu, 09 Apr 2020 16:06:52 GMT
Call-ID: 731adee5973440e5a087737a6d8e21af
Server: Cisco-SIPGateway/IOS-15.6.3.M4
CSeq: 12505 PRACK
Session-ID: 50a45820630d5fe2b5119b4968e1e4ab;remote=d26722b774615f76bf51491f64f48ff1
Content-Length: 0
*Apr 9 16:06:52.015: //19/F59B530E801B/SIP/Msg/ccsipDisplayMsg:
Sent:
UPDATE sip:503@192.168.6.100:54380;ob SIP/2.0
Via: SIP/2.0/UDP 192.168.6.11:5060;branch=z9hG4bK213F6
From: <sip:101@192.168.6.11>;tag=17C168-12D0
To: "test3" <sip:503@192.168.6.11>;tag=27dbfb25e35148c2a2cbb40ebba0ec80
Date: Thu, 09 Apr 2020 16:06:52 GMT
Call-ID: 731adee5973440e5a087737a6d8e21af
User-Agent: Cisco-SIPGateway/IOS-15.6.3.M4
Max-Forwards: 70
Supported: timer,resource-priority,replaces
Timestamp: 1586448412
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 UPDATE
Contact: <sip:101@192.168.6.11:5060>
Min-SE: 1800
Remote-Party-ID: "Conference" <sip:192.168.6.11>;party=called;screen=no;privacy=off
Call-Info: <urn:x-cisco-remotecc:callinfo>; orientation=to; security= unknown
Session-ID: d26722b774615f76bf51491f64f48ff1;remote=50a45820630d5fe2b5119b4968e1e4ab
Content-Length: 0
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide