CUE Basic Integration with CME

Here are all the steps to perform if you want to integrate the CUE with the CME

  1. Create a SIP dial peer pointing to the CUE Module
  2. Configure the MWI On/Off extensions
  3. Configure the connectivity between CME and CUE Modules
  4. Perform CUE Configuration

For the first step , your dial peer will look like

dial-peer voice 1000 voip
destination-pattern 5555
session protocol sipv2
session target ipv4:172.17.1.1
dtmf-relay sip-notify
codec g711ulaw
no vad
!

The configurations of the MWI On/Off must be generic as it must cover all numbers and it is generally implemented as a kind of prefix as the MWI must know which number must be turned on or off. So it adds the number after the extension the MWI shortcut.

ephone-dn 50
number 5000….
mwi on
!
ephone-dn 60
number 6000….
mwi off

Regarding the link configuration between the CUE and CME, you need to borrow the Ethernet interface where the CUE module resides (don’t forget that CME and CUE can be splitted). So everything under the service-engine ( this is the CUE module) will rely on the Ethernet interfaces:

interface Service-Engine 1/0
ip unnumbered FastEthernet 1/0
service-module ip address 172.17.1.1 255.255.255.0
service-module ip default-gateway 172.17.1.254
!
ip route 172.17.1.1 255.255.255.255 Service-Engine1/0
!

In a multi-site implementations , you have then to configure a translation between your remote CME and the central CUE/CME because we told before that CUE relies on SIP Protocol and the rest of your network is an H323 network , so you need to translate all H323 request to SIP. You can do it generally with the config:

!
voice service voip
allow-connections H323 to sip

Call Manager Express – CME : Quick Definition

CME provides call processing and enterprises telephony features in a small-to-medium sized network environment, and supports an amount of IP Phones depending the router platform.

To deploy it , you must also install several additional files in the flash and be sure to have the clock set up (it can be done also via the NTP) as it is needed to generate the CNF-Files.

SRST Dial Plan Considerations

To match the local number with the external number during a SRST failover, you can use the command dialplan-pattern <<tag_pattern>> extension-length <<length>>. this command also ensures that a full E.164 address is sent as the ANI for outgoing calls. The dialplan-pattern command causes the SRST router to create an additional virtual dial peer for local extension corresponding to the pattern specified in the command.So, this command can be used to map the DNIS sent by the PSTN to a local extension.

Pay attention that if you play with translation rules on your voice-port, it may be a good choice also to continue with digit manipulation to conform your SRST dialplan as the translation rule are processed before.

SRST Call Transfer

SRST routers support also the call transfer between IP Phones by default when they are registered onto it. But to really have a successful transfer call , you need also to precise the pattern transfer and the way on how it will transfer your call. So don’t forget to implement these commands:

!
call-manager-fallback
transfer-pattern <<pattern>>
transfer-system <<method>>
!

What are representing the parameters ?

  • <<pattern>> is the pattern that you authorize to dial under SRST mode ( example …. or .T)
  • <<methods>> is the call transfer method operation.

Let’s see what are the operation mode possible:

  • Blind : Cisco proprietary method where calls are directly transferred without any consultation.
  • Full-blind : H450v2 standard for call transfer where calls are directly transferred without any consultation.
  • Full-consult : H450v2 standard for call transfer where you need to perform a consultation before to initiate the real transfer. This method requires two line to make the transfer and if the second line is not available then the full-blind is used instead.
  • Local-consult : H450v2 standard for call tranfert but this time, it is only valid for local transfers.So again if you don’t have the second line or you are not transferring to a local party , the blind method is used instead.

Full-blind and full-consult are the Cisco preferred method.

Don’t forget also to configure your line as dual-line to allow not only the call transfer but also the call waiting , conferencing and so on

Page 6 of 25« First...234567891011...20...Last »