Quick Tip #3

Question: I am trying to import CUCM end users into Unity Connection, but my search under CUC > Tools > Import Users does not return any results:

Answer: Make sure that you check the following:

1. AXL connections are setup correctly under Telephony Integrations > Phone System > Edit > AXL Servers
2. AXL connections are using port 443
3. AXL service is activated and running on Unity Connection
4. CUCM end user is associated to its IP phone and that a primary extension is set under User Management > End User

Quick Tip #2

Question: How can you send a test call from an IOS gateway itself?

Answer: You would use “csim start [dialed digits]“.  However, be aware that though the dialed digits strings will match the destination-pattern defined in your dial peer.  Any voice translation-profiles applied at the dial-peer level will not be activated during a csim test call.

Case in point, I have the following setup:

dial-peer voice 11300 voip
 translation-profile outgoing OUT-GK-EXPAND
 destination-pattern [15]…$
 session target ras
 dtmf-relay h245-alphanumeric
!
voice translation-profile OUT-GK-EXPAND
 translate called 11300
!
voice translation-rule 11300
 rule 1 /5…$/ /1#1212394\0/
 rule 2 /1…$/ /1#1617863\0/

If I dial “5002″ from BR2-PHN2 (ext. 3002), dial-peer 11300 is matched ([15]…$) and then translated from 5002 > 1#12123945002 before it is sent, via RAS, to my gatekeeper. 

If I issue a “csim start 5002″, it will match my dial-peer 11300 (“debug voip dialpeer”), but the translation will not occur.  Verify this for yourself by running “debug gatekeeper main 10″ from your gatekeeper.  You’ll see that the call comes in as “5002″ instead of “1#12123945002″.

Happy labbing!

Quick Tip #1

Question: In IOS, the default dial-peer terminator is #.  This terminator never needs to be added to a destination-pattern command.  It is a system-wide command.  How would you change the dial-peer default terminator in the IOS?

Answer: You would use “dial-peer terminator [0-9, A-F, *, or #]“