CUCM HW conference failing despite being registered

When Video Endpoint attempts to ‘adhoc’ a third endpoint into a conference they loose Video. Having a look at the HW resources they were definitely configured and also showing registered to CUCM. Upon investigating the logs there seems to be a authentication issue when the resource is invoked.

<methodResponse>
<fault>
<value><struct>
<member>
<name>faultString</name>
<value><string>Authentication failure</string></value>
</member>
<member>
<name>faultCode</name>
<value><int>14</int></value>
</member>
</struct></value>
</fault>
</methodResponse>
00751162.000 |12:35:43.071 |SdlSig |HttpHandlerRes |restart0 |SipMcuControl(1,100,36,2) |HttpHandler(1,100,39,2) |1,100,39,2.583^*^* |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] CI=100 Branch= 0 Pkid= Type=0 ResponseCode=0
00751162.001 |12:35:43.071 |AppInfo |SipMcuControl::checkForSuccess- 14
00751162.002 |12:35:43.071 |AppInfo |SipMcuControl::checkForSuccess- Authentication failure
00751162.003 |12:35:43.071 |AppInfo |SipMcuControl::restart0_HttpHandlerRes- found Query transaction for Id 100

This is odd. The Media resource is registered to the CUCM so one can be forgiven for assuming there is no issue with the conference resource. I entered the wrong credentials completely to be sure and reset the CFB and it still registered. Entered the right credentials, made a call and it was successful,

Looks like a bug on CUCM 11.5.1.

Advertisements

Cisco CMS remote error

when TLS encryption was enabled on a trunk from Cisco CMS, all of a sudden calls in from Lync/SkypeforBusiness started failing, here is the output from CMS:-

call 48: recognised as Lync
call 48: incoming encrypted SIP call from “sip:julie.microsoft@XYZ.com” to local URI “sip:1004@vc.XYZ.com” (Lync)
forwarding call to ‘sip:1004@vc.XYZ.com’ to ‘1004@vc.XYZ.com’
call 49: outgoing SIP call to “1004@vc.XYZ.com”
call 49: setting up UDT RTP session for DTLS (combined media and control)
call 49: ending; remote SIP teardown with reason 14 (remote error) – not connected after 0:00
call 48: ending; local teardown – not connected after 0:00

this does not give us much information to work from, so you need to dig deeper. You can either pull logs from CMS via logs > detailed tracing and download via SFTP or get CallManager RTMT logs downloaded to see what the problem is

SIP/2.0 401 Unauthorized
Via: SIP/2.0/TLS 192.168.0.180:5061;branch=z9hG4bK5d3181dbb905b9058
From: “Julie Microsoft” <sip:julie.microsoft@XYZ.com>;tag=e876910435d
To: <sip:dx80@vc.XYZ.com>;tag=2106778089
Date: Thu, 02 Nov 2017 12:49:31 GMT
Call-ID: e62d36f7-5d84-47a1-8ba4-1f3f3433g6a2
CSeq: 183141193 INVITE
Allow-Events: presence
Server: Cisco-CUCM11.5
WWW-Authenticate: Digest realm=”XYZCluster”, nonce=”L1CKj9PJ6qreX9PRZUMm”, algorithm=MD5
Content-Length: 0

401 Unauthorized, well that tells you it is not authenticated to make that call. The SIP Trunk Security profile which had Enable Digest Authentication ticked was not meant to be there.

 

Error when Adding CMS License

When uploading the the Cisco Meeting server License to the platform as you get it from Cisco you get the following error:simple solution to this is to rename the license file to cms.lic and you are now able to upload to the file to CMS without any errors

you can check the license in CMS with the following command

acano> license
Feature: callbridge status: Activated expiry: 2017-May-18 (89 days remain)
Feature: turn status: Activated expiry: 2017-May-18 (89 days remain)
Feature: webbridge status: Activated expiry: 2017-May-18 (89 days remain)
Feature: branding status: Activated expiry: 2017-May-18 (89 days remain)
Feature: recording status: Activated expiry: 2017-May-18 (89 days remain)
Feature: personal status: Activated expiry: 2017-May-18 (89 days remain)
Feature: shared status: Activated expiry: 2017-May-18 (89 days remain)

 

 

 

 

 

 

 

Death to the phones of old

As of CUCM version 11.5 Cisco has finally removed support for the legacy phones, now when i say Legacy i mean really old phones.. i understand why theyve removed its support and have always been impressed on why they have had these in for so long. They make some really tough phones, I remember visiting a customer site with a really intense call center and phone usage. they had 7940’s IP phones whose key pad was completely worn out but the phones were just slogging away.the customer saw no need to replace the perfectly functioning IP Phones. I dont think this customer will be upset that Cisco has made this announcement because they are not affected

… but i will surely be 😦 i have a 12SP phone, one of the first IP Phones from the Selsius days that i managed to get from a friend @ cisco. i still use it from time to time but looks like i will be adding it to my museum with great regret .. if i decide to upgrade 😀

CX42n3EW8AAqBLn.jpg large

enough with the reminiscing, here are the affected IP phones:-

  • Cisco IP Phone 12 S
  • Cisco IP Phone 12 SP
  • Cisco IP Phone 12 SP+
  • Cisco IP Phone 30 SP+
  • Cisco IP Phone 30 VIP
  • Cisco Unified IP Phone 7902G
  • Cisco Unified IP Phone 7905G
  • Cisco Unified IP Phone 7910
  • Cisco Unified IP Phone 7910G
  • Cisco Unified IP Phone 7910+SW
  • Cisco Unified IP Phone 7910G+SW
  • Cisco Unified IP Phone 7912G
  • Cisco Unified Wireless IP Phone 7920
  • Cisco Unified IP Conference Station 7935

 

11.5 release notes

 

PLM Password reset issue

i recently had a issue where it was not clear which application user was assigned to be the admin for PLM, this is easily resolvable by typing the following command:

admin:license management list users
App user: ItsMeSilly

now the is what if i have forgotten the password? well the user guide for 10.5 says the command to reset this password is license management change user password

admin:license management change user name password
Expected 0 mandatory and up to 0 non-mandatory parameter(s)
but 1 parameter(s) were found
Executed command unsuccessfully
Error executing command

there is a bug id for this: CSCus29004, basically a typo in the docs with the correct command being:

admin:license management reset user password
The username: ItsMeSilly
New Password: ******
Re-enter Password: ******
The administrator account password was successfully changed.

further info:-

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCus29004

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/plm/10_5_1/userguide/CPLM_BK_U9B156B7_00_user-guide-rel-1052.pdf

Cisco #Spark notes

Cisco Spark is broken down into three component areas

  1. Cisco Spark Platform
  2. Hybrid Services
  3. API’s
spark
1. Cisco Spark Platform

The Cisco Spark platform is comprised of the following core services

a. Message
b. Meeting
c. Call

message
Message allows a participant the to have 1on1 and Team messages in Virtual rooms, it allows Persistent messages with File Sharing, share photos to the rooms which are then accessible on all devices including mobiles, you can search content, people anytime within a inbuilt search function, @mention allows you to create a kind of notification to the intended participant so that when i @yournamehere you get notified someone mentioned you thus allowing you to quickly respond all with Secure E2E encryption

this is a free service that allows you to invite and collaborate with anyone with just an email address, Spark will send a email to the user who if they do not have a Spark account they will then be able to register with the link provided… pretty straight forward and takes <1min to complete..

meet

Meeting  allows you to easily meet with anyone at any time, meetings are initiated from a single click or can be scheduled for a later time. users can connect to these meetings face to face on a HD Voice and Video call. this offering supports upto 25 participants on a call to include Voice, Video & screen sharing, it supports any Spark client sharing and Spark room systems. if additional quantity is required WebEx meetings will need to be scheduled which supports upto 200 participants but only supports a separate Web client, PSTN integration, Video Systems. while there is no clear transition or escalation path from Spark Meeting to WebEx, i suspect this is something the WebEx/Spark teams are looking into and can imagine it to be available soon.

whats pretty cool here is that when WebEx / Spark is integrated into the on-prem environment (through the Calendar Connector), you can automatically create a room by just adding @spark and @webex to the calendar invite.

Spark Room systems…..This allows you use Spark rooms on codecs such as the SX10, such that when you are on a spark call for example you can move the meeting and content to the SX10 and when you wish to leave, you can take the call with you back on the mobile device by dropping the call back on your device

call

Call allows you to deploy phones to users while utilising the cloud infrastructure, it supports the latest generation of Phones, the cisco 7800 and 8800, it offers three types of features:
Basic Telephony

  • PSTN calling+
  • Video Calling
  • Single Number Reach
  • Call Forward
  • Transfer
  • DND
  • Hold/Resume

 

Advanced Features

  • Auto Attendant
  • Hunt Groups
  • Shared Lines
  • Video on Hold
  • deskphone control with Spark
  • Ad hoc Conferencing
  • zero touch meeting

 

Administrative features

  • User Self care portal;
  • customer bulk provisioning
  • customer & partner admin portal
  • external health portal
  • support tab

 

+PSTN service are provided from a 3rd Party provider approved by Cisco, which provide local, national, international, DDI/DID capabilities
The actual deployment of devices is straight forward, its a case of entering code into the phone or hold the QR code infront of Camera, it will then register to the cloud service.

qr

hybrid

2. Hybrid Services
This allows customers to integrate premises application to Cisco Cloud such as Cisco Call Control, Calendar and Directory.

Directory service
– extends the enterprise directory contacts into the cloud for use with both Cisco UC and Spark customers, with this AD integration when a user is deactivated in AD deactivates the cloud service and removes user from all rooms and services,

Calendar Service –
Simple Scheduling – as mentioned earlier you can schedule meetings and add @webex, and/or @spark to the location field in an invite, this does away with the need for plugins. it will add WebEx details and/or create a Spark room for all attendees to get the converation started before the meeting, this way if content is shared and intros completed, come the time for the actual meeting, and you just get the job done and waste less time. If Video rooms are included in the meeting, they are provisioned for One button to push OBTP

Call Service Connect
– connects your phone system to Cisco Spark, this allows Spark to behave like a softphone, it also provides interop between Jabber and Spark. users can use either Jabber, Spark or deskphone to make calls, users can also be reached on any device. this way you are maximising on existing investment on enterprise telephony

Call Service Aware
– Jabber and Desk phone call history is pushed to Spark, so when using in conjunction with Spark, they can be called back easily. this also creates a “Zero touch meeting” which allow you to answer incoming call on any device, once it identifies both parties have spark enabled it allows you to start a room and share content directly on the spark client, this feature also allows quick redial of missed calls from anywhere
Requirements
arch

Office 365 is currently in EFT and should be available in March 2016

api

3. API’s

Visit https://developer.ciscospark.com/

 

Further Information
Spark integrations https://developer.ciscospark.com/integrations.html
Spark Availability https://support.ciscospark.com/customer/portal/articles/1940194-where-is-cisco-spark-available
Zapier https://zapier.com/zapbook/cisco-spark/
IFTTT https://ifttt.com/cisco_spark

Jabber 11.0 shortcuts

we all want something that makes our lives simpler or wer just plain lazy, aside from the basic Windows shortcuts for copy, paste, bold, underline we should all really know?! that can be used for IMs, here are some Jabber 11.0 shortcuts that you can use to do just that when dealing with calls. most of the shortcuts are still applicable @ v9.x

j11acc

for more information, please refer to the Jabber 11.0 end user Guide