12-31-2015 02:21 PM - edited 03-18-2019 05:22 AM
Hello Experts ;
I am unable to dial ip address by use * instead of dot by touh pad . Please advice
172*16*50*40 unable to dial every time it changes to this format172.16.50.40...
KV
12-31-2015 02:37 PM
172.16.50.40 is the correct format when dialling IP addresses so when it changes * to . then this is normal, and correct, behaviour as 172*16*50*40 would not get you anywhere at all.
/jens
Please rate replies and mark question(s) as "answered" if applicable.
01-01-2016 02:54 AM
Thanks ;
Actually we have route pattern !*!*!*! in Callmanager in order to reach to expressways. What is the best practice route pattern for dialing IP from SX 80 ? What i know Callmanager does not suport IP address ..
Appreciate your support
01-01-2016 03:41 AM
Take a look on this link:
regards,
Acevirgil
01-02-2016 06:53 AM
Thanks ; Any other options except those ? ..
01-02-2016 09:41 AM
If you want to dial IP Addresses from endpoints registered to CUCM, you must use the configuration example Acevirgil linked to in his reply. CUCM only accepts DNs or SIP URI dialing, it format understand anything outside of that such as IP Addresses, which is why you need to use the method outlined in that example.
01-03-2016 12:32 PM
Thanks but how to restricts sx80 to dial * instead of . cause we have route pattern of !*!*!*! ..
01-03-2016 09:03 PM
You should use Option 1 noted in that example and append a domain to the dialed address, then strip the domain off at the VCS/Expressway. As Jens has mentioned the guide is misleading when it comes to Option 2 which doesn't actually work as how the endpoints will automatically translate the asterisks to periods.
01-03-2016 09:13 PM
You can't change the behavior of the endpoint. Can you add another pattern that matches something other than the asterisk as the separator?
Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
Please remember to mark helpful responses and to set your question as answered if appropriate.
01-02-2016 04:21 PM
Heh - that document shows, IMO, a disconnect between the CUCM development team and the end-point development team as it states:
"Option 2"
"Replace the dots with a symbol in order to turn the IP address into a string.
For example, to dial the IP address 198.51.100.2, users will dial 198*51*100*2."
And yet, the end-point development team includes a functionality in the end-point which automatically changes 198*51*100*2 to 198.51.100.2 when dialling IP addresses, which is, unless I've missed something, exactly what kingvoice is experiencing.
Seeing all the different issues CUCM users have to deal with makes me rather happy we never went for this solution - and I'm very pleased to say we will commence deployment of Pexip this Jan/Feb with the intention of eventually moving away from all Cisco infrastructure devices. :)
/jens
Please rate replies and mark question(s) as "answered" if applicable.
06-03-2020 08:23 AM
12-31-2015 03:03 PM
When dialing IP Adresses, using an asterisk (*) in the place of a period(.) is a short easy method to enter the address as the codec will automatically change the asterisks to periods when it recognizes you're trying to input an IP address. Once you enter the third asterisk, followed by a number, it will change them all to periods as long as what you're entering is in the format of an IP Address.
06-03-2020 08:50 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide