7821 and 8831 CUCM 8.6

Do I need to buy licenses (UCL) for a new 7821 and 8831? I have a lot of DLU available in my CUCM 8.6.
Gino

Hi Angel,
You can refer the ordering guide and table 2.1
http://www.cisco.com/web/partners/downloads/partner/WWChannels/technology/ipc/downloads/UC_8_6_OG.pdf
The Cisco® IP Phone 7821 requires a Basic User Connect License (UCL) in order to connect to Cisco Unified Communications Manager. The Cisco® IP Phone 7841 and 7861 require an Enhanced User Connect License (UCL) in order to connect to Cisco Unified Communications Manager.
regds,
aman

Similar Messages

CUCM 8.6.2 Phones not registering 7841 and 8831

Hi all
I am trying to register some new phones - 7841 and 8831. We installed the COP and Device Pack and rebooted the cluster. Firmware defaults in the server are sip78xx.10-1-1SR2-1 and sip8831.9-3-3-5.
These are the first phones of these models that we are trying to use. All other devices are up and working. I added the phones manually, auto-reg is disabled. These new phones are both displaying the same behavior - they booted, but neither device will register. They are both running the the same firmware version configured as the default in the server.
I have looked at some other discussions but haven't seen any solutions that match up with our issue. Your input and ideas appreciated, thanks

I'm having this same problem. Over the weekend, I installed the latest device packs and restarted both servers in the cluster. I'm running CUCM 8.6.2 and the phones are 8831.
What's really strange is that the phone is getting incorrect info from the switch port. It's getting a DHCP address from the VLAN2 subnet, when it should be receiving an IP from the VLAN100 subnet.
VLAN2 = Data
VLAN100 = Voice
The original port config:
interface FastEthernet0/25
description Workstations on VLAN2 - Phones on VLAN 100
switchport access vlan 2
switchport trunk encapsulation dot1q
switchport trunk native vlan 2
switchport mode trunk
switchport voice vlan 100
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
mls qos trust device cisco-phone
mls qos trust cos
auto qos voip cisco-phone
spanning-tree portfast
end
I even changed the switch port configuration to this:
interface FastEthernet0/25
description Workstations on VLAN2 - Phones on VLAN 100
switchport access vlan 100
switchport trunk encapsulation dot1q
switchport trunk native vlan 100
switchport mode trunk
switchport voice vlan 100
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
mls qos trust device cisco-phone
mls qos trust cos
auto qos voip cisco-phone
spanning-tree portfast
end
VLAN 2 isn't even in the configuration, but the phone (even after a RESET) is still getting an IP from the DHCP server on VLAN2.
Very strange behavior.
Additional info:
The phone status menu is showing a continuous message of:
TFTP Timeout : SEPXXXXXXXXXXXX.cnf.xm.
No Trust List Installed.
Any suggestions / ideas would be appreciated.

7821 and CUCM 8.6.2 Support

HI, i need support for 7821 phones on an 8.6.2 CUCM cluster; do i need to install the first device pack that give support to the phone or i can install the latest or any newer device pack?
Thank you.

Because you just installed the FW for the phone, installing FW HAS NEVER been the way to add support for new devices, support for new devices can only be achieved 2 ways, there's a 3rd option, but it's rare
A) Upgrade to version with native support
B) Install the DevPack
C) For very, very few devices, there was a device enabler to add support for just one device, quite uncommon
So, to answer your question, yes, you need to install the DevPack on all your servers and then perform a cluster reboot. If you haven't read the README/RNs from the DevPack.

Bulk phone import and export CUCM 8.5

In preparation for a migration to CUCM 9.1.2 we need to update the owner ID field on around 7000 phones. The only way to do this through the bulk admin tool is to export phone all details, update the field and then re import all the phones. The export generates a .txt file. If I open this as an csv in excel it automatically chooses the column data types which messes with the number fields by stripping off leading 0s. If I try and import the data Excel says there are too many columns. How have others been able to work with the phone all details export?

If there is a Cisco utility to do this I would be greatful. To be honest I'm getting rather annoyed with this process. So far I've ran into these 2 bugs:
https://tools.cisco.com/bugsearch/bug/CSCsu97248
https://tools.cisco.com/bugsearch/bug/CSCtl87980
One of my colleagues has a created a script that goes through the exported file and fixes up the service parameters so we got around these. I piloted re-importing a couple of hundred devices and few spat out sql/db connection errors. I then tried to update another 400 phones the next night and although the validation goes fine, when I try and import i'm faced witha Memory allocation error:
sql.SQLException: Memory allocation failed during query processing.
I know this is most likely specific to our CUCM environment and we will be doing a restart tonight to hopefully resolve the issue (the TAC engineer suggested restarting the DB service). However it just seems like one issue after another to do a fairly simple task. The whole process of having to import every field on every phone to update one field is rediculous. I have a list of phone IDs and a list of users, why isn't there a way to define a custom file format and use the update option rather than having to re-insert all details?
This blogger wrote a cURL AXL script to pretty much do what I'm suggesting:
http://pandaeatsbamboo.blogspot.hk/2014/01/shell-script-to-update-device-user.html
However I have no prior experience with working with the CUCM Database via SQL and if anything goes wrong I would be stuffed.

Jabra BIZ 1900 Duo QD Not Working on 7821 and 6921

Hello,
We have a Jabra BIZ 1900 Duo QD headset connected to a 7821 IP Phone via it's headset jack. The problem is nothing can be heard from the headset. I don't know if this is a bug on the phone firmware or if there is a setting on the CUCM that would enable this.
CUCM is v10.5.
Thanks in advance.

Answer: The supplied connector by the supplier was not correct. So they replaced it with a different connector model.

UC560 and 8831 device

I have a UC560 which is EOL, along with a 7937 which is also EOL. Is there sw available to add a 8831 to the UC560 or am I simply out of luck.

Hi Ronco,
You're out of luck. Cisco 8831 is not supported on UC560. You can buy a ThirdParty Conference SIP Phone to register it on UC560.
Regards

Backup and Restore CUCM

Hello,
Cisco supports making snap shot of the Virtual Machines?
Regards
Leonardo Santana

Read here
Unified Communications VMware Requirements
http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements

UCCX 7.0.1SR5 to 8.0 upgrade while also adding LDAP integration for CUCM - what happens to agents and Historical Reporting data?

Current State:
•    I have a customer running CUCM 6.1 and UCCX 7.01SR5. Currently their CUCM is *NOT* LDAP integrated and using local accounts only. UCCX is AXL integrated to CUCM as usual and is pulling users from CUCM and using CUCM for login validation for CAD.
•    The local user accounts in CUCM currently match the naming format in active directory (John Smith in CUCM is jsmith and John Smith is jsmith in AD)
Goal:
•    Upgrade software versions and migrate to new hardware for UCCX
•    LDAP integrate the CUCM users
Desired Future State and Proposed Upgrade Method
Using the UCCX Pre Upgrade Tool (PUT), backup the current UCCX 7.01 server.
Then during a weekend maintenance window……
•    Upgrade the CUCM cluster from 6.1 to 8.0 in 2 step process
•    Integrate the CUCM cluster to corporate active directory (LDAP) - sync the same users that were present before, associate with physical phones, select the same ACD/UCCX line under the users settings as before
•    Then build UCCX 8.0 server on new hardware and stop at the initial setup stage
•    Restore the data from the UCCX PUT tool
•    Continue setup per documentation
At this point does UCCX see these agents as the same as they were before?
Is the historical reporting data the same with regards to agent John Smith (local CUCM user) from last week and agent John Smith (LDAP imported CUCM user) from this week ?
I have the feeling that UCCX will see the agents as different almost as if there is a unique identifier that's used in addition to the simple user name.
We can simplify this question along these lines
Starting at the beginning with CUCM 6.1 (local users) and UCCX 7.01. Let's say the customer decided to LDAP integrate the CUCM users and not upgrade any software.
If I follow the same steps with re-associating the users to devices and selecting the ACD/UCCX extension, what happens?
I would guess that UCCX would see all the users it knew about get deleted (making them inactive agents) and the see a whole group of new agents get created.
What would historical reporting show in this case? A set of old agents and a set of new agents treated differently?
Has anyone run into this before?
Is my goal possible while keeping the agent configuration and HR data as it was before?

I was doing some more research looking at the DB schema for UCCX 8.
Looking at the Resource table in UCCX, it looks like there is primary key that represents each user.
My question, is this key replicated from CUCM or created locally when the user is imported into UCCX?
How does UCCX determine if user account jsmith in CUCM, when it’s a local account, is different than user account jsmith in CUCM that is LDAP imported?
Would it be possible (with TAC's help most likely) to edit this field back to the previous values so that AQM and historical reporting would think the user accounts are the same?
Database table name: Resource
The Unified CCX system creates a new record in the Resource table when the Unified CCX system retrieves agent information from the Unified CM.
A Resource record contains information about the resource (agent). One such record exists for each active and inactive resource. When a resource is deleted, the old record is flagged as inactive; when a resource is updated, a new record is created and the old one is flagged as inactive.

CUE 8.5.1 NME-CUE web page setup no setup initialization and error: Login to CUCME failed

When first login in via the web page. When going to Configure menu and choosing CUCME to enter it manually, I get:
Error: Login to CUCME failed with the new values. Check the new CUCME configuration and enter the correct values.
hostname: 172.23.0.1
web user name: admin
web password: cisco
Sip gateway hostname: 172.23.0.1
ccn reporting historical
database local
description "se-172-23-0-2"
end reporting
ccn subsystem sip
gateway address "172.23.0.1"
mwi sip unsolicited
end subsystem
BR2-ROUTER#sh run
Building configuration...
Current configuration : 5264 bytes
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname BR2-ROUTER
boot-start-marker
boot-end-marker
card type t1 0 3
logging message-counter syslog
logging buffered 51200 warnings
no aaa new-model
clock timezone MST -7
clock summer-time MDT recurring
network-clock-participate wic 3
dot11 syslog
ip source-route
ip cef
ip dhcp excluded-address 172.21.0.1 172.21.0.49
ip dhcp excluded-address 172.21.0.59 172.21.0.254
ip dhcp excluded-address 172.20.0.1 172.20.0.10
ip dhcp pool CME
   network 172.21.0.0 255.255.255.0
   option 150 ip 172.21.0.1
   default-router 172.21.0.1
ip dhcp pool LAPTOPS
   network 172.20.0.0 255.255.255.0
   default-router 172.20.0.2
   dns-server 10.10.10.1
no ip domain lookup
ip domain name wilson.com
no ipv6 cef
multilink bundle-name authenticated
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
no supplementary-service h225-notify cid-update
sip
bind control source-interface GigabitEthernet0/0.20
bind media source-interface GigabitEthernet0/0.20
registrar server expires max 600 min 60
voice register global
mode cme
source-address 172.21.0.1 port 5060
max-dn 4
max-pool 4
authenticate register
timezone 12
time-format 24
date-format YY-M-D
voicemail 3600
tftp-path flash:
create profile sync 0021447056000116
ntp-server 174.137.67.50 mode directedbroadcast
voice register dn 1
number 3006
call-forward b2bua busy 3600
call-forward b2bua mailbox 3006
call-forward b2bua noan 3600 timeout 12
name rp-sip-1-16
label SIP 511-5016
mwi
voice register pool 1
id mac FCFB.FBCA.30CE
type 7965
number 1 dn 1
dtmf-relay rtp-nte
username 3006 password cisco
description 687-3006
codec g711ulaw
voice-card 0
username admin privilege 15 secret 5 $1$..D.$orbTsqgPSvNkMpfjjkg5q.
archive
log config
hidekeys
controller T1 0/3/0
cablelength long 0db
controller T1 0/3/1
cablelength long 0db
interface Loopback0
ip address 172.23.0.1 255.255.255.252
ip ospf network point-to-point
interface GigabitEthernet0/0
description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
no ip address
duplex auto
speed auto
interface GigabitEthernet0/0.10
encapsulation dot1Q 10 native
ip address 172.20.0.2 255.255.255.0
interface GigabitEthernet0/0.20
encapsulation dot1Q 20
ip address 172.21.0.1 255.255.255.0
interface GigabitEthernet0/0.30
encapsulation dot1Q 30
ip address 172.22.0.1 255.255.255.0
interface GigabitEthernet0/1
ip address 192.168.1.138 255.255.252.0
duplex auto
speed auto
interface Integrated-Service-Engine1/0
ip unnumbered Loopback0
service-module ip address 172.23.0.2 255.255.255.252
service-module ip default-gateway 172.23.0.1
no keepalive
ip forward-protocol nd
ip route 172.23.0.2 255.255.255.255 Integrated-Service-Engine1/0
ip http server
ip http access-class 23
ip http authentication local
no ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip http path flash:/gui
access-list 23 permit 10.10.10.0 0.0.0.7
nls resp-timeout 1
cpd cr-id 1
control-plane
ccm-manager fax protocol cisco
mgcp fax t38 ecm
dial-peer voice 3600 voip
destination-pattern 36..
session protocol sipv2
session target ipv4:192.168.1.144
dtmf-relay sip-notify
codec g711ulaw
no vad
sip-ua
retry invite 3
timers trying 400
mwi-server ipv4:192.168.1.144 expires 3600 port 5060 transport udp
gatekeeper
shutdown
telephony-service
no auto-reg-ephone
em logout 0:0 0:0 0:0
max-ephones 10
max-dn 10 no-reg both
ip source-address 172.23.0.1 port 2000
voicemail 3600
max-conferences 8 gain -6
call-forward pattern .T
web admin system name admin password cisco
dn-webedit
transfer-system full-consult
transfer-pattern .T
create cnf-files version-stamp Jan 01 2002 00:00:00
ephone-dn 1
number 3007
description 687-9898-3007
name Vatos locos
call-forward busy 3600
call-forward noan 3600 timeout 12
ephone-dn 2
number 3008
description 687-9898-3008
name Vatos locos2
call-forward busy 3600
call-forward noan 3600 timeout 12
ephone-dn 3 octo-line
number 3009
huntstop channel 6
ephone-dn 4
number 7999....
mwi on
ephone-dn 5
number 7998....
mwi off
ephone 1
device-security-mode none
description TESTTTTT
mac-address FCFB.FBCA.3406
max-calls-per-button 5
busy-trigger-per-button 4
type 7965
button 1:1 2:3
ephone 2
device-security-mode none
description TESTTTTT
mac-address FCFB.FBCA.3030
max-calls-per-button 4
busy-trigger-per-button 3
type 7965
button 1:2 2:3
line con 0
exec-timeout 0 0
logging synchronous
login local
line aux 0
line 66
no activation-character
no exec
transport preferred none
transport input all
transport output pad telnet rlogin lapb-ta mop udptn v120
line vty 0 4
access-class 23 in
privilege level 15
login local
transport input telnet
line vty 5 15
access-class 23 in
privilege level 15
login local
transport input telnet
scheduler allocate 20000 1000
ntp server 174.137.67.50
end
BR2-ROUTER#
Apr 12 2011 16:23:12 gui/admin_user.js
122     585532 Mar 30 2011 05:48:46 phone/7975/cnu75.8-3-2-27.sbn
123    2453636 Mar 30 2011 05:48:56 phone/7975/cvm75sccp.8-3-2-27.sbn
124     326315 Mar 30 2011 05:48:58 phone/7975/dsp75.8-3-2-27.sbn
125     557786 Mar 30 2011 05:49:00 phone/7975/jar75sccp.8-3-2-27.sbn
126        638 Mar 30 2011 05:49:02 phone/7975/SCCP75.8-3-3S.loads
127        642 Mar 30 2011 05:49:02 phone/7975/term75.default.loads
128          0 Mar 30 2011 05:49:02 phone/7941-7961
129    2494499 Mar 30 2011 05:49:12 phone/7941-7961/apps41.8-3-2-27.sbn
130     547146 Mar 30 2011 05:49:16 phone/7941-7961/cnu41.8-3-2-27.sbn
131       2340 Apr 02 2011 03:55:02 April012011.txt
132       3579 Apr 12 2011 03:52:42 softkeyDefault_kpml.xml
133         69 Apr 12 2011 03:52:40 syncinfo.xml
134       2682 Apr 12 2011 03:52:42 SEPFCFBFBCA30CE.cnf.xml
135       1882 Apr 12 2011 03:52:42 SIPDefault.cnf
136       3613 Apr 12 2011 03:52:42 softkeyDefault.xml
137       3987 Apr 12 2011 16:23:10 gui/admin_user.html
138       1029 Apr 12 2011 16:23:14 gui/CiscoLogo.gif
139        617 Apr 12 2011 16:23:14 gui/CME_GUI_README.TXT
140        953 Apr 12 2011 16:23:14 gui/Delete.gif
141      16344 Apr 12 2011 16:23:14 gui/dom.js
142        864 Apr 12 2011 16:23:16 gui/downarrow.gif
143       6146 Apr 12 2011 16:23:16 gui/ephone_admin.html
144       4558 Apr 12 2011 16:23:16 gui/logohome.gif
145       3866 Apr 12 2011 16:23:16 gui/normal_user.html
146      78428 Apr 12 2011 16:23:18 gui/normal_user.js
147       1347 Apr 12 2011 16:23:18 gui/Plus.gif
148        843 Apr 12 2011 16:23:18 gui/sxiconad.gif
149        174 Apr 12 2011 16:23:18 gui/Tab.gif
150       2431 Apr 12 2011 16:23:20 gui/telephony_service.html
151        870 Apr 12 2011 16:23:20 gui/uparrow.gif
152       9968 Apr 12 2011 16:23:20 gui/xml-test.html
153       3412 Apr 12 2011 16:23:20 gui/xml.template

Fixed. Routing issue:
Routing issue:
ip http access-class 23 !!!!!! Preconfigured from Factory
ip http authentication local
no ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip http path flash:/gui
access-list 23 permit 10.10.10.0 0.0.0.7 !!!!!! Preconfigured from Factory
To fix
No ip http access-class 23

CUCM and Avaya CS1000 SIP connection

                   Hello - looking for some help on a SIP trunk configuration between the 2 devices. Currently we are running CUCM 9.1 with Avaya Session Manager 6.3. We are having issues with the call completing from the CS 1000 to the CUCM. Below are the session traces from both the Session Manager and CUCM. The CS1000 currently has 4 digit extensions and the CUCM has 7 digit extensions. We translate the number in the Session Manager to send the 7 digits. If you could lead in the right direction I would appreciate it. WOuld this have something to do with the context coming out of Session Manager? It looks like CDP.UDP and then only the 4 digits and the CUCM needs the 7. I also attached the configurations guide used for this.
Session Manager trace:
   mil-ss-01                 CUCM 9
                       SM100                10.101.2.75             10.174.2.75
13:04:53.730 |<--OPTIONS-|           |           |           |           | (1) sip:10.5.1.30
13:04:53.731 |--200 OK-->|           |           |           |           | (1) 200 OK (OPTIONS)
13:04:53,734 |                    Request Adaptation                     | Adapter: mil-ss-01
13:04:53,734 |                    Request Adaptation                     | Adapter: mil-ss-01
13:04:56.183 |--INVITE-->|           |           |           |           | (2) T:7317;phone-context=cdp.udp F:anonymous@anonymous U:7317;phone-context=cdp.udp
13:04:56.184 |<--Trying--|           |           |           |           | (2) 100 Trying
13:04:56,185 |                  Remote host is trusted                   | Trusted
13:04:56,185 |                    Request Adaptation                     | Adapter: mil-ss-01
13:04:56,186 |                Applied ingress Adaptation                 | P-Asserted-Identity=<sip:[email protected]>, Request-URI=sip:[email protected], History-Info=<sip:[email protected]>;index=1, <sip:[email protected]>;index=1.1
13:04:56,186 |                Originating Location found                 | Location: mil-cs1000m-01
13:04:56,186 |        Try routing to determine if emergency call         | Location: mil-cs1000m-01
13:04:56,186 |                Request Dial Pattern route                 | for: sip:[email protected] Location: mil-cs1000m-01
13:04:56,186 |               Dial Pattern route parameters               | URI Domain: company.com Location: mil-cs1000m-01
13:04:56,186 |                 Trying Dial Pattern route                 | Domain: company.com Location: mil-cs1000m-01
13:04:56,186 |                    Dial Pattern found                     | for: 7317 Pattern: 7317
13:04:56,186 |                    Route Policy found                     | Pattern: 7317 RoutePolicyList: to_CUCM9
13:04:56,187 |                        Route found                        | for: sip:[email protected] SIPEntity: CUCM 9
13:04:56,187 |                     Entity Link found                     | SIPEntity: CUCM 9 EntityLink: mil-sessionmgr-01->TCP, biDirId=null, deny=false:5060
13:04:56,187 |                    Request Adaptation                     | Adapter: CUCM 9
13:04:56,188 |                 Applied egress Adaptation                 | NoAdaptationModuleExists=true, Request-URI=sip:[email protected];routeinfo=0-0, Remote-Party-ID=<sip:[email protected]>;party=calling;screen=no;privacy=off,
13:04:56,188 |                    Routing SIP request                    | SipEntity: CUCM 9 EntityLink: mil-sessionmgr-01->TCP:5060
13:04:56,189 |              No hostname resolution required              | Routing to: sip:10.5.131.12;transport=tcp;lr;phase=terminating
13:04:56.191 |           |--INVITE-->|           |           |           | (2) T:7317;phone-context=cdp.udp F:anonymous@anonymous U:7657317 P:terminating
13:04:56.196 |           |<--Trying--|           |           |           | (2) 100 Trying
13:04:56.198 |           |<--Not Fou-|           |           |           | (2) 404 Not Found
13:04:56.199 |           |----ACK--->|           |           |           | (2) sip:[email protected]
13:04:56,200 |                    Request Adaptation                     | Adapter: CUCM 9
13:04:56,201 |                    Request Adaptation                     | Adapter: CUCM 9
13:04:56,201 |                    Request Adaptation                     | Adapter: mil-ss-01
13:04:56.202 |<--Not Fou-|           |           |           |           | (2) 404 Not Found
13:04:56.203 |----ACK--->|           |           |           |           | (2) sip:7317
13:05:07,597 |                Remote host is not trusted                 | Host not trusted
13:05:07,597 |                Originating Location found                 | Location: mil-cs1000m-01
13:05:12.657 |           |<--------OPTIONS-------|           |           | (3) sip:10.5.2.51
13:05:12,659 |                Remote host is not trusted                 | Host not trusted
13:05:12,659 |                Originating Location found                 | Location: mil-cs1000m-01
13:05:12.660 |           |--------200 OK-------->|           |           | (3) 200 OK (OPTIONS)
13:05:16.877 |           |<--------------OPTIONS-------------|           | (4) sip:10.5.2.51
13:05:16,879 |                  Remote host is trusted                   | Trusted
13:05:16,879 |                    Request Adaptation                     | Adapter: mil-ss-01
13:05:16,879 |                Applied ingress Adaptation                 | P-Asserted-Identity=<sip:[email protected]>
13:05:16,879 |                Originating Location found                 | Location: sas-cs1000e-01
13:05:16.880 |           |--------------200 OK-------------->|           | (4) 200 OK (OPTIONS)
13:05:24.463 |           |<--------------------OPTIONS-------------------| (5) sip:10.5.2.51
13:05:24,465 |                Remote host is not trusted                 | Host not trusted
13:05:24,465 |                Originating Location found                 | Location: mil-cs1000m-01
13:05:24.466 |           |--------------------200 OK-------------------->| (5) 200 OK (OPTIONS)
CUCM Trace Invite:
SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.5.2.51 on port 46314 index 6 with 3188 bytes:
[1179,NET]
INVITE sip:[email protected] SIP/2.0
P-AV-Message-Id: 1_1
Route: <sip:10.5.131.12;transport=tcp;lr;phase=terminating>
History-Info: <sip:[email protected]>;index=1, <sip:[email protected]>;index=1.1
Remote-Party-ID: <sip:[email protected]>;party=calling;screen=no;privacy=off
Allow: INVITE, ACK, BYE, REGISTER, REFER, NOTIFY, CANCEL, PRACK, OPTIONS, INFO, SUBSCRIBE, UPDATE
Contact: <sip:00000000;[email protected]:5060;maddr=10.5.1.30;transport=tcp;user=phone;gsid=68cac530-5d21-11e3-8b45-78e3b505dc88>
Alert-Info: <cid:[email protected]>
Supported: 100rel, x-nortel-sipvc, replaces
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3
Via: SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974
Via: SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140
Via: SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
Record-Route: <sip:[email protected];transport=tcp;lr>
Record-Route: <sip:10.5.2.50:15060;transport=tcp;ibmsid=local.1372169047609_2400497_2400521;lr>
Record-Route: <sip:[email protected];transport=tcp;lr>
P-Charging-Vector: icid-value="68cac530-5d21-11e3-8b45-78e3b505dc88"
User-Agent: Nortel CS1000 SIP GW release_7.0 version_linux-6.50.00 AVAYA-SM-6.3.1.0.631004
P-Asserted-Identity: <sip:[email protected]>
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
Max-Forwards: 66
CSeq: 1 INVITE
Content-Type: multipart/mixed;boundary=unique-boundary-1
Content-Length: 1063
Av-Global-Session-ID: 68cac530-5d21-11e3-8b45-78e3b505dc88
P-Location: SM;origlocname="mil-cs1000m-01";origsiglocname="mil-cs1000m-01";origmedialocname="mil-cs1000m-01";termlocname="Cisco BE6K";termsiglocname="Cisco BE6K";smaccounting="true"
--unique-boundary-1
Content-Type: application/sdp
SDP Message
====================================================
v=0
o=- 746 1 IN IP4 10.5.1.30
s=-
c=IN IP4 10.5.1.36
t=0 0
m=audio 5234 RTP/AVP 18 0 8 101 111
c=IN IP4 10.5.1.36
a=tcap:1 RTP/SAVP
a=crypto:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
a=crypto:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
a=pcfg:1 t=1
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:111 X-nt-inforeq/8000
a=ptime:20
a=sendrecv
--unique-boundary-1
Content-Type: application/x-nt-mcdn-frag-hex;version=linux-6.50.00;base=x2611
Content-Disposition: signal;handling=optional
0500bc05
0107130081900000a200
09090f00e9a4830001004000
1315070011fa0f00a10d02010102020100cc040000c56000
1e0403008183
4a1c0100180001001a011404000067353505000004000000000048710000
--unique-boundary-1
Content-Type: application/x-nt-epid-frag-hex;version=linux-6.50.00;base=x2611
Content-Disposition: signal;handling=optional
011201
3c:4a:92:f4:84:f4
--unique-boundary-1--
CUCM Trying Message:
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1180,NET]
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Content-Length: 0
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1181,NET]
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Content-Length: 0
SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.5.2.51 on port 46314 index 6 with 623 bytes:
[1182,NET]
ACK sip:[email protected] SIP/2.0
Route: <sip:10.5.131.12;transport=tcp;lr;phase=terminating>
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3
Via: SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974
CSeq: 1 ACK
Max-Forwards: 66
Content-Length: 0
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1180,NET]
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Content-Length: 0
CUCM not found message:
SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.5.2.51 on port 46314 index 6
[1181,NET]
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3,SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974,SIP/2.0/TCP 10.5.2.50:15060;rport;ibmsid=local.1372169047609_2400497_2400521;branch=z9hG4bK129750805377494,SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb-AP;ft=19;received=10.5.2.51;rport=19140,SIP/2.0/TCP 10.5.1.30:5060;branch=z9hG4bK-3fa2ea5-894636b6-7d11effb
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Date: Wed, 04 Dec 2013 19:12:41 GMT
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
CSeq: 1 INVITE
Allow-Events: presence
Reason: Q.850;cause=1
Content-Length: 0
CUCM ACK message:
SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.5.2.51 on port 46314 index 6 with 623 bytes:
[1182,NET]
ACK sip:[email protected] SIP/2.0
Route: <sip:10.5.131.12;transport=tcp;lr;phase=terminating>
Call-ID: abef5b48-1e01050a-13c4-55013-3fa2ea5-5d08551f-3fa2ea5
From: <sip:[email protected];user=phone>;tag=ac493fe8-1e01050a-13c4-55013-3fa2ea5-2b7d5ad-3fa2ea5
To: <sip:7317;[email protected];user=phone>;tag=580~35abe322-3212-479c-8a2c-ab75ead590d5-21575914
Via: SIP/2.0/TCP 10.5.2.51;branch=z9hG4bK138498682095974-AP;ft=3
Via: SIP/2.0/TCP 10.5.2.50:15060;rport=30522;ibmsid=local.1372169047609_2400498_2400522;branch=z9hG4bK138498682095974
CSeq: 1 ACK
Max-Forwards: 66
Content-Length: 0
Thanks.

This document worked for us between CUCM BE6000 ver 9.0 and the Avaya.
The main focus on the Cisco side is this: Page 37 - 41
5.4. Define SIP Trunk Security Profile
Expand System  Security Profile and select SIP Trunk Security Profile. Click to
configure a SIP Trunk Security Profile.
Enter the following values and use defaults for remaining fields:
 Name Enter name
 Description Enter a brief description
 Incoming Transport Type Verify “TCP+UDP” is selected
 Outgoing Transport Type Verify “TCP” is selected
 Accept Out-of-Dialog REFER Enter
 Accept Unsolicited Notification Enter
 Accept Replaces Header Enter
Click . The screen below shows SIP Trunk Security Profile for the sample configuration
5.5. Define SIP Profile
Expand Device  Device Settings and select SIP Profile. Click to configure a SIP
Profile.
Under SIP Profile Information section, enter the following values and use defaults for
remaining fields:
 Name Enter name
 Description Enter a brief description
 Default MTP Telephony Event Payload Type Enter “120”
 Disable Early Media on 180 Enter
Note: Disabling Early Media allows local ringback to be used.
Under Parameters used in Phone section, scroll to end of section and enter the following values
and use defaults for remaining fields:
 RFC 2543 Hold Enter
Click . The screen below shows SIP Profile for the sample configuration.

Cisco 9951 and cucme registration problem

Hi Everybody
I am trying to register a cisco 9951 phone to a cucme. The phone was previosly connected and registered to a cucm 9.1, now it must be registered in the cucme. The problem is that the status messages of the phone show that the phone has 9.3(2) firmware version and the cucme has 9.2(1) sip9951.9-2-2SR1-9.loads. It means that the phone has a higher version than the version in the router flash (cucme).
I tryed tod download a newer cucme file-set but the last version available in cisco.com is the 10.0 and it has the sip9951.9-2-2SR1-9.loads file which is still older than the version in the phone. So the phone doesnt register.
I follow step by step the instructions to configure and register ip sip phones to cucme. but I am stock.
here is the configuration:voice register global
mode cme
source-address X.X.6.54 port 5060
max-dn 10
max-pool 5
load 9951 sip9951.9-2-2SR1-9
timezone 42
tftp-path flash:
create profile sync 0001184550824421
camera
video
voice register dn 1
number 4002
name SIPPhone 2
voice register pool 1
id mac 501C.BFFC.DD85
type 9951
number 1 dn 1
username nico password 12345
description +571344002
camera
video
tftp-server flash:Phones/9951/dkern9951.100609R2-9-2-2SR1-9.sebn alias dkern9951.100609R2-9-2-2SR1-9.sebn
tftp-server flash:Phones/9951/kern9951.9-2-2SR1-9.sebn alias kern9951.9-2-2SR1-9.sebn
tftp-server flash:Phones/9951/rootfs9951.9-2-2SR1-9.sebn alias rootfs9951.9-2-2SR1-9.sebn
tftp-server flash:Phones/9951/sboot9951.031610R1-9-2-2SR1-9.sebn alias sboot9951.031610R1-9-2-2SR1-9.sebn
tftp-server flash:Phones/9951/sip9951.9-2-2SR1-9.loads alias sip9951.9-2-2SR1-9.loads
tftp-server flash:Phones/9951/skern9951.022809R2-9-2-2SR1-9.sebn alias skern9951.022809R2-9-2-2SR1-9.sebn
the status mesages on the phone say:
Upgrade rejected: HW compat failure. Must use 9.3(2) or later release on this phone
Error updating locale
It still shows:
File not found United_States/g4tones.xml
File not found SIP_English_United_States/ik-sip.jar
Those files tha the phone doesnt find are in the cucm 9.1. I tryed to put them in the flash and configured the tftp-server command and I also downloaded the 9.3(2) from the cucm and copied to the router flash, but it still has registrations problems.
I also tryed to reset the phone to the factory defaults but this sequence with # key and 123456789*0# doesnt aply to sip phones and the procedure of the following link still doesnt work:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/9971_9951_8961/10_0/english/adminguide/P567_BK_A27DADFD_00_adminguide-8961-9951-9971-10_0/P567_BK_A27DADFD_00_adminguide-8961-9951-9971-10_0_chapter_010100.html
Please help me with this issue.
Best regards

Hi Sayeed,
Can you please send accross SIP messages when phone is trying to register with CME ?
Thanks
Manish

MeetingPlace 5.3 and CUCM 7.1

Hi
What choice I have for upgrade of the CUCM to version 7.1 and remain the MeetingPlace in versión 5.3?
TIA
Cristian Munoz

I already did the CUE reload several times. In fact i restore the CUE to factory default and still the problem. I have to clear that the CUE and The CUCM are remote connected through a WAN, but the pings betwen both are responding.
se-10-10-113-253# ping 10.10.9.160
PING 10.10.9.160 (10.10.9.160) 56(84) bytes of data.
64 bytes from 10.10.9.160: icmp_seq=1 ttl=61 time=41.4 ms
64 bytes from 10.10.9.160: icmp_seq=2 ttl=61 time=30.8 ms
64 bytes from 10.10.9.160: icmp_seq=3 ttl=61 time=43.4 ms
64 bytes from 10.10.9.160: icmp_seq=4 ttl=61 time=70.1 ms
64 bytes from 10.10.9.160: icmp_seq=5 ttl=61 time=31.7 ms
--- 10.10.9.160 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 164ms
rtt min/avg/max/mdev = 30.886/43.534/70.192/14.249 ms, pipe 2, ipg/ewma 41.095/42.661 ms

CUCM 10.5(1) and Unity Connection 9.1(2) compatibility

I'm planning to use PCD to migrate my MCS Call Manager 8.0(3) cluster to 10.5(1) early next week. I have a standalone 9.1(2) Unity Connection server and I'm reading conflicting information on Cisco's website about their compatibility. One page says they are compatible (http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/cucsccpmtx.html#46452) and another page says I have to upgrade Unity Connection to at least 10.0 (http://tools.cisco.com/ITDIT/vtgsca/VTGServlet). Can someone clarify this for me please?
If Unity Connection 9.1(2) is incompatible with CUCM 10.5(1) and I need to upgrade it, which procedure should I do first - or if they can safely be done at the same time. If I do Call Manager first, will Unity Connection be "dead in the water" until I get it upgraded?
Thanks in advance!
Lisa

That's very good news. Thank you very much, Jaime, for your speedy reply. You are truly an asset to this community!
If I do upgrade CUC at the same time and both CUCM (pub and sub) and CUC (standalone) are at 10.5(1), where would you host PLM? Right now I have ELM co-located on my CUC server. Our voice environment is reasonably small - less than 400 voice mail accounts and roughly 450 phones.
Also, can I upgrade CUC at the same time PCD is migrating my CUCM cluster or should this be done at a different time?
Thank you again!
Lisa

ELM 9.1 and CUCM 9.1 Registration Conflict

Hi,
Have a standalone ELM server and a CUCM 9.1.1a cluster registering to it that has been working fine for a few months.
A few days ago the CPU was pegging on the ELM server (hostagt process) and I could not restart that process individually, and I did a graceful restart of the ELM server (utils system restart) and it came back up and everything was fine.
Now a few days later, I get alert from CUCM that the ELM sync has not worked for past 7 days and there are 53 days remaining.
On the ELM server, under Product Instancxes the CUCM has a Registration Conflict error and says it is managed by another ELM server. There is only one ELM server. The CUCM license page says it is managed by this ELM server that is complaining.
I've restarrted the ELM server with no change, and I tried to restart the ELM Client on the CUCM server without change.
Do I need to delete the CUCM product instance from the ELM server and add it back?
Is there something hung up on the CUCM server and I need to restart other services on it? I am not seeing much in the logs on either server.
Both ELM and CUCM are version 9.1.1a.
Thanks

Hi there,
Could be this perhaps;
Symptom: Product Instance registration fails with an error that the product instance is already managed by ELM.
Resolution: Log into the CLI of the product you are trying to add, and run the command license client reset registration which will clear its previous register with ELM.
From;
https://supportforums.cisco.com/docs/DOC-34910
Cheers!
Rob
"Why do the best things always disappear "
- The Band

7841 and Directories

I have a customer that has 7841 phones and is running CUCM 10.5.1
They have a TAC case open as 633570203 on the issue of accessing the Corporate Directories.
Having access to the Corporate Directory would seem to me to be one of the basic apps that we are all using with these phones and from the Customer's point of view, they have been less than satisfied with TAC's response.
Is this a known bug and when will it be resolved?
There are other issues that they are having with this phone

Hi Richard,
Perhaps they are hitting this bug;
7821/41 "host not found" intermittently accessing Corporate Directory
CSCuq12291
Symptom:
- 7821 and 7841 sometimes fails to get the corporate directory giving eventually host not found.
-This happens randomly.
- After resetting the phone solves the issue.
- Phone Firmware Used sip78xx.10-1-1-9 and sip78xx.10-1-1SR1-4.
- Affected phones are connected over LAN and WAN.
Last Modified:
Mar 11,2015
Status:
Fixed
Severity:
3 Moderate
Product:
Cisco IP Phone 7800 Series
Support Cases:
16
Cheers!
Rob
Known Affected Releases:
(2)
10.1(1)
10.1(1)SR1
Known Fixed Releases:
(1)
10.2(1.12)

7821 and 8831 CUCM 8.6

Similar Messages

Maybe you are looking for