Welcome to the Cisco Networking Professionals Ask the Expert conversation. This is an opportunity to discuss Call Manager 3.3 with Cisco expert Dave Goodwin. Dave has been a voice escalation engineer for Cisco's TAC for the last three years. He joined Cisco in 1998 as a TAC engineer, and is now involved in handling escalated issues and new product testing. Feel free to post any questions relating to Call Manager 3.3. Remember to use the rating system to let Dave know if youve received an adequate response.
Dave might not be able to answer each question due to the volume expected during this event. Our moderators will post many of the unanswered questions in other discussion forums shortly after the event. This event lasts through January 31. Visit this forum often to view responses to your questions and the questions of other community members.
Will CM 3.3 support the 7920 wireless IP Phone that i've been hearing rumours about? Will it require any additional equipment (other than APs) to support that wireless phone?
Since such a phone has not yet been announced, I am unable to answer your question with a high degree of accuracy.
That being said, the latest Cisco CallManager 3.3 release does not include the definition for any such phone. However, there is a streamlined way to add support for new phones and gateways that is easy for both Cisco Business Units as well as for administrators to install. So at such time as a phone like the one you mentioned becomes available, it will require little effort to add the support for it.
Under "System Capabilities Enhancements", on this doc it says "New Cisco IP Phone (Cisco IP Phone 7905 and Cisco IP Phone 7920) support"
Then that is the answer. Any other information about the Cisco IP Phone 7920 would need to be obtained through your Cisco account representative.
I want to be able to capture the CLID number coming into my 3745 (h.323) gateway, and route it based upon a SQL database. I have IVR and ICD setup to attatch to query the SQL database, but I can't seem to find a good way to present the number to the script. Is there an easy way to do this? I have seen a way to do it with Unity, but I want to make it transparent to the caller (no tranfering you now) type message. Any ideas on this?
Although this is not specific to Cisco CallManager 3.3, you should be able to easily receive the Caller ID from the gateway and compare it to records in the database. For CRA 2.2, the Get Session Info step will allow you to store the value of the Caller ID in a local variable, that can then be used to query the database:
For CRA 3.0, the Get Call Contact Info step will allow you to do the same:
Does 3.3 give CallManager the ability to recieve caller ID calliing party name information in the Facility IE field? If not, when can we expect to see this addition?
In the initial release of Cisco CallManager 3.3(2), the answer is no. I do know that this particular feature is currently being finalized in the software, and I would hope to see its release publicly available in the Q2 timeframe of this year. The timeframe I have presented is subject to change.
As a follow-up to this, the feature will be available in Cisco CallManager 3.3(3). The timeframe information remains the same.
Note that this will require any MGCP gateway with PRI backhaul, such as a 6608 port or a 26xx series gateway. It will not work while using an H.323 based configuration.
If you wish to simply receive Caller ID Name from the PSTN or a PBX using the Facility IE, then it will work with any T1 protocol type, except for 4ESS where Facility IE is not defined, or QSIG which uses different information in the Facility IE.
If you are wishing to deliver the Caller ID Name to a PBX using Facility IE, then CallManager needs to be configured on that PRI to use the NI2 protocol.
This is great news, as I have 2 customers waiting for Calling Name display !!
Do you know if there are any issues with Calling Name Display on the ICS 7750, PRI MRP blade ? (I assume it will have to use MGCP) ?
No, I am not aware of any issues specific to those platforms. As long as the correct version of Cisco CallManager is installed (after it becomes available) and the PRI endpoint is controlled via MGCP, then it will work.
does 3.3 have the ability to forward calling party ID to an external number? For example, I use Unity as my auto-attendant. Whenever someone forwards their calls of-net (to a cell phone for example) they get the call but it is the caller ID infor from CM not the original caller that shows up. This makes it kinda hard to screen calls :) Thanks in advance
Yes, Cisco CallManager can definitely use the original calling party's number in many scenarios like the one you describe. However, the exact circumstances may have an effect on the end result. For example, if an analog line is used for the outbound call to the cell phone, then there is no way to alter the Caller ID. Additionally, if the call is answered by a human or by another station-based system (such as Cisco Unity) and then transferred to the cell phone, then that will result in the phone's Caller ID being sent rather than the original party's.
There are couple features that are available in the traditional telephony world that are not directly available in the Callmanager platform. Can you tell us if they are in 3.3 or give us a roadmap on when we might see an update which might address them.
1. Avaya's Call Answer Group or Call Coverage group. Ring Simulateously on multiple phones and once the call is answer that line is still available to ring through to the other phone in that group.
2. Call waiting with the ability transfer one of the calls if two calls are on the are live same line.
3. MWI via QSIG.
4. MGCP support for the 1700 platform
1. This is a very useful feature, and could be described as a hunt group that rings multiple hunting stations at the same time. Cisco CallManager 3.3 does not have this capability. It is definitely on the roadmap and is currently planned for the next major release. The timeframe is currently approximately Q4 of this year. As it gets closer you would be best served by speaking with your Cisco account representative to get updates on the timeframe.
2. If I am understanding this feature description correctly, I believe the answer is the same as for #1.
3. Also same as #1. Cisco CallManager 3.3 does add support for basic QSIG calls, including Calling Name and Connected Name, which was an important first step towards long-term, feature-rich QSIG support.
4. I don't know of support for this in the "traditional telephony world" as you mentioned. ;-) In the administration pages, I now see Cisco 1751 and 1760 platforms as configurable gateways for MGCP support. A call to Cisco TAC should reveal which IOS levels support this capability on those two platforms.
More and more features require MGCP instead of H.323, for example Q.SIG is one of that. When will be the 7200 PA-VX port adapter supported with MGCP?
In FAQ's about CCM 3.3, it writes that FastStart is supported for only incoming calls. Do you plan to support FastStart for both incoming and outgoing calls for CCM 3.3 in the near future? If the answer is yes, can you please tell us when will they be supported?
Thanks in advance.
I'm wondering how I could implement a system where a user (or operator) can pick up an IP phone.. and automatically have it dial 12-15 other IP phones within our network. We are currently running CM 3.0.. and need to implement this sytem immediately. Basically it would be used in emergency situations, where we would want to notify everyone at once about whatever is happening (i.e. fire dept, police, different depts, etc) Any & all help would be greatly appreciated.
You can do it using CRA Editor 2.2 which comes as a plugin in icd ivr application software. icd-ivr 2.2.5 is the latest version and can be found in Software Center. But you have to check first the compatibility matrix since you use an early version of CCM.
Cisco CallManager does support shared lines, however that feature does not offer the ability for all the parties sharing that line to all use it at the same time and all hear the same party.
If you need to deliver the same text or audio information to a number of phones simultaneously, then the best idea would be to use a third party application. Use the following link to find a third party near you:
The only other home-grown way I can think of to accomplish this task would be to write an XML service that sends HTTP push commands to the desired IP phones in the network, which cause them to either bring up static or dynamic generated text on their screens from a web server, or causes them to dial a MeetMe conference number that has already been setup.
If you wish to pursue the home-grown route, information on XML Services programming for Cisco CallManager 3.0 phones can be obtained from:
Additionally, more extensive information about this can be obtained in the Cisco Press Book Developing Cisco IP Phone Services: A Cisco AVVID Solution, ISBN number 1587050609.
H.323 FastStart support for outbound calls is a bit more difficult implementation from an architectural standpoint with Cisco CallManager, hence the reason for inbound support only right now.
Support for outbound calls will be available in a Cisco CallManager 3.3 "Feature Patch" (not to be confused with a Support Patch). The currently planned release date for this Feature Patch is Q2 of this year, subject to change.
As far as I know, this is not currently planned for the 7200 as a voice platform. If this is an important capability, then please share your business case(s) with your Cisco account representative so they are able to present this information to the appropriate folks within Cisco.
What I can tell you is that all the software work needs to be accomplished on the IOS side for the 7200. Cisco CallManager will very easily be able to support the 7200 as an MGCP gateway at such time as the IOS feature might become available.
Posted this as a question before I saw your forum......
I have not been involved in any upgrades to 3.3, save those of internal Cisco sites.
The upgrade is a more involved procedure than previous upgrades, due to the required steps of 1) backup, 2) reinstall OS 2000.2.3 from CD, 3) install/restore.
That being said, an upgrade to Cisco CallManager properly performed will succeed. However, I have no qualms stating that the process can be easier using one of the approved servers that use RAID 1 mirroring, plus one extra drive. In this case, if any mistakes are made or problems encountered, it is much quicker and easier to go back to the previous version and call Cisco TAC for assistance. The alternative (which is completely viable) that takes longer involves installing the previous version of 3.1 or 3.2 and performing an MCS Restore.
can we install version 3.3 in an MCS-7822 server? Does it require a memory upgrade or the default (512 MB) is adequate? We want to install Application Engine for Extended services too. I cannot find anywhere the system requirements for this version (everywhere it is just refered that an MCS is required).
Cisco CallManager 3.3 is supported to run on an MCS-7822 server, and I would say a minimum of 512MB is required, and I would also say that Extended Services is not supported at the same time to be on the safe side. You might think of the MCS-7822 as an earlier, slower version of the MCS-7815 server, except with a lower maximum amount of memory. Its capabilities are listed here:
I am trying to find out if there is limit in the number on digits that can be entered into a speed dial on either a 7910 or a 7960 IP phone. Could you please either point me to where I can find this information or post it here if you know it. Thanks is advance for you help.