Hi, am new on this blog i need some help. I want to integrate IP phones remotely with the CME at the head office using DHCP to give the IP address and the call number. I have tried using the IP helper-address but may no head way.Thanks.
Hi Guyz,
I am New Member, i am working on Voice Project with Call Manager Express(very new for me) , I have lot of queries can someone guide me through it
1)I have 2 Cisco 2951 routers can they have HA(publisher,subscriber) like Call Manager ?
A)Cisco 2951 rtr with CME:-8.6 and CUE:-8.6
2)I have Call Center set up which i need to Implement wherein all users will get call via Toll Free Number but the users wont have DID numbers as extensioni have 2 PRI and both should be active and by pressing 9(TATA PRI) and 0(REL PRI) how to configure this set up
3)How the users will make outbound call and take board line number
4)I need to configure common mailbox if the agents are busy customer can leave Voice mail for them ?(I JUST HAVE 6 PORTS IN WHICH IVR AND MAIL BOXES SHOULD WORK)
Can somebody help me with configuration ? or any notes
Thanks in Advance for help,
Hi ,
Just as a reminder when you sit in the lab, try to not forget to put the correct Calling number , type and plan and this for all situation so it is true as well for SRST.
So a good vision of the call routing is important
Here are all the steps to perform if you want to integrate the CUE with the CME
- Create a SIP dial peer pointing to the CUE Module
- Configure the MWI On/Off extensions
- Configure the connectivity between CME and CUE Modules
- 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
CUE is as the CME a small business voice mail solution that you can easily deploy on a router. Most of the time, CUE will reside on the same chassis than the CME but for some implementations, you can split both. The only backdraw is that you must have a LAN connectivity between your elements.
CUE is interesting because it doens’t provide only voice mail but can also provide a small Auto-Attendant (AA). The integration between CUE and CME is done via the SIP protocol, while the integration with a Call Manager will be done via JTAPI ( CTI-QBE). It can be the case for implementation where you need to provide Unity backup on SRST location).
CUE will be supported by Network Module (NM-CUE) or as an Advanced Integration Module (AIM-CUE).
CME can be integrated with Cisco Unity, it is more or less as an integration with Call Manager except the fact that you must every setting in the CLI mode. Let’s see a kind of basic config:
!
telephony-service
voicemail 5555
!
ephone-dn 10
number 1234
call-forward busy 5555
call-forward noan 5555 timeout 10
ephone-dn 16
number 5566
mwi on
ephone-dn 17
number 5577
mwi off
ephone-dn 20
number 5555
name “VM-Port 1”
preference 0
no huntstop
ephone-dn 21
number 5555
name “VM-Port 2”
preference 1
no huntstop
ephone-dn 22
number 5555
name “VM-Port 3”
preference 2
no huntstop
ephone-dn 23
number 5555
name “VM-Port 4”
preference 3
!
ephone 20
vm-device-id “CISCOUM-VI1”
button 1:20
ephone 21
vm-device-id “CISCOUM-VI2”
button 1:21
ephone 22
vm-device-id “CISCOUM-VI3”
button 1:22
ephone 23
vm-device-id “CISCOUM-VI3”
button 1:23
So you can easily see that your config is trying to match the Unity port name and this is done with the command vm-device-id <<string>>. It helps also to register with Unity where you need the deviceId instead of a mac-address.
Recent Comments