Category list

Call Forwarding

Call forwarding (for busy, no-answer, and unconditional forwarding) raises many of the same issues as call transfer. Likewise, these issues can be addressed using an MTP to simplify the H.323 signaling operations.

As you read in Chapter 7, the preferred method of handling call forwarding for Cisco CME is H.450.3. Again, Cisco CME can disable its H.450.3 feature when it detects calls from a Cisco CallManager. Under these circumstances, the Cisco CME system falls back to using internal call forwarding or VoIP-to-VoIP call routing for intersite call forwarding.

Just like the call-transfer case, an MTP allows internal call forwarding to occur without impact to the H.323 call leg. Of the three types of forwardingbusy, no-answer, and unconditionalthe no-answer form generally involves more signaling complexity. When a call forward no-answer occurs, the preliminary call negotiation for the original called phone must be revoked (after the no-answer timeout). It is replaced with a new call to the forward-to destination phone. The forwarded call can potentially require the use of different parameters than those negotiated for the original called phone. The busy and unconditional forms of call forwarding usually don't involve a preliminary call actually reaching the forwarding phone; this tends to simplify the signaling. Figure 8-6 shows call forwarding between a Cisco CME system and a Cisco CallManager using MTP.

Figure 8-6. Cisco CallManager and Cisco CME Call Forwarding with MTP

You can see that Figure 8-4, which shows call transfer, and Figure 8-6, which shows call forwarding, are nearly identical. Figure 8-7 shows intersite Cisco CME call forwarding for a call from a Cisco CallManager. Compare it to Figure 8-5 for the equivalent call transfer case.

Figure 8-7. Cisco CallManager Forwarding with Multiple Cisco CMEs

For the special case of call forwarding to a voice mail system, note that the H.323 call setup for the forwarded call includes the original called number (the number of the forwarding phone). This can be used to provide integration with the voice mail system and to allow automatic selection of the voice mailbox that belongs to the forwarding phone.

Connected Party Name and Number Services

One of the reasons why Cisco CME uses the H.450.2 call transfer and H.450.3 call forwarding mechanisms is that it provides a standard means to support updating of the originating phone's display to track who the connected-to party is. Connected party display is often considered an important feature in business telephone networks. The connected party display is broader than the usual residential caller ID display you may be familiar with at home. Not only does it provide information about the calling party for inbound calls, but it also provides information about the called party for outbound calls. The connected party display can show you the name of the person you have called, for example. This is in contrast to simply displaying the number you dialed . Also, the standard caller ID display function provides a one-time indication of who the caller is only at the beginning of an incoming call. The connected party display feature allows for midcall updates of the connected party information that occur when the far end of the call performs a call transfer.

For example, after a caller has been transferred, his phone display can be updated to show the name and number of the extension he has been transferred to. Likewise, when you receive a call transferred to you by someone else, your phone display may initially show the caller ID of the person who is transferring the call to you. After the transfer is complete, your phone's display may update to show the caller ID of the transferee (caller).

When Cisco CME disables the H.450.2/3 mechanisms to interwork with Cisco CallManager, this display update mechanism is unavailable. However, Cisco CallManager has its own mechanism for performing connected party display updates. Cisco CallManager uses H.323 display and information IEs. Cisco CME also supports these IEs for performing connected party display updates.

The H.323 IE messages are carried as part of the H.323 signaling path . They are unaffected by the use of an MTP because they are informational messages only and don't generate changes to the call signaling state. This means that even when a Cisco CallManager performs an internal call transfer hidden behind an MTP, the H.323 information and display IEs are received by the Cisco CME system and are used to provide display updates. Not only can Cisco CME receive display IEs from Cisco CallManager, but it also sends display IEs to Cisco CallManager when Cisco CME performs internal transfer or forwarding.

Cisco CME sends these display IE messages for all H.323 calls regardless of whether a Cisco CallManager is involved in a call. This means that you can still get intersite connected-to party updates in Cisco CME networks where you have chosen to globally disable H.450 services.

Buy on amazon.com >>

Au D., Choi B., Haridas R.

<< Previous page

Table of contents

Next page >>