cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Who Me Too'd this topic

CUCME 10 - Shared Line on 3rd Party SIP Device

Andre Lahl
Level 1
Level 1

Hey all,

I'm having a problem configuring a shared line on a Cisco IP-Phone 6941 and a 3rd party SIP device. When I call the shared line DN only the CP-6941 is ringing. Is there a known problem with shared line on 3rd party SIP devices on CUCME10?

My configuration:

 

voice service voip
 ip address trusted list
  ipv4 0.0.0.0 0.0.0.0
 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
  h225 timeout t302 3
 modem passthrough nse codec g711alaw redundancy maximum-sessions 15
 sip
  bind control source-interface GigabitEthernet0/0
  bind media source-interface GigabitEthernet0/0
  registrar server expires max 120 min 60

 

 

voice register global
 mode  cme
 source-address 10.16.1.250 port 5060
 timeouts interdigit 3
 max-dn 200
 max-pool 42
 load 6941 SIP69xx.9-3-3-2
 authenticate register
 authenticate realm lab.local
 timezone 23
 time-format 24
 date-format D/M/Y
 tftp-path flash:
 file text
 create profile sync 0021461723559918
 network-locale DE
 user-locale DE
 camera
 video

voice register dn  2
 number 7002
 name Test-Nr.2
 huntstop channel 2
 label Test-Nr.2

voice register dn  4
 number 2010
 shared-line
 huntstop channel 2

 

voice register pool  1
 id mac MAC-ADDRESS
 type 6941
 number 1 dn 4
 username test1 password test1
 codec g711ulaw
 no vad
!
voice register pool  2
 id mac MAC-ADDRESS
 type 6941
 number 1 dn 2
 username test2 password test2
 codec g711ulaw
 no vad
!
voice register pool  6
 id mac 0000.0000.0000
 number 1 dn 4
 username 2010 password 2010
 description Gigaset 2010
 codec g711ulaw
 no vad

 

show sip-ua status registrar
Line          destination      expires(sec)  contact
transport     call-id
              peer
============================================================
2010          10.16.0.3        22            10.16.0.3
UDP           1147098390@10_16_0_3
              40002

7002          10.16.0.2        59            10.16.0.2
UDP           a44c11d1-204e0006-00007348-00002b83@10.16.0.2
              40004

7001          10.16.0.1        59            10.16.0.1
UDP           a4934c40-6ddd0007-00004b72-000054c1@10.16.0.1
              40001

2010          10.16.0.1        59            10.16.0.1
UDP           a4934c40-6ddd0008-00007382-00007b13@10.16.0.1
              40003

 

40002  voip  up   up             2010$              0  syst ipv4:10.16.0.3:5060
40004  voip  up   up             7002$              0  syst ipv4:10.16.0.2:5060
40001  voip  up   up             7001$              0  syst ipv4:10.16.0.1:5060
40003  voip  up   up             2010$              0  syst ipv4:10.16.0.1:5060

 

As you can see, the number 2010 is registered two times on the CUCME. So the shared line is active on both devices. But there is still the problem with call alerting on the 3rd party device.

 

 

 

 

 

 

Who Me Too'd this topic