Several of my customers wants to provide the ability to include PIN in SIP URI to facilitate the connection to meeting from video endpoint. There are various scenarios where this feature will be helpful.
The format would be: xxxxx@domain,,PIN# (e.g.: 7777@myCompanySIPdomain.com,,1234#)
IP Phones and Jabber clients support such patterns and I am not sure why endpoint such as SX20, Room 55 device, etc... don't. When trying to do so with device registered on CCM or VCS, it looks like the device tries to resolve "myCompanySIPdomain.com,,1234#" using a DNS request and fails for obvious reasons.
Can anyone from Cisco clarify why it is not supported and if it will soon be?
The issue is there is no agreed standard on how this should be done between manufacturers or systems, so it will largely depend on what it is you are dialling in to to support some kind of format. Adding something to the end of a SIP URI means it's no longer a valid SIP URI, which is why it fails when you dial it from one of the systems you mentioned.
One example that I have seen used by one of the Internet VC providers that maintains the SIP URI format is [Meeting ID].[Password].[Layout].[Host Key]@[IP Address or Domain]. This could be 1234.7777@myCompanySIPdomain.com in your example, but that dial format is specific to their infrastructure.
Wayne -- Please remember to rate responses and to mark your question as answered if appropriate.
Well I would appreciate if Cisco would share how how to achieve the intended call without customising the SIP was it will require further treatment on the side of the call processing unit. My customers use very standard Cisco UC infrastructure with CUCM and SX20. Again, it is possible to from Jabber, a phone, the voicemail or Webex. To me delivering the same functionality should be the natural way to go.
Have you tried using proximity to connect the VC system to the Webex meeting? That way you should not need to reformat the SIP uri as it’s the proximity client, Webex Meeting Desktop app on Windows or Webex app on a smartphone or Jabber or Webex Teams or the stand-alone Cisco Proximity application that instructs how to connect to the meeting.
When an Ad hoc conference is triggered by an endpoint to escalate a point-to-point call into a three-way call.HQ-CUCM sends an API request via HTTPS to the Cisco Meeting Server to set up a conference. You can see from the event log of CMS that API us...
You want in some scenarios different URIs or call-IDs and different access code are used by guest and host participants to join a meeting, and different rights or privileges, for example add or remove participants, mute audio or video, or when there...
Opus is an adaptive codec that provides better audio call quality than G.711/G.729 voice codecs and in a low bandwidth environment. The codec has a very low algorithm delay and is it is highly scalable in terms of audio bandwidth, bitrate, and comple...
Background:When deploying a multisite with centralized call processing across multiple countries, the digit manipulation can be complex, in this scenario US Site as HQ, GE Site in Germany and AU Site in Australia use different dial plan.We need to unified...
Version 3.3 introduces the ability to schedule meetings and see upcoming meetings in web app. Web app users can schedule meetings, modify the scheduled meetings, and notify participants via email. Scheduler is a new component that enables scheduling meeti...