Jabber and Dial Plans?

Hi, so i have Jabber working with my UC540 and my network access points AP541Ns. this is good!
However no doubt there will be many things we find problems with...
One of the big ones is the lack of a dial plan for Jabber with the iPhones contacts. Its needs to automatically add the '0' or whatever you need to add to dial an outside line.
Is there a way i can do this or is this something we need to add to the software?

Hi, ok so does anyone have an update on this???
I just got Jabber working better than ever with the help of cisco support, but the missing zero to dial out is a pain.
Any ideas?
UC540 system with 8.6.1 Software Pack

Similar Messages

Jabber and dial from IE yet?

Does Jabber support direct dialling from IE yet? Trawled through previous discussions and release notes but doesn't look promising. Can I get a quick Yes/No with reference for 5 points please? :)
CUCM 10.5
Jabber 10.6
Cheers
Rich

Hi Jacob,
The second window
is a Cisco Jabber window and is working as designed.
The 1st window you sent
This is not a Cisco window, it is a Microsoft Outlook window.
This would imply that the Cisco Click to X feature is not installed on the affected machine.
Do you have many users with this issue?
Would it be possible to reinstall Jabber on this machine?

Remove and install dial plan installer - the effects on route patterns etc

Hi All,
I am hoping someone could answer this one for me quickly.
I have a scenario during an refresh upgrade to CUCM 10.5(2) where it fails in the install logs with "component_install:807, failed to refresh_upgrade Infrastructure_post components | <LVL::Critical>".
The fix to this may be that I need to uninstall the AUNP dialplan before upgrading.
See (https://supportforums.cisco.com/printpdf/12334191)
What is the effects on route patterns etc when removing the AUNP dial plan?
Will the configuration be maintained and become operable once I upgrade and re-install the AUNP?
Thanks in advance
Kent

Check your database replication status, this might help:
https://supportforums.cisco.com/docs/DOC-13672
HTH,
Chris

CCM 9.1 dial plan with 11 digits Pros and Con

all I came into a new setup where they have the following:
DN: 11 digits (1XXXXXXXXXX) which matches the DID's
all LDAP users has +1 dialing in telephone field
I guest this was mainly used for + dialing
used across 5 locations
Now they want to add site codes (CCC+last4) 7 digits for internal dialing
-- plan on adding 20 more sites.
this would not be so bad if the site had DID's in a con't range. I am hoping this does not turn into a nightmare
plan:
leave the DN at 11 digits
change the display to show CCC+last4
create translation for the site code (CCC)
CCC.XXXX -- predot, prefix 1678507 = 16785075555
has anyone done this type of dial plan before? Pros and Con

Hello!
Please, explain a little bit more "this would not be so bad if the site had DID's in a con't range"..
Can u put some examples may be?
Regards,
Kirill

New Dial plan & Voice policies not taking effect with Polycom CX 600 Desktop Phone in production deployment, Worked fine in Testing

Hi,
We are in the process of Migrating Cisco CUCM & Voice Gateway (From another vendor to Cisco).
The requirement is all internal calls between Cisco IP Phones & Lync to be flown through CUCM. Means internal extension to extension. Remaining all calls like Mobile, National, International, Toll Free, Emergency, Shared numbers calling to be routed
to Cisco Voice Gateway.
We created the test dial plan, Voice policies, Route and assigned it to couple of user from Lync (2 extensions) and from Cisco side we have taken 2 IP Phones which is pointed to new CUCM. We tested all below scenarios,everything was working fine.
Lync to Lync Call using internal Extension number – Routed through Cisco new CUCM
Lync to Cisco Call using internal Extension number – Routed through Cisco new CUCM
Cisco to Lync Call using internal Extension number – Routed through Cisco new CUCM
Lync to Hotline Numbers (66XX, 68XX Numbers) – Routed through Cisco Gateway
Lync to Shared Numbers starting with 600 (Verified the number 600535353) - Routed through Cisco Gateway
Lync to Emergency numbers & Toll Free Numbers (Not verified the emergency Number as we decided to do it at end) - Routed through Cisco Gateway
Lync to Landline Numbers – Any 7 digit numbers - Routed through Cisco Gateway
Lync to National Numbers – Starting with 3,4,6,7,8 followed by 7 digits - Routed through Cisco Gateway
Lync to Mobile Phones – Starting with 05 contains exactly 10 digits - Routed through Cisco Gateway
Lync to International Numbers – Starting 00 contains at least 11 digits - Routed through Cisco Gateway
All Incoming calls – From Landline, Mobiles, International Numbers - Routed through Cisco Gateway
Call Transfer – To another Lync Extension, Cisco Extension, Landline, Mobiles, International Number
Conference – with another Lync Extension, Cisco Extension, Landline, Mobiles, International Number
Call Forwarding – To another Number, Voice mail
Response Groups
Click to call – As if user try to place a call by directly click the number from Outlook, Websites will be in E.164 format
Dial in meeting – Conference calls are works fine
But when we roll out to the production we are facing issues listed below
1) The phones we used during testing are working which is using same dial plan, Voice policy, Route, PSTN Usage. But from production most of the phones are not working (using the same dial plan, voice policy, Route). Also Problem is only with external calls
as the internal calls are working fine between Cisco & Lync even in production (Routed through CUCM) NOTE: All incoming calls are working fine (From international, local, national, extension)
2) How long its going to take for Lync to push the new voice policies, Dial plans to the Phones?
3) Is there a way to forcefully update the policies, dial plans to the Phone?
4) Also the environment is using over 100 dial plans, so I just copied and pasted the Normalization rules that we tested and working fine. Most of the dial plans are assigned to individual users as every dial plan contains a normalization rule for
international calling with Unique Prefix (Example: User John international Normalization rules says #1234#00#CountrycodePhonenumber, means if John has to place the international call he need to dial #1234# followed by 00 and then country code, then actual
phone number). In this case how long its take for the users / phones to get updated with new dial plans?
6) Is it recommended to use multiple dial plans ? What are the best practices?
5) Also calls are working fine one & failing on subsequent tries. Means when I dial first 1 or 2 times. Call fails, but when I try 3rd time and subsequently it works. After some again there will be failure during 1 or 2 attempts. Why is it so?
6) After updating the dial policies, voice Route, Voice policies If i reboot all the phones from Switch, Will the changes take effect immediately?
7) Also when some one calling from mobile or external number to Lync extensions they cant here any Dial tones or caller tunes? Its working fine when they call Cisco Extensions. Also to Lync its working if we dial in E.164 Format, if we dial like 023XXXXX
format its not working. Any guess about this issue?
Waiting for some one to help,
Best regards
Krishna
Thanks & Regards Krishnakumar B

Hi,
1. As all incoming call worked normally, please double check outgoing ports for Lync FE Server and Mediation Server.
You can refer to the link of “Ports and protocols for internal servers in Lync Server 2013” below:
http://technet.microsoft.com/en-us/library/gg398833.aspx
2. When an administrator makes a change to Lync Server (for example, when an administrator creates a new voice policy or changes the Address Book server configuration settings) that change is recorded in the Central Management store.
In turn, the change must then be replicated to all the computers running Lync Server services or server roles.
So it may not replication completely immediately.
3. You can run the following cmdlet with Lync Server Management Shell on FE server to
forcibly replicate information to a computer: Invoke-CsManagementStoreReplication
4. As you used over 100 dial plans, it may be the issue of multiple dial plans. Would you please tell us why you created different dial plan for individual user with unique prefix?
5. Multiple dial plans and undue normalization rules may cause call fail. You can double check the normalization rule.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Best practice to Change Dial plan?

Hi,
Customer has made plenty of misdialed 911 calls so they want to change the dial plan. They have CUCM, CUC and UCCX .. I will try to suggest putting a delay for 3 sec or so and blocking 911! or 911!# translation pattern .. but in case if they do want to change their dial out number.. what's the best practice for this? I tried looking for a suggestion or document but couldn't find it... at this point I can only think of copying existing RP's and change the dial out number to 8 and if required if they will have an H.323 gateway then might require configuration on dial peers... Any suggestion on this is appreciated? Thanks

Hi Vishal,
If 911 is being dialed accidentally, you can try configuring a 9.911 or 911# route pattern. 9.911 will require you to change the destination pattern and forward digit settings on dial-peer or you can actually strip it on cucm itself and will not require a change on dial-peers. Other than that you need to check your dial-plan and see if there are any router patterns that are overlapping with 911 you can try editing them as well by changing the first digit for those route patterns to something other than 9.
HTH
Manish

SPA3000 F/W 3.1.20(GW) last digit repetition within the dial plan is not working for gateway 0-4

H/W: SPA3000
F/W: 3.1.20(GW)
Problem: The last digit repetition within the dial plan is not working for gateway 0-4.
Line 1 Dial Plan: (****|<#,xx.<:@gw1>|1747xxxxxxxx.<:@gw1>)
Dial "17474743246#" which works for gw1.
Dial "#17474743246" which also works for gw1.
Dial "17474743246" which doesn't work and actually goes through VoIP 1 but not gw1.
It results in I have to specify a fixed number of digits for gw0-gw4 in the dial plan or it won't works. This could be very difficult for international calls.
Is there any way to specify Interdigit Short Timer with <:@gw0>?
BTW, it's strange that I have to include (****) in the dial plan to enter IVR. Without it I can't even hear any sound coming from gw1 (SIPphone). Maybe the SPA needs a factory reset. The test dial plan might look like,
S:4,(****|*xxx.|[2-9]|xxxxx|*0<:@gw1>|1747xxxxxxx<:@gw1>|1408xxxxxxx<:@gw0>|xxxxxxxxxxxxxxxxxxxx.!)
The last barring sequence "xxxxxxxxxxxxxxxxxxxx!" is to make sure the Interdigit Short Timer works after the last digit dialed otherwise the number will be transmitted immediately which is not preferred.

IMHO , if there's a need for you to include *** on the dial plan to enter the IVR menu there might be a need to reset the unit.
I believe that you can set the interdigit timer by including that on the dial plan ie: xxxxS0 just like on a hotline, i just never had a chance to try including that syntax when invoking gw0 on the dial plan , but i guess you may give it a try.

Dial plan: Can we change the redirect number (sip-sip)?

Hello Scott Page/Alexei/Dirk Anyone.
I have a question on dial plan:
Call flow: A---cucm----pgw----voicemail
              B-----|
Its a sip to sip call, what i need to do is change the redirect number or rather add a digit to the redirect number at the PGW side.
For instance:
A number: 902228990
B number: 902228996
Redirect number: 92228996 --->Here i want to change it to 902228996
pgw patch: 9.8.2    "Patch:"CSCOgs014/CSCOnn014""
bash-3.00$ uname -a
SunOS tcs-tza1 5.10 Generic_127127-11 sun4u sparc SUNW,Netra-440
I checked from the cisco website but i think its only for isup sip calls only but not sure.
numan-add:fullnumbertrans:svcname="Service Name",numbtype="Number Type", digstring="Original Digits",
translatednum="Translated Digits"
Where numtype can be choose 3 for redirect number.
numtype—Identifier for the number type (1-5), it is one of the following values: 1—called party number 2—calling party number 3—redirecting number 4—calling party number and redirecting number 5—original called number
Can some help me out with the dial plan configuration?.
Regards,
Aby

Guys,
This configuration would work?, please let me know
1. mml> numan-add:service:custgrpid="DP00",name="BATMANredirect"
2. mml> numan-add:fullnumbertrans:svcname="BATMANredirect",digstring="92228996", translatednum="902228996",numtype="3"
numtype=3-->redirect number
3. Adding a result type of NUM_TRANS:
mml>   numan-add:resulttable:custgrpid="DP00",name="results",resulttype="NUM_TRANS", dw1="BATMANredirect",dw2="3",dw3="3",setname="setname3"
dw2--->number type hence i put it 3
dw3--->NOA--->hence i put it as national ie 3,
dw4--->Dialplan?-- can i avoid this?
4. mml> numan-add:resulttable:custgrpid="DP00",name="noar",resulttype="R_NUMBER_TYPE", dw1="4",setname="setname3"
dw1===>NOA again, i put it as dw1="4" as national.
Can any of you help me if this would do the trick or anything else needs to be added?.
Thanks and appreciate your time.
Regards,
Aby

Dial plan change.Internal calls are dialing slow

Hi,
I have made dial plan change in one customer from 3 digits to 2.But there is an IVR with CTI ports with 3 digits and the first digit is overlapping with some 2 digits phones. So when you try to dial for example number 61 the CUCM is waiting for the interdigit timeout because the CTI RP is with number 600.And there are some hunt pilots with 3 digits. So I have decided to move all 3 digits CTIs and hunt pilots to different partition and exclude them from the internal partition, but the problem still exists. So let say I have:
pt_1
css_1 (includes only pt_1)
pt_2
css_2 (includes only pt_2)
Phone 1
DN 10
pt_1
css_1
Phone 2
DN 20
pt_1
css_1
Phone 3
DN 100
pt_2
css_2
Phone 4
DN 200
pt_2
css_2
Why when I call phone 1 from phone 2 the cucm is waiting for the interdigit timeout, but when I call phone 3 from phone 4 no problem?
Thanks for the help.

Hi there,
Is it possible for you to attach your Route Plan report .csv
for us to have a look at. Maybe we can help identify the overlap.
Cheers!
Rob

911 Dial Plan for Specific Users

Hi all, We have a Lync 2013 deployment here.
I am trying to achieve something that I am not sure is even possible with 911 calling.
Out SIP provider is telling us that we MUST send all calls outbound as a specified number (let's use 555-4040 in this example).
What I would like to achieve, is to configure an outbound translation ONLY when a user dials "911". All other calls will go outbound as the user's regular DID number.
Is this even possible with the Lync dial plans/translations?
If not, then it appears we must ALWAYS translate outbound calls as "555-4040" no matter what number the user dials.
Thanks!

Yes, you can do it. You have to create a new voice route for 911 calls only. When you create a route, there is an option to "Suppress caller ID". This is the place where you enter the caller ID that you want to have.
Another way to do it directly on your IP gateway. I have done it before on AudioCodes and on Dialogic gateways. You create a new manipulation rule and specify that if dialed number is 911, replace the caller's number.
Please “Vote As Helpful” and/or “Mark As Answer” if this post helped you.

How does a single cisco router network enable outgoing calls for small businesses if no dial plan is used

Hi Cisco techs,
I was recently asked this question at work from the rest of my team as they know I am doing studies for cisco ICND 1 & 2.
And couldn't answer them.
Or does this require more information like hardware used etc?
Had searched Google to ambiguous results.
Can someone give me a link to advise please
Thanks in advance again..

Dear,
For small business (up to max 450 users) we use Call Manager Express (CME) which is configured on Cisco Voice router.
If no dial plan is used or configured then none of callmanager can do external outgoing/internal calls. Dial plan is basic thing which must be configured on cisco voice router (e.g. CME).
If you have configured Phones (ephone & ephone dn) and if they are registered on callmanager express then for internal calls you dont need to configure dial plan because callmnager have all the information of its phones.
If you want to have external incoming/outgoing calls for CME then you will have to create dial peers/dial plan.
For a CME lab setup, you can visit below link.
http://cisco.jjc.edu/cnt208/PDF/CCNP4_lab_2_1_en.pdf
Suresh

Analogue devices not using assigned dial plan

Hi,
We are using Tenor gateways for running analogue devices (fax, cordless phones) through Lync 2013. It works fine on our standard dial plan which all end-users are on. However, for a business reason, we need to do restricted dialing on the cordless phones
(e.g. dial a 5 digit access code to dial out).
The cordless phones exist in AD (created using new-csanalogdevice in the Lync Mgmt Shell) and I'm using the following command to assign the dial plan:
get-csanalogdevice "My test phone" | grant-csdialplan -policyname "restrictedCallDialPlan(77777)" -v
When I run get-csanalogdevice "My test phone" | Select DialPlan I can see I am using the restricted dialling dial plan but the calls are not restricted - e.g. I can call my mobile phone as normal with out having to preceed the number with
77777.
First thought was there was a configuration an issue with the dial plan. Checking it in the Lync Ctrl Panel it all looks fine, and it more importantly, it works as expected on Common Area Phones (Polycom CX500).
If I have to, I can do the restriction on the Tenor gateways but it's not a "nice" solution as the config gets messy. Ideally we'd like to do it in Lync so we can manage it all from one place.
Is anyone familiar with assigning dial plans to analogue extensions in Lync and know of a reason this wouldn't work?
Many thanks

Hello,
I experienced the same behaviour utilising analogue devices within Lync, during my research it appeared that while you can set a dial plan against an analogue device, this will never take affect and
will only inherit normalisation rules defined in the Global dial plan. Please see the following article below under the "Call Routing For Analogue Devices" section, around half way down this section it explains in details the grant-csdialplan behaviour
for an analogue device. In my case, I utilised a feature on the AudioCodes MediaPack devices which we were using for analogue connectivity in order to restrict dialling on a per port basis.
http://www.mylynclab.com/2013/04/microsoft-lync-facts-about-fax.html
Regards.
http://www.b4z.co.uk

Exchange UM is always using the Global Lync Dial plan for calls.

Our multi-tenant exchange UM will have auto-attendants that will do response groups. For example an auto-attenant option may be "technical support" which will ring a technical support queue. We have found that when exchange places the call to the
workflow extension (example 123)) formatted as +11231231234;ext=123 in the workflow that Lync follows the Global dial plan only. This fails because the user dial-plan is what translates the 3 digit extension back to the full E164 format. We have not found
a way to tell the exchange UM which Lync dial-plan to use, and we cannot figure a way to use the exchange dial-plan to format in a proper E164 (number/extension) format.
We worked around the issue now by using a non-important number sequence for an extension in the exchange auto-attenant, then hard-coding each extension sequence in the Lync global dial-plan to translate it one-to-one for whatever DID;ext combo it should
map to. This cannot be the best way to do this, however.
What are your thoughts with calls from exchange to Lync on how a dialplan should be specified?

Well, this is a very interesting article. This is really not the answer to my question, but it does open a side discussion. I have absolutely no problem using a key mapping and dial extension in my Exchange UM AA. Reading this article made me re-test my
AA. I can dial an extension and I can dial a key mapping. I also can say an extension and I can say a key mapping option. I dialed in to test all 4 scenarios and they are working fine. I really should contact Matt on this to find out what scenario made him
write that blog post.
On a different topic, that is not the issue here. My question is after a key-mapping is accepted (and it is) the call is transferred to that extension in Lync. The extension maps to a response group. The response group format is in E164 with the ext= at
the end. The Dial Plan (in Lync) that is used is always Global to translate that extension. In an Enterprise environment, this is most likely not an issue. But, in a hosted environment we cannot rely on anything Global. The dial plan that should be processed
is the user dialplan.
As I mentioned, I do have this working, but I am stretching the use of the global dialplan to translate a fake extension back into the user dial-plan E164 format. For example:
Exchange UM AA has option '2' for the Help Desk. I have exchange dial extension 000.
In Lync's global dial plan I have a match for extension 000 which translates to +16786660121;ext=296
+16786660121;ext=296 then matches the response group needed for option 2.
Now, if Exchange read the user dial plan that the exchange UM should belong to (paired?) then the global dialplan and the fake 000 extension would not be needed, I could simply just dial 296 and let the user dial plan do the 3 digit to E164 translation it
is already programmed to do.

Extension is already assigned to another user on a dial plan.

I am unable to UM enable a user with a specific extension. I get the error that the extension is already assinged to another user. I cannot locate the number in the directory.
I have exported with Get-UMMailbox.. the extension is not in the export.
ldap query for msRTCSIP-Line gives no results.
ldap query for Telephone Number no results.
Lync ctrl panel search does not return any results.
Any advice is appreciated.
l1b3r4l

I figured out my issue. This may be similar for others.
Scenario: I attempted to UM enable a Lync user that I assigned an "available" number. When I UM enabled I was presented with an error stating that the extension was already assigned to a user in the dial plan.
I did custom ldap searches for msRTCSIP-Line=tel:+1xxxxxx1234 - No results with this search.
I searched via the Lync ctrl panel filters for this number. - No results returned.
I attempted the proxyaddress=smtp: search via custom ldap search in ADUC. - No results.
What happened was a user was assigned Enterprise voice andded to a dial plan, then was moved over to the Aura system. WHen this happened the number was given back to the pool, the user was set as PC>PC only. This user did not have UM disabled
when removed from Lync Enterprise voice.
I was able to locate the user using the following commmands. I found the user disabled UM, then was able to provision the new user without issue.
The command to do so is as follolws: (plus bonus commands for your enjoyment)
get-ummailbox | ForEach { If($_.Extensions -eq 4322){$.DisplayName}}
get-ummailbox | where { $_.Extensions -eq "45873" }
Get-UMDialplan -Identity "DefaultDialPlan" | Format-List
Hope this helps someone!
Enjoy
l1b3r4l

Auto attendant intermittently routes call to out of region/not in dial plan UM server

Hi all,
Exchange 2013 on prem, hardware not virtual. CU5 w/Lync 2013
I've got calls that get intermittently routed to UM servers that are out of region and not in the dial plan. The out of region UM server sees the call is outside of business hours & sends helpdesk calls to voicemail instead of the appropriate phone
menu.
Additionally, when Exchange admins who are in different time zones look at the GUI w/the AA's business hours they see a time skew even though the time displayed is listed as Eastern. I think the mis-routing & the time zone skew are related. When
the Tokyo server gets the call it checks the time: 3AM? Not in business hours even though in Eastern Time where the call is supposed to go, it is in business hours.
In the Lync client log (as seen via the snooper tool) this is the last message before the call gets transferred:
“ms-diagnostics:
15032;reason="Re-directing request to the destination in 302”
Additionally the time zone on the AA schedule is set to Eastern Time. Why is the TYO UM server ignoring this and applying local time?
Any tips to point me in the right direction would be appreciated.
Adam

Number two was correct! The affected site did not have an arbitration mailbox. Details follow.
I still have the underlying problem of AA's getting the time zone of the UM server applied rather than the time zone they are allegedly set to (for example Beijing business hours served from a TYO UM server getting TYO time).
With the help of MS support we resolved the immediate problem: calls getting routed to our TYO site.
It turns out that every AD site with Exchange servers needs to have an arbitration mailbox with the grammar generator role set & ready. If a site with UM servers does not have an arbitration mailbox it will proxy the call to another site that does.
In our case, it would route them to our Tokyo site that applied the wrong hours to the auto attendant.
Here's how we created the arbitration mailbox
[PS] C:\temp\autoattendant>New-Mailbox -Arbitration -Name "A new UM Grammar Mailbox" -Database <some db hosted in site> -UserPrincip
alName [email protected] -DisplayName "A new UM Grammar Mailbox"
C:\temp\autoattendant>Set-Mailbox [email protected] -Arbitration -UMGrammar:$true
This keeps the call from going out of site to an Exchange UM server in a different time zone.
The tricky bit is that this does not immediately work. The mailbox needs to pick up the OrganizationCapabilityUMGrammarReady capability which it will only get when the grammar generator runs. In 2010 you were able to kick this off manually. In
2013 it runs once a day. You have to wait until Get-Mailbox -Arbitration | fl name, servername, persistedcapabilities shows the OrganizationCapabilityUMGrammarReady has been assigned to the mailbox.
I still have not yet resolved the underlying problem of why UM servers are ignoring the time zone setting on AA's business hours.

Jabber and Dial Plans?

Similar Messages

Maybe you are looking for