[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cisco-voip
Subject:    Re: [cisco-voip] Webex Proximity Callback to Video Endpoints with CUCM
From:       Anthony Holloway <avholloway+cisco-voip () gmail ! com>
Date:       2019-10-21 21:44:48
Message-ID: CACRCJOgjZZ+i=QYdsw0jwXc1eQgBsPEQr7Cf+LAD3nVGTsozKg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I +1'd it for ya B-Rye.  ;)

On Mon, Oct 21, 2019 at 1:01 PM Brian Meade <bmeade90@vt.edu> wrote:

> Hey everyone,
>
> With Webex Meetings video callback to a CUCM-registered video endpoint via
> proximity, Webex always tries the DN@domain.com format rather than the
> Primary URI configured.
>
> We've confirmed that the video endpoints advertise the DN@domain.com as
> well as the Primary URI but Webex Meetings is setup to prefer
> DN@domain.com.
>
> In our organization and many customer organizations, the B2B Expressways
> do not allow DN@domain.com calling.
>
> This issue has become much worse with the new Webex join experience
> launched recently.
>
> At ePlus, my coworker opened a Collaboration Idea for resolving this-
> https://ciscocollaboration.ideas.aha.io/ideas/COLLAB-I-3255
>
> Webex BU is using this to prioritize fixes and new features.
>
> Can you vote for this issue if it is applicable to yourself or a customer
> of yours?  We're really hoping to drive some visibility of this issue.
>
> Thanks,
> Brian Meade
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[Attachment #5 (text/html)]

<div dir="ltr">I  +1&#39;d it for ya B-Rye.   ;)</div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 21, 2019 at 1:01 PM \
Brian Meade &lt;<a href="mailto:bmeade90@vt.edu">bmeade90@vt.edu</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hey \
everyone,<div><br></div><div>With Webex Meetings video callback to a CUCM-registered \
video endpoint via proximity, Webex always tries the <a href="mailto:DN@domain.com" \
target="_blank">DN@domain.com</a> format rather than the Primary URI \
configured.</div><div><br></div><div>We&#39;ve confirmed that the video endpoints \
advertise the <a href="mailto:DN@domain.com" target="_blank">DN@domain.com</a> as \
well as the Primary URI but Webex Meetings is setup to prefer <a \
href="mailto:DN@domain.com" \
target="_blank">DN@domain.com</a>.</div><div><br></div><div>In our organization and \
many customer organizations, the B2B Expressways do not allow <a \
href="mailto:DN@domain.com" target="_blank">DN@domain.com</a> \
calling.</div><div><br></div><div>This issue has become much worse with the new Webex \
join experience launched recently.</div><div><br></div><div>At ePlus, my coworker \
opened a Collaboration Idea for resolving this-  <a \
href="https://ciscocollaboration.ideas.aha.io/ideas/COLLAB-I-3255" \
target="_blank">https://ciscocollaboration.ideas.aha.io/ideas/COLLAB-I-3255</a></div><div><br></div><div>Webex \
BU is using this to prioritize fixes and new features.</div><div><br></div><div>Can \
you vote for this issue if it is applicable to yourself or a customer of yours?   \
We&#39;re really hoping to drive some visibility of this \
issue.</div><div><br></div><div>Thanks,</div><div>Brian Meade</div></div> \
_______________________________________________<br> cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" \
target="_blank">cisco-voip@puck.nether.net</a><br> <a \
href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" \
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br> \
</blockquote></div>



_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


[prev in list] [next in list] [prev in thread] [next in thread]