[cisco-voip] Jabber for Windows 10.5 and LDAP searches not in E.164 format (Application Dial Rules)

[NateCCIE .]

I would do both.  Correct the source, but make it work if they miss one.

On Wed, Nov 5, 2014 at 1:54 PM, Jason Aarons (AM) <
jason.aarons at dimensiondata.com> wrote:

>  Customer mostly uses E.164 in CUCM 10.5.
>
>
>
> They added Jabber for Windows and some entries in LDAP like mobile phone
> are just area code-phone number without the E.164. They can’t click to call
> these numbers as it doesn’t match a route pattern.
>
>
>
> I’m thinking that I could configure an Application Dial Rule with 10
> digits that Prefix with pattern +1.   So if a search for user via LDAP with
> mobile number 904-444-5555 is found and they dial it changes to
> +1-904-444-5555 and goes out.
>
>
>
> Or would it be best to go into Active Directory and store items like
> Mobile Numbers as E.164?
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141105/1aa2f014/attachment.html>