First of all, in order to qualify, students need to undergo the authorized 360 “workshop” (be sure to recognize that it’s 2 weeks of training and quite a bit more expensive than some of the other options out there) and, as usual, waiver requests need to be approved by the instructor from the workshop. The waiver is then submitted to Cisco for approval and approved or disapproved without clear indication of success of that request. The program is temporary and begins on April 1^st 2010… just as another waiver program (that seems to have failed) is about to end.

The IPexpert team is determined to provide our students with the best possible training material available on the market. For that reason, we pledge right here and right now, that we will have the best preparation material on the market for the Core Knowledge section of the lab exams… by the time this program goes live. Yes, by April 1^st of this year. All IPexpert clients will have access to an OEQ / Core Knowledge eBook (we will be delivering eBooks for the R&S, Voice, Security and Service Provider labs).

Combine that with our current products and offerings:

• World-class Video on Demand (with supplemental Student Slide & Topology Books)
• World-class Audio on Demand (lecture different than VOD)
• World-class ILT Training (Week 1)
• World-class OWLE Training (Week 2)
• World-class Workbooks (and accompanying Detailed Solution Guides)
• World-class Workbook Video Walkthroughs (Hundreds of hours of video solutions)
• World-class Rack Rental at ProctorLabs (Latest & greatest hardware, online, with an unmatched GUI)
• World-class Online Community at OnlineStudyList.com (free online mentoring avenues)
• World-class Technical Support for all issues
• The largest alumni of successful CCIE students overall

In addition to all of the above (current offerings and upcoming FREE Core Knowledge eBook), we are shortly going to introduce two additions to our family of products in all tracks. We call them “vLectures” and “Ask the Expert Sessions”.

vLectures will be 2-4 hour long, live online lectures, delivered by one or more of our instructors on a given subject through our online classroom. These sessions will also be recorded and posted to our student accounts.

Ask the Expert sessions will be 2-4 long online sessions with one or more of our instructors and will focus on either a specific technology or a given lab from our Workbooks. Students attending the sessions will interact with the instructors, ask the questions and gain invaluable expertise. These will, also, be recorded and posted to student accounts.

Oh and one more thing…

These three new products … are going to be FREE for all our current BLS customers in all tracks. No need to qualify or pay premium.

Do our students need OEQ waivers? We think not. Here at IPexpert, we deliver on our promise to make you experts – with no shortcuts. We don’t think you need to “purchase” the ability to pass or “waive” the OEQ portion of your lab (by paying upwards of x2 or x3 as much for less training, less support and less proven success).

Good idea by the 360 team, or an act of desperation to salvage a failing program? You make the call…

Regards,

- Wayne A. Lawson II (CCIE #5244) – Founder & President, IPexpert, Inc.

If you come from CCM 4.1 days and now studying for your Voice CCIE Lab Exam, you might be aware that there’s a new codec setting in UCM 7.0 and later, I’m talking about the G.722 Wideband codec, I wanted to talk about it today as it may cause some confusion when comparing it with G.711 negotiation and configuration.

G.722 is a wideband codec (within the family of ADPCM codecs) which first recommendation came out more than 15 years ago, it was developed as a necessity to create a new voice codec standard that provides a better voice telephony quality than the toll quality that G.711 offers. It basically doubles the audio content within the same bit rate of G.711 i.e. 64kps, meaning that a wider set of frequencies are encoded- decoded. Therefore for the G.711 recommendation the range is up to 3.44 Khz and for G.722 reaches the 8Khz of audio frequency, which translates into a higher voice quality.

If we talk about the UCM configuration of this codec, we see that in the regions settings, the codec G711 and G722 options are presented by separate, however, these two options basically means the same and tells that the codec negotiation between the two endpoints involved should occur at a desired maximum rate of 64kpbs.

When negotiating codec, the endpoints involved in the call advertise their codec capabilities to the UCM which then chooses the common codec between them.

Now, let’s suppose that we have two endpoints supporting and advertising the G.722, are involved in a call whose region relationship are set to G711 or G722 codec, what codec will be negotiated between them? (Assuming all the remaining parameters both in regions and phones are set to the default value), I’m sure you know this one!!, well, it will be G.722 because UCM will always give preference to the higher quality codec (unless the link loss type is set to lossy), which is G.722 over G.711 in this case.

We should also be aware that with default configurations G.722 codec will be advertised and negotiated for intraregion calls (again, if the endpoints support it) as the default intraregion codec is G.711 and link loss type is low loss, now the question is how to get rid of this codec advertising and negotiation, well, you can actually do it in several places. In CallManager Service parameters you can disable the G.722 negotiation for all devices in the cluster with the “G722 Codec Enabled” parameter; this will be enough if the requirement is to disable G.722 clusterwide. In addition you can also disable the G.722 advertising from the phones in Enterprise parameters and phone settings with the “Advertise G.722 Codec” setting, having as always the phone precedence over the general (Enteprise Parameter) configuration. Having this configured, phones supporting G.722 will negotiate G.711 codec as in the CCM 4.1 days.

Be also aware that Cisco is and will be supporting the G.722 codec in most of their newer voice products, so a basic knowledge of this codec is a must.

That’s all for now, play around with these settings in your lab and write your comments!!

Stay tuned for more!!

Otto Sanchez

CCIE #25592 (Voice)

Support Engineer – IPexpert, Inc

URL: http://www.IPexpert.com

Please Note: In these example, we are using ProctorLabs Pod #111. Please, use Pod assigned to your session to try things out.

Using The Terminal Server

Picture 1 below shows the portion of your ProctorLabs user interface from which you can initiate connections to various devices.

On the top of the selection is the link called “Terminal Server”. Clicking on this link should open the the link using your operating systems’ Telnet URL handler and connect to ProctorLabs terminal server, allocated for your session. Take note here that Windows 7 doesn’t have Telnet installed by default. Quick search online should help you enable both Telnet client and Telnet URL handlers in Internet Explorer. The remainder of this text assumes that both work.

When you click on the Terminal Server link, you should see the connection open to the Terminal Server. Log in with your ProctorLabs username and password.

Connected to pod111ts1.proctorlabs.com.
Escape character is '^]'.

         ****PROCTOR LABS, INC. SECURE ONLINE RACK SYSTEM****
      WELCOME to Proctor Labs, Inc. CCIE preparation vRack.

    WARNING:  This system is for the use of authorized clients only.
          Unauthorized access is a violation of federal, state,
                        civil and criminal laws.

http://www.ProctorLabs.com

User Access Verification

Username: username
Password: password

PL-POD-111-TS-RS#

You are now connected to Terminal Server. You can see devices connected to it by typing “show hosts”

PL-POD-111-TS-RS#show hosts
Default domain is not set
Name/address lookup uses static mappings

Host                      Port  Flags      Age Type   Address(es)
BB3                       2013  (perm, OK) **   IP    10.1.1.1
BB2                       2012  (perm, OK) **   IP    10.1.1.1
R9                        2009  (perm, OK) **   IP    10.1.1.1
R8                        2008  (perm, OK) **   IP    10.1.1.1
R7                        2007  (perm, OK) **   IP    10.1.1.1
R6                        2006  (perm, OK) **   IP    10.1.1.1
R5                        2005  (perm, OK) **   IP    10.1.1.1
R2                        2002  (perm, OK) **   IP    10.1.1.1
Cat4                      2016  (perm, OK) **   IP    10.1.1.1
Cat3                      2015  (perm, OK) **   IP    10.1.1.1
Cat2                      2014  (perm, OK) **   IP    10.1.1.1
Cat1                      2010  (perm, OK) **   IP    10.1.1.1
BB1                       2011  (perm, OK) **   IP    10.1.1.1
R4                        2004  (perm, OK) **   IP    10.1.1.1
R1                        2001  (perm, OK) **   IP    10.1.1.1

If we take the example of R1 above, we can see that you can connect to it by telnetting to port 2001. You can do so from the server, by just typing “R1″.

PL-POD-111-TS-RS#r1
Translating "r1"
Trying R1 (10.1.1.1, 2001)... Open

         ****PROCTOR LABS, INC. SECURE ONLINE RACK SYSTEM****
      WELCOME to Proctor Labs, Inc. CCIE preparation vRack.

    WARNING:  This system is for the use of authorized clients only.
          Unauthorized access is a violation of federal, state,
                        civil and criminal laws.

http://www.ProctorLabs.com

User Access Verification

Username: username
Password: password

            You are on line number: 1

Router>

We are now connected to R1. We can configure it or do whatever we like. We can go back to the Terminal Server, by typing escape sequence <ctrl><shift> 6 followed by x. We are now back to terminal server, BUT – we are not yet disconnected from R1. Let’s connect to R2.

Router><ctrl><shift>6 x
PL-POD-111-TS-RS#r2
Translating "r2"
Trying R2 (10.1.1.1, 2002)... Open

         ****PROCTOR LABS, INC. SECURE ONLINE RACK SYSTEM****
      WELCOME to Proctor Labs, Inc. CCIE preparation vRack.

    WARNING:  This system is for the use of authorized clients only.
          Unauthorized access is a violation of federal, state,
                        civil and criminal laws.

http://www.ProctorLabs.com

User Access Verification

Username: username
Password: password

            You are on line number: 2

Router#

Let’s go back to R1. Press the escape sequence to go back to terminal server. There, type “show sessions”.

Router#<ctrl><shift>6 x
PL-POD-111-TS-RS#show sessions
Conn Host                Address             Byte  Idle Conn Name
   1 r1                  10.1.1.1               0     0 r1
*  2 r2                  10.1.1.1               0     0 r2

We can see two active sessions. One is connected to R1 and the other one to R2. We can also see small “*” next to R2. If we just press <enter>, we will return to the active session – marked by a star! Note the session numbers just before host name. We can use that to resume some other session. If we want to resume our session to R1, we can type “resume 1″, or simply “1″. Give it a try.

If you wish to destroy the session, type “disconnect <num>” on the terminal server, to disconnect the session <num>. Let’s disconnect our session 1.

PL-POD-111-TS-RS#disconnect 1
Closing connection to r1 [confirm]
PL-POD-111-TS-RS#show sessions
Conn Host                Address             Byte  Idle Conn Name
*  2 r2                  10.1.1.1               0     0 r2

Session 1 is gone. It will come back when we connect to, say, R4:

PL-POD-111-TS-RS#r4
Translating "r4"
Trying R4 (10.1.1.1, 2004)... Open

         ****PROCTOR LABS, INC. SECURE ONLINE RACK SYSTEM****
      WELCOME to Proctor Labs, Inc. CCIE preparation vRack.

    WARNING:  This system is for the use of authorized clients only.
          Unauthorized access is a violation of federal, state,
                        civil and criminal laws.

http://www.ProctorLabs.com

User Access Verification

Username:<ctrl><shift>6 x
PL-POD-111-TS-RS#show sessions
Conn Host                Address             Byte  Idle Conn Name
*  1 r4                  10.1.1.1               0     0 r4
   2 r2                  10.1.1.1               0     0 r2

Beware of this session number reuse, especially when time-pressed. You may want to open your devices in logical order and use them that way. If you decide to do so, it may be a wise idea to configure “exec-timeout” appropriately on destination hosts, otherwise your sessions may time out.

Once you get the hang of the idea, using Terminal Server is really quick and powerful way to access all your Proctor Labs devices.

However, some of use think there are more efficient ways. Read on for few suggestions.

Direct Sessions to Devices

Remember when we looked at Terminal Server and we connected to port 2001 for R1? You don’t have to connect to terminal server to open that session. You can telnet directly to port 2001 from your own computer, using any telnet client, or by clicking on the appropriate device from your ProctorLabs Web GUI! Let’s connect to R1 by clicking on it.

Connected to pod111ts1.proctorlabs.com.
Escape character is '^]'.

         ****PROCTOR LABS, INC. SECURE ONLINE RACK SYSTEM****
      WELCOME to Proctor Labs, Inc. CCIE preparation vRack.

    WARNING:  This system is for the use of authorized clients only.
          Unauthorized access is a violation of federal, state,
                        civil and criminal laws.

http://www.ProctorLabs.com

User Access Verification

Username: username
Password: password

            You are on line number: 1

Router>

We are now directly connected to R1! If you click on some other router or other device, you will be connected directly to it!

You should note that you cannot have more than one connection to the same device. In a case you are getting “Connection Refused” message, you need to telnet to Terminal Server and clear the existing session to the device you wish to connect to.

Using direct sessions to devices is an efficient method. Using built-in telnet client in Windows (and some other operating systems) on the other hand is not. Many of them lack features like increased scroll buffer, resizable windows, etc. For that reason, there are other clients that can be used instead. Here are some of the more popular ones.

SecureCRT (Windows)

SecureCRT is the terminal application available you in the CCIE lab. Newer versions of it support some options not available during the exam (for example, tabs), but those advanced features may prove to be useful during studies, when you are not trying to replicate the exact environment in the lab.

The most efficient way to use SecureCRT is to utilize its built-in bookmarks, called Connections. This system can be accessed by choosing File->Connect menu, or <alt>-c keyboard shortcut. Screenshot below is an example of bookmarks created for ProctorLabs Routing and Switching Pod 111.

Double-clicking on any of the bookmarked devices will open a new tab (or window) with the connection to the appropriate device. What’s nice with this approach is that the title bar of the window will be automatically set to the name of the device.

Of course, the most difficult and time consuming bit is actually building bookmarks. Well, I have special treat for you here. We’ve already done it for you – for all our pods in all our tracks, you can get them here: ProctorLabs-SecureCRT.

Installing IPexpert’s Bookmarks to SecureCRT

Now that you have the bookmarks, it’s time to install them. Please, follow this step-by-step procedure for an easy install.

1. Download the ProctorLabs-SecureCRT.zip above and save it to temporary folder
2. Open SecureCRT and find Options -> Global Options menu
3. Open the above menu and select General from the tree on the left. Copy “Configuration folder” path to clipboard. See picture below:



4. Close SecureCRT, find and open that folder in Windows Explorer. Go to subfolder called Sessions. If one does not exists, please create it.
5. Extract the contents of the ProctorLabs-SecureCRT.zip file into this folder. You should now have subfolder called ProctorLabs.
6. Start SecureCRT and select File->Connect.

You should have all of our bookmarks in your SecureCRT now!

Putty and Putty Connection Manager (Windows)

Putty is a free terminal application for Windows, which is proving to be very popular. By itself, it provides cumbersome bookmarks management, however, there is 3rd party add-on, called Putty Connection Manager. If you happen to be Putty user, look for this one online – you will be pleasantly surprised. To see it in action, just watch our Routing and Switching Video on Demand or a screenshot below.

Just as with SecureCRT, most of the work is to create bookmarks for your Pod. If you take a look at the screenshot above, you will notice that it shows many pods. Yes, you guessed it right! You can get database file here: ProctorLabs-PuttyCM.

Installing IPexpert’s Bookmarks to Putty Connection Manager

This operation is a little bit different than the one with SecureCRT. Especially so because there are two ways in which it can be done (CCIEs love alternative solutions, don’t we?). After you have downloaded the ProctorLabs-PuttyCM.zip file above, extract the contents to a temporary folder.

If you don’t already have any bookmarks in your Putty Connection Manager, you can copy the file to more permanent location and change extension from XML to DAT. Next, from File menu, select Open and navigate to your ProctorLabs-PuttyCM.dat file. When you open the database, make sure that Connection Manager option in View menu is enabled. You should now have nice ProctorLabs bookmarks tree on the right.

If you already use Putty Connection Manager, using another database may or may not be the thing you want. Another approach is to import the entries from XML. You can use the same file, but in order to import bookmarks, you need to have an open database. To initiate import process, go to Database menu, select Import and Export menu. Chose option to import and in the next step navigate to ProctorLabs-PuttyCM.xml file. When you have finished, your existing bookmarks should be updated with new ProctorLabs ones!

Whatever step you used, you can make the database as the default one to open every time you open Putty Connection Manager and you are all set.

But… what if you are using some other operating system, say, Mac or Linux? Stay tuned, that’s coming soon!

–
Marko Milivojevic – CCIE #18427
Senior Technical Instructor – IPexpert

Mailto: markom@ipexpert.com
Telephone: +1.810.326.1444
Fax: +1.810.454.0130

The last couple of weeks I had to struggle with time to study for the CCIE Voice exam.

I managed to do a little bit of CUCME studying.

In this blog I am going to post a basic configuration to start off with to understand how you configure SCCP endpoints with CUCME.

Step 1

Set up TFTP server on router for phones to pick SCCP firmware

!

tftp-server flash:PHONE/7940-7960/P00308000500.bin alias P00308000500.bin

tftp-server flash:PHONE/7940-7960/P00308000500.loads alias P00308000500.loads

tftp-server flash:PHONE/7940-7960/P00308000500.sb2 alias P00308000500.sb2

tftp-server flash:PHONE/7940-7960/P00308000500.sbn alias P00308000500.sbn

!

Step 2

Define system parameters for SCCP phones

!

telephony-service

no auto-reg-ephone

max-ephones 2

max-dn 2

ip source-address 10.10.110.3 port 2000

load 7960-7940 P00308000500

create cnf-files

!

Step 3

Create the phone lines (DN)

!

ephone-dn 1 octo-line

number 1001

description 1111-1001

!

ephone-dn 2 octo-line

number 1002

description 1111-1002

!

Step4

Create a phone and map it to a phone line (DN)

!

ephone 1

description 79XX PHONE 1001

mac-address 0079.96FF.287F

type 7960

button 1:1

!

ephone 2

description 79XX PHONE 1002

mac-address 003C.D56A.9826

type 7960

button 1:2

–

Regards,

Iwan Hoogendoorn

CCIE #13084 (R&S / Security / SP)

Sr. Support Engineer – IPexpert, Inc.

URL: http://www.IPexpert.com

In this blog I am going to post a basic configuration to start off with to understand how you configure SIP endpoints with CUCME.

Step 1

Set up TFTP server on router for phones to pick SIP firmware

!

tftp-server flash:PHONE/7940-7960/P0S3-08-9-00.loads alias P0S3-08-6-00.loads

tftp-server flash:PHONE/7940-7960/P0S3-08-9-00.sb2 alias P0S3-08-6-00.sb2

tftp-server flash:PHONE/7940-7960/P003-08-9-00.bin alias P003-08-6-00.bin

tftp-server flash:PHONE/7940-7960/P003-08-9-00.sbn alias P003-08-6-00.sbn

!

Step 2

SIP configuration and setup of registrar server

!

voice service voip

allow-connections sip to sip

sip

bind all source-interface Vlan100

registrar server expires max 600 min 60

!

voice register global

mode cme

source-address 11.11.101.1 port 5060

max-dn 2

max-pool 2

load 7960-7940 P0S3-08-6-00

authenticate register

tftp-path flash:

create profile

!

Step 3

Create the voice register dn’s (phone lines)

!

voice register dn 1

number 2001

!

voice register dn 2

number 2002

!

Step 4

Create the voice register pools (phone configuration)

!

voice register pool 1

description 79XX PHONE 2001

id mac 003F.A3F4.AA54

type 7960

number 1 dn 1

dtmf-relay sip-notify

username 2001 password cisco

description 2222-2001

!

voice register pool 2

description 79XX PHONE 2002

id mac 002D.456E.345A

type 7960

number 1 dn 2

dtmf-relay sip-notify

username 2002 password cisco

description 2222-2002

–

Regards,

Iwan Hoogendoorn

CCIE #13084 (R&S / Security / SP)

Sr. Support Engineer – IPexpert, Inc.

URL: http://www.IPexpert.com

Today’s topic is going to be the desktop phone control from Cisco Personal Communicator Client, CUPC, via CTI and its configuration both in CUPS and CUCM.

As many of you are aware of, the CUCP’s CTI phone control is performed directly from the presence client itself via CTI/QBE interface, in other words the CUCP talks to the CUCM CTI Service to control the designated desktop phone, there’s no intervention of the CUPS in the process.

First of all, perform the basic integration between CUCM and CUPS (this configuration assumes no DNS servers are in the network):

• Add the CUPS as an application server in CUCM ->System ->Application Server menu
• Assign Presence capabilities to the end user (Enable CUP and CUPC use) in CUCM ->System ->Licensing -> Capabilities Assignment
• Run the CUPS post installation setup, you can use the CUCM Admin user as the AXL user required for this setup
• Change the presence server name to IP Address in the CUPS System-> Topology menu
• Configure the Cisco UP SIP Proxy service parameter and set the domain name, go to CUPS System-> Service Parameter
• Start all the CUPS services from the Cisco Unified Serviceability-> Tools-> Service Activation Menu
• Reboot the presence server for the name change to take effect

Now, let’s configure the CTI control config specifics:

• In CUCM end user-> assign device configuration, associate the corresponding device to the user, and very important but sometimes forgotten, assign the end user to the Standard CTI Enable user group
• Also in the CUCM end user configuration, assign the end user primary extension in the Directory Number Associations section
• Make sure “Allow Control of Device from CTI” is checked in the regarding phone device and line configuration
• In CUPS-> Application-> Cisco Unified Personal Communicator-> User Settings Menu, assign the TCP CTI Gateway Profile (automatically created during the CUPS synchronization with CUCM) for the user
• Finally, log into the CUPC and control your phone desktop, you should see a window similar to this:

Sometimes a restart of CUCM CTIManager service and CUPS Services are needed in order to get CTI control working properly from CUPC

Well, remember to be very specific in your configurations, you might be asking why I didn’t mention SIP trunk configuration, device line end user association, etc. My purpose here was only to configure CTI phone control via CUPC and not to enable presence features. This approach might help you to understand every piece of CUPS, save very valuable time in your lab exam and configure exactly what you are asked for.

Try this at home!!!

Otto Sanchez
CCIE #25592 (Voice)
Support Engineer – IPexpert, Inc.
URL: http://www.IPexpert.com

Here is another status update of my progress in pursuit of my CCIE Voice certification. Last week was again a week where things didn’t go very fast.  I was stuck at the chapter where I needed to do a mutual conversion between SCCP and SIP images on a phone…for the simple reason that I don’t have a phone.  I was not sure if I could do this with the softphones that I am using to practice basic stuff.  So the only option was to get some Cisco 7960’s.

After a whole week searching for these phones I finally found someone in the Netherlands who was selling three Cisco 7960´s.  If you look on Ebay, there are enough for sale…but I did not want to waste a lot of time, as things are going really slow.

Last week I also became really sick … and I thought to myself, “could things any slower than this?”  But then again, during my previous 3 CCIE studies, I also had these moments and I am sure all of the students have these moments!

Anyway, my 3 x Cisco 7960´s are on their way and I hope I will receive them in the next day or so.  Ahh, and as I am using IPexpert material, I forgot that I need to convert my my account to the new type account!  Will do that as soon as I finish this blog!

I know not much technical stuff went down last week, but, I will make it up next week for you guys!

Thanks for reading and see you guys next week!

Iwan Hoogendoorn
CCIE #13084 (R&S / Security / SP)
Sr. Support Engineer – IPexpert, Inc.

In this blog, we will begin with Mobile Connect; aka “Single Number Reach” (SNR). SNR supports the ability to redirect incoming IP calls from CUCM to up to ten different remote devices. During this process the incoming call will ring the local IP device and any of the enabled remote devices. In the event this call goes unanswered it is routed to the local IP device’s destination, not that of the remote device.

Now then, let’s move to the nuts and bolts and build our scenario. Jill is a Sales Rep at a prominent Toy Distributor. The majority of her work week involves extensive traveling. Due to the nature of her business, it is essential to ensure reachability. To add to this, she has indicated it is very inconvenient to manage multiple voice mail accounts. We must also ensure we are complying with company standards which state all remote devices are within the local calling area.

For the sake of this blog, let’s assume Jill’s Enterprise IP device is configured and associated with an end user account.

User Account Configuration

This activates Mobile Connect and allows it to work with an adjunct device (in this case, Jill’s desk phone). Keep in mind, this method consumes 2 DLU’s. If you do not associate with an adjunct device, 4 DLU’s will be consumed.

1. Ensure the account is associated with the correct IP device

2. Check the “Enable Mobility” check box and select the “Primary User Device”

3. Check the “Enable Voice Access” check box (This will be covered in Unified Mobility – Part 3.)

4. Ensure the user is assigned to the “Standard CCM End Users” Group

Remote Destination Profile Configuration

The remote destination profile contains the parameters that apply to all remote destinations for that particular user. In this case, these settings should accommodate the same capabilities as the Enterprise IP phone. Keep in mind, the “Calling Search Space” for the profile only applies when engaging Mobile Voice Access and Enterprise Feature Access calls. (This will be covered Unified Mobility Part 3.) The “Rerouting Calling Search Space” is used to route calls to the Remote Destinations attached to the user’s profile. Be careful not to forget this in your configuration. You may also in some cases want to apply calling restrictions. In this scenario, we would utilize a local-only CSS in order to adhere to company policy.

Remote Destination Configuration

A remote destination represents a mobile or other remote phone that is configured to accept calls that come from the system as a result of the shared line configured in the remote destination profile. This is where the rubber hits the road. Several remote destination call characteristics are applied in this configuration component. For now, we are just going to cover a few of the tricky ones.

1. When entering the “Destination Number”, ensure to enter the number as if you were dialing it direct from the Enterprise IP Device.

2. Answer too soon timer – this timer protects the call from being forwarded to the remote device’s voicemail. An example of this would be if the remote device was in an area where mobile network was unavailable and the ring cycle was eliminated, thus causing the call to be “answered too soon” for CUCM to maintain control of the call and properly forward back to the Enterprise Voicemail.

3. Answer too late timer – this timer sets the amount of time CUCM allows for the remote device to answer. Once the timer expires, the call will be pulled back and transferred to Enterprise voicemail. This timer will need to be adjusted per Remote Destination and will depend on the typical ring cycle of the remote device.

4. Delay Before Ringing Timer – depicts the time that passes before the call is extended to the remote destination. It is recommended to set this to 0 (zero) when hunt groups are utilized.

Once desired settings are applied, check “Enable Mobile Connect”. This will allow calls to be extended while simultaneously ringing at the Enterprise IP device. For this blog, we will assume Jill would like the Ring Schedule to be set for “all of the time”. (Time of Day access will be covered in Unified Mobility – Part 2)

At this point it is good to double-check the Enterprise IP device configuration to ensure the call-forward no answer settings are routed to voicemail. It is also good to ensure that your “ring no answer” timer will not restrict the timing you have depicted in the Remote Destination.

It is now time to notify Jill of the good news….

Jill embraces SNR and is now asking if there is a way for calls that originate on the Enterprise IP Device (desk phone) can be moved to her Remote Destination without call interruption. She is also requesting if a SNR call is retrieved on her mobile device as; is there a way to transfer the call back to my desk phone once back in the office?

To be continued…

Amy Ryan CCIE #24677 (Voice)
Sr. Technical Instructor – IPexpert
Mailto: aryan@ipexpert.com
Telephone: +1.810.326.1444
Live Assistance, Please visit: www.ipexpert.com/chat
eFax: +1.810.454.0130