In CUCM if we add update UDP’s or devices with Extension Mobility IP Phone Services subscribed, the import process appends another IP Phone Service, so you could end up with multiple IP Phones Services subscribed. Hence when the phone user press the Services button on the IP Phone, the menu displays more than one instance of the IP Phone Service, in this case Extension Mobility.
One way to prevent the IP Phones Services from being duplicated or appended to the Device or UDP is to make sure the import process deletes all IP Phones Services before adding the IP Phone Service from your CSV or TXT file.
Under Override Options check the box “Override the existing configuration”
Then check the box Delete all existing Subscribed Services before adding new ones”
If you already have duplicate IP Phone Services subscribed to Devices to UDPs. Go to the Bulk Administration Menu and select the Devices (or UDP) then select Update Phones. Use Update via Query.
If you then check the phones or UDPs, you will now only have one subscription of the IP Phone Service.
Thought I would post this topic as I know I tend to forget the many patterns and wildcards that can be used in IOS to march dial peer patterns and translation patterns for that fact. Some patterns are more common that others, however for the lab exam, Im sure the questions will have you creating more complex patterns to test your knowledge.
Patterns used in IOS
- 0-9 A-D * # These are standard DTMF characters used in IOS.
- . wildcard that matches any single digit. Important to note the . does not match the * or the #
- + can be used if first character to indicate +E164 dialling (IOS 12.4.20 – first introduced)
- + regex that means one or more of the previous character if not first in string
- ? regex that means zero or one of the previous character
- % regex that means zero or more of the previous character
- ^ regex that means beginning of line
- $ regex that means end of line
- T wait for interdigit timeout (only used in IOS). This combined with the . matches all numbers Example .T
- \ escape next character to use as literal character
-  range of digits. Example [2-4]66 means 266 or 366 or 466
- () a collected pattern of digits (normally used with regex) (100)?55511 could mean
55511 or 10055511
Let me know if you would like examples of patterns and I will add to post.
Quick note on how Cisco IOS matches dial peers. A single dial peer can be used for both inbound and outbound call legs. The rule destination-pattern can be used for both inbound and outbound dial peer matching, but remember destination-pattern match the calling number (ANI) for inbound call legs and matches the called number (DNIS) for outbound call legs.
Matching Inbound Dial Peer for both VOIP and POTS
- incoming called-number – Matches called number (DNIS)
- answer-address – Matches calling number (ANI)
- destination-pattern – matches calling number (ANI)
- port – Matches inbound Port (POTS ONLY)
- Default dial peer – used with VOIP dial peer ONLY
Default Dial Peer matches the below
- Any codec
- VAD enabled
- No DTMF
- DSCP 0
- No RSVP
- No TCL or VXML Applications
- No DID
Matching Outbound Call Leg
- destination-pattern – Matches called number (DNIS)
A popular integration is with using Microsoft Excahnge 2010 as voicemail as opposed to using CUE or CUC. In CUC and CUE a simple check box allows you to effectively disable the PIN (for internal only). However with MS Exchange 2010, there is no GUI option so its to the Exchange Management Shelll (Powershell) we go.
First thing to do is query the user’s mailbox to check the settings. IN particular we are looking for the option “PinlessAccessToVoiceMailEnabled”.
get-ummailbox -identity “emailaddress” | fl PinlessAccessToVoiceMailEnabled
If the mailbox does have a PIN enforced, the results will show “FALSE”
To disable the PIN on the mailbox type the following
set-ummailbox –identity email address –PinlessAccessToVoiceMailEnabled $true
Remember this only applies to internal access. Does not apply to accessing your voicemail from an external device. Also this does not apply to accessing our calendar or email via the phone system, you will need a PIN to access these areas of the MS Exchange 2010 Unified Comms.