Error connecting to a S4B and CMS Dual Homed Call

When attempting to Join a Microsoft Skype meeting the call from a Cisco Endpoint fails, a point to point however does not, looking at the logs it suggests that it cannot find the conference “meet.alictrify.com/joe.microsoft/2h2g6c6r” not found

2018-06-19 12:53:27.669 Info 2000 log messages cleared by “admin”
2018-06-19 12:53:34.558 Info call 16: incoming encrypted SIP call from “sip:dx80@alictrify.com” to local URI “sip:meet.alictrify.com/joe.microsoft/2h2g6c6r@alictrify.com”
2018-06-19 12:53:34.625 Info lync conference resolution: C3p query error
2018-06-19 12:53:34.626 Info lync conference resolution: conference “meet.alictrify.com/joe.microsoft/2h2g6c6r” not found
2018-06-19 12:53:34.626 Info forwarding call to ‘sip:meet.alictrify.com/joe.microsoft/2h2g6c6r@alictrify.com’ to ‘meet.alictrify.com/joe.microsoft/2h2g6c6r@alictrify.com’
2018-06-19 12:53:34.629 Info call 17: outgoing SIP call to “meet.alictrify.com/joe.microsoft/2h2g6c6r@alictrify.com” (Lync)
2018-06-19 12:53:34.652 Info call 17: ending; remote SIP teardown with reason 18 (not found) – not connected after 0:00
2018-06-19 12:53:34.653 Info call 16: ending; local teardown – not connected after 0:00

Since we are attempting to join a Lync Meeting and not a gateway call which would be converted to MS-SIP, CMS needs to convert the user portion of the URI into an HTTPS target and try to find an Office365 meeting hosted at that URL. This is achieved by setting the SimpleJoin to be enabled and set to Yes.

Once configured, the resolution will work and this will now show up as:

2018-06-19 13:23:24.749 Info lync simplejoin resolution: successfully completed
2018-06-19 13:23:24.754 Info call 34: outgoing SIP call to “joe.microsoft@alictrify.com;gruu;opaque=app:conf:focus:id:2h2g6c6r” (Lync focus)
2018-06-19 13:23:24.758 Info call 33: setting up UDT RTP session for DTLS (combined media and control)
2018-06-19 13:23:24.785 Info conference “Lync conference meet.alictrify.com/joe.microsoft/2h2g6c6r”: unencrypted call legs now present
2018-06-19 13:23:24.790 Info call 34: SIP call ringing
2018-06-19 13:23:24.826 Info call 35: outgoing SIP call to “joe.microsoft@alictrify.com;gruu;opaque=app:conf:focus:id:2h2g6c6r” (Lync conference subscription)
2018-06-19 13:23:24.861 Info call 36: outgoing SIP call to “Joe.Microsoft@alictrify.com;gruu;opaque=app:conf:audio-video:id:2H2G6C6R” (Lync)
2018-06-19 13:23:24.862 Info call 37: outgoing SIP call to “Joe.Microsoft@alictrify.com;gruu;opaque=app:conf:chat:id:2H2G6C6R” (Lync IM)

This shows that the Lync Focus which is responsible for enforcing the Conference Control Policy,  Lync Conference Subscription, Audio / Video, Lync IM setup completes successfully for Skype Meeting ID 2h2g6c6r

in CMS you can also see the same channels setup in the active calls:-

Advertisements

OBTP not updating

When attempting to setup a Skype for Business meeting from a client inviting a Cisco DX80 endpoint it was not updating,

having a look at the logs it seems like a Credentials error :

2018-06-19 13:34:19,401 [MeetingSynchronizerThread] INFO – Forcing update for endpoint dx80@alictrify.com.
2018-06-19 13:34:19,401 [MeetingSynchronizerThread] INFO – Sending out OBTP information to endpoint dx80@alictrify.com for meeting ‘dx80@alictrify.com’.
2018-06-19 13:34:19,401 [MeetingSynchronizerThread] INFO – Updating endpoint dx80@alictrify.com with OBTP information; attempt 1
2018-06-19 13:34:23,682 [OBTPThread] INFO – Failed to connect to endpoint on ‘192.168.0.11’, now trying with a different protocol.
2018-06-19 13:34:24,526 [MeetingSynchronizerThread] INFO – Failed to connect to endpoint on ‘192.168.0.11’, now trying with a different protocol.
2018-06-19 13:34:28,510 [OBTPThread] ERROR – ConnectToSystem
System.Exception: The remote server returned an error: (401) Unauthorized.
2018-06-19 13:34:29,354 [MeetingSynchronizerThread] ERROR – ConnectToSystem
System.Exception: The remote server returned an error: (401) Unauthorized.
2018-06-19 13:34:29,526 [OBTPThread] INFO – Updating endpoint dx80@alictrify.com with OBTP information; attempt 2

this is corrected by navigating in SynergyJoin application to Video Systems and adding password to the endpoint in question.

SynergySky: updating calendar with OBTP

In the SynergySky Join Version 2.5 there is a preview feature that allows the calendar invite to be updated after the meeting invite has been sent out, for this to work additional permissions need to b configured in Exchange which allows the meeting organiser to update the meeting after the invite has been sent out otherwise the organiser will receive the following error:

Scenario:
User books meeting inviting Microsoft S4B Client and Cisco Video Endpoint (DX80). Calendar does not get updated as permissions not set in Exchange. Exchange Version used: 2016

The following power shell permissions applied to the Exchange will give users the right permissions needed to perform this action

This will give exchange service account ‘Editor’ access to be able to update the calendar appointment with dial in information:

Add-MailboxFolderPermission -Identity joe.microsoft@alictrify.com:\Calendar -User administrator@alictrify.com -AccessRights Editor

The service account also needs an AD user object permission: ‘sendas’ for each user to send a updated invite to all recipients –

Add-ADPermission “Joe Microsoft” -User alictrify\administrator -Extendedrights “Send As”

< this was previously implicitly included in the Exchange server “Full Mailbox Access” permission or added in Exchange Online as part of the Add-RecipientPermission

Now when you send a invite you will not receive a failure email but rather a update in the calendar as follows:

When the time for the meeting comes you will see OBTP appear on screen:

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.

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

Video

zero touch migration of Cisco IP phones… Free

Yep, for free and for a limited time .. read on.. UnifiedFX has released a pretty cool tool called #MigrationFX for migrating old Cisco Phones to new. if you take into consideration the time taken to plan and swap phones accross this works out to be a very good solution.

the process is as simple as ordering new phones and distributing to users; no need to scan MAC addresses and allocate and configure for user and ship to THAT user. once user/s receive the phone, its as simple as unplugging the handset and using the same cable adding the new device. this then kick starts the auto provisioning process.

to see how this works see the following link

you can try out the product for free for upto 50 phones, by registering with them http://www.unifiedfx.com/migrationfx-lab-edition/.

and i know you are thinking, but you said for FREE.. and yep im coming to that, if your migration includes more than 100 phones, Cisco will throw this product in for free by using the following promo code L-CP-MGFX-PROMO= in the same TMP registration.

more information from Cisco on this promotion: http://refreshcollab.cisco.com/webportal/16/4/17/description