MMoh via SRST in IOS

Prerequisites 

* SRST router can play MOH file as a multicast to users in the remote site. Unicast MOH is not supported. This saves valuable bandwidth required for streaming MOH over wan.

* The codec used for MOH to remote site (between MOH server's region and Site2) should be g711.

* Only a single MOH source should be used across all phones for this feature to work. (User and Network hold should be same)

* Prevent MOH from reaching branch sites or even crossing wan. Set MMOH hop count to 1 in callmanager.

* Enter a base multicast address (say 239.1.1.1, 16384) in Callmanager. This will be used for g711ulaw. 239.1.1.2 will be used for g711alaw, 239.1.1.3 for g729 and 239.1.1.4 for wideband (as long all these codecs are checked in service parameter and increment by ip address is selected)

Configuration on SRST router

* ccm-manager music-on-hold —- enable multicast moh on ios router

*interface loopback 0, ip address ##1.1.1.1## ##255.255.255.255##  — Configure this so that Pots users will hear multicast moh.

* Configure SRST in the router

    – call-manager-fallback

    - ip source-address ##fastE ip address## port 2000

    – max-ephones , max-dn

    -  moh ##filename## (specifies the moh file – .au or .wav, 8khz, mono)

    – multicast moh 239.1.1.1 port 16384 route ##ipaddress-list##  (if route option is not used, it will use ipaddress used in "ip source-address" command.

    for ex: multicast moh 239.1.1.1 port 16384 route ##fastEipaddress## ##loopbackipaddress##

Enable MOH with g729

Set the MOH service parameter for G729 and G711.

Put MOH server in same region as Site1

Use g729 between Site 1 and Site2/3.

Enable MMOH

a. Enable Multicast option on MOH server. Use increment by IP Address rather than port. (239.x.x.x). Set the hop counts according to how many router hops the packet has to traverse. Also dont forget to enable PIM on routers.

ip multicast-routing

int s0

ip pim sparse-dense-mode

b. Enable multicast option on audio source

c. Enable Multicast option on MRGroup.

d. Apply this group to a MRGList

e. Apply the list to device pools.

f. Reset moh servers.

FXO Caller ID

FXO Caller ID works only with H323 and not with MGCP

Using # in route patterns

# is a valid character in Route patterns. If a route pattern contains # as an intermediate digit, call manager will not consider that to be a digit termination.

MGCP will pass the #(both trailing# and the # in between) to the gateway.

H323 will pass the # in between the numbers to the gateway, but sending the trailing # depends on the Service Parameter “Strip # sign from Called Party Number”.

IOS Transcoding and Conferencing on NM-HDV

1. Copy mac-address of the interface that you want to use to register with Callmanager. (match with sccp local command)

2. Add a new IOS conference bridge with device name "CFBxxxxxxxxxxxx" or a new IOS Transcoder with "MTPxxxxxxxxxxxx".

3. Type the following commands in the router

########Enable DSPfarm services under appropriate slot################

voice-card 1
 dsp services dspfarm

###############Activates dsp farm and sets max number of sessions#################

dspfarm transcoder maximum sessions 4   —- configures max number of conf. sessions (4 transcoding sessions take 1 dsp)
dspfarm confbridge maximum sessions 2  —- configurs max number of transcoding sessions (1 conferencing session take 1 dsp)

dspfarm

sccp local FastEthernet0/0.2  —- specifies a local interface to use to register with callmanager. Use mac-address of this interface.
sccp  —- globally enables SCCP.
sccp ccm 10.1.21.33 priority 1  —- specifies the callmanager with priority of 1. Specify up to 4 callmanagers.

sccp ccm 10.1.21.34 priority 2 —– specify backup callmanager

If the transcoder or Cfb does not register with callmanager,

a. try reset it from callmanager.

b. do a "no sccp" and then do a "sccp" and see if it registers.

Output of "sh sccp"
SITE3-R3#sh sccp
SCCP Admin State: UP
Gateway IP Address: 192.168.221.240
Switchover Method: IMMEDIATE, Switchback Method: GUARD_TIMER
Switchback Guard Timer: 1200 sec, IP Precedence: 5
Max Supported MTP sessions: 0
User Masked Codec list: None
Transcoding Oper State: ACTIVE – Cause Code: NONE
Active Call Manager: 10.1.21.33, Port Number: 2000
TCP Link Status: CONNECTED
Conferencing Oper State: ACTIVE – Cause Code: NONE
Active Call Manager: 10.1.21.33, Port Number: 2000
TCP Link Status: CONNECTED
Call Manager: 10.1.21.33, Port Number: 2000
                Priority: 1, Version: 3.1 or Higher 

Meet me – Issue with using a range

When specifying a range for Meet-me, it gives a fast busy if the user tries to dial a meet me DN that is in use. Say, if the meet me range is 79XX and 7900 is already in use and a user tries to call 7900 it gives a fast busy. The user must know upfront which meet me number is available.

Test conference bridge and transcoder config on 6608

Could not make the 6608 to register successfully with Callmanager. Test this later.

Call transfer between CME and Callmanager

Since CME supports h450.2. h450.3 for transfer and callforward, test how we can setup call transfer and forward between CME and CM.

a. Use hairpin routing

b. Use tandem gateway.

6608 MGCP configuration

To configure a 6608 blade to register with Callmanager, do the following,

a. Log into the 6500 switch and do a sh module to find the slot number in which 6608 is installed

b. Do a "set port voice interface help"

6500# (enable) set port voice interface help
Usage: set port voice interface #mod/port# dhcp enable [vlan #vlan#]
set port voice interface #mod/port# dhcp disable #ipaddrspec#
tftp #ipaddr# [vlan #vlan#]
[gateway #ipaddr#] [dns [ipaddr] [domain_name]]
(ipaddr_spec: #ipaddr# #mask#, or #ipaddr#/#mask#
#mask#: dotted format (255.255.255.0) or number of bits (0..31)
vlan: 1..4094
System DNS will be used if disabling DHCP without DNS parameters)

 For ex:

set port voice interface 7/2 dhcp disable 10.1.1.1/24 vlan #voicevlan# tftp 10.1.1.33 gateway 10.1.1.254 dns 10.1.1.2 cisco.com

or

set port voice interface 7/2 dhcp disable 10.1.1.1 255.255.255.0 vlan #voicevlan# tftp 10.1.1.33 gateway 10.1.1.254 dns 10.1.1.2 cisco.com

 c. Do a sh port <mod/port> and copy the mac-address of the port. Edit this in a notepad, and remove all
"-" (dashes).

 d. Use this mac-address to add a new gateway or add a new conf. bridge or transcoder.

MGCP and Translation rules

Translation rules applied in the dial-peer or voice port does not take effect when using MGCP

Application Dial rules

Applies only when using the IPMA console application and using the speed dials or directory to place calls. For ex: an assistant can dial a number with out prefixing a 9, an app dial rule can be used to prefix a 9, strip a few digits (if wanted) etc.

This does not work from assistant phone.  The following are the only way you can dial

a. You have to drag and drop the number from the speed-dials or directory search window in the console application to the call window in the console.

b. Right click on the speed-dial or directory search window and click Dial option.

App dial rules can be prioritised in a list. Its just like an ACL. If a match is made, it will immediately apply the rules specified in that rule and then routing control goes over to Callmanager (Route patterns, translation patterns) from IPMA.

 

EM and Call restrictions

When setting up EM, do not add partitions for route patterns that are location specific (like 911 or local calls) to the CSS at the EM Device profile. Add the partitions for location specific route patterns to the CSS at the device level.

Attendant Console – Partition issue

Attendant console is not partition aware on 3.3 and 4.1. So if you have overlapping extensions on different partitions, those lines would be grayed out in the attendant console.

This behavior has been modified in CCM 4.2 and 5.0.

Call waiting and Call forward.

Exercise is to set a phone with three lines with same extension.

Line 1 is in partition 1, call forward busy set to Line 2 on CSS 1

Line 2 is in partition 2, call forward busy set to Line 3 on CSS 2

Line 3 is in partition 3.

CSS1 order — partition 2

CSS2 order — partition 3

Make sure call waiting is disabled on lines 1,2,3.

Attendant Console – Service parameters

Allow Routing with Unknown LineState : When this parameter is set to true the calls get routed to a line in the hunt group even if the line state is unknown.
This is a required field.
Default: false.

#### If the phone is not registered, the phones linestate is unknown. AC under default settings, do not route calls if linestate is unknown.
Directory Sync Period : Specify how often you want to do the Directory Synchronization – in hours; 0 means no Directory Synchronization will be done.
This is a required field.
Default: 3. ##### This is the frequency at which sync b/n LSAP directory and attendant console server happens. Unit: hr. Minimum: 0. Maximum: 720. ### Below two parameters are kind of contradictory.

Keep Original CalledParty If Forwarded : If this is set to true, the OriginalCalledParty will not be reset during the redirect if the call is forwarded to Pilot Point.
This is a required field.
Default: true.
Reset Original Called : If the flag is set, it will reset the originalCalledParty during redirect. It can be overwritten by Keep Original CalledParty If Forwarded if call was forwarded to the Pilot Point.
This is a required field.
Default: true

The Original called party will be reset only in the following condition:

Keep Original CalledParty If Forwarded is False and Reset Original Called is True

Attendant Console

Install Attendant console software from Plugins page. 

 a. Configure ac user.

Username has to be exactly “ac”.

Password has to be exactly “12345″ (doesnt matter what pin you use)

b. Configure a pilot point. Select algorithm (first available or longest idle)

c. Configure Hunt group, select a pre-defined pilot point and add members to the hunt group.

d. Associate the pilot point and the phone that attendant console is controlling to “ac” user.

e. Create an attendant console user (username and password). This is used to log into attendant console software.

e. Stop and Start TCD service.

Default algorithms for Load balancing

a. First available member – If the first member is busy, it will hunt to next member.

b. Longest idle – call will be routed to that member who has been idle for longest time.

c. Circular hunt – Set the ACServer.properties file in Cisco callmanager to implement Circular hunting.

 

How to set up Circular Hunt.

Go to C:\Program Files\Cisco\CallmanagerAttendant\etc\ACServer.properties , Open this file in notepad. Contents look like this.

 # Propery file that server uses.

#Jtapi Username
JTAPI_USERNAME=ac

#Jtapi Password
JTAPI_PASSWORD=5e51405d76 (###This password is encrypted, can be cracked using passwordutils.exe from command line. This translates to “12345″)

#Database Access Username
DB_USERNAME=

#Database Access Encrypted Password
DB_PASSWORD=

# Attribute to use for department field in case it is not one of
# the standard ones. The default for DCD & Netscape directories
# is departmentNumber. For Active directory it is ‘department’.
#
# However, if you integrate with a corporate directory and
# use a different attribute to store the department information
# then populate that attribute name here.

DEPARTMENT_ATTRIBUTE=
# Directory paging size to use when generating user lists.
# It default to 500 (1000 being the Active Directories
# default search result size limit).
#
# However, if you integrate with a corporate directory and
# it has an explicit paging size set at less than 500, then
# change the following value to something little smaller than it.

LDAP_PAGING_SIZE=

# Specify comma seperated pilot point device names for which
# circular hunting algorithm is used. This will override
# what is configured in the admin pages.
CIRCULAR_HUNTING_PILOT=ACPilot (### Give the name of the Hunt group Pilot here. This setting overrides the algorithm configured in the pilot configuration page)

 

IPMA with Ext. Mobility

Select Mobile Manager option under User configuration page — Cisco IPMA

 Select the device profile that you want IPMA to control

Set the CSS of Device profile (line setting) to CSS-I-E

Set the partition of Device profile (line setting) to Manager.

Modify the settings under assistant.

IPMA terms

ImmDiv – Immediately divert calls to assistant. (as the call comes in to manager)

Intercept – Forcefully pull the call back that was diverted to assistant or transferred by IPMA (based on manager rules) to assistant. The call can be pulled back only when it is ringing, not after the assistant answered the call.

Assistant Watch on – Manager can see what call the assistant is on.

Div All – Divert all calls to Assistant (no matter what)

DND – Do not disturb mode – Silence the incoming call.

TransfVM – Transfer to Voicemail.

Inclusive filters — Those in the list are the only numbers from which calls will ring the manager's phone

Exclusive filters — Those in the list are the numbers from which calls will ring the assistant;s phone

IPMA – using Wizard

** Install BAT before running IPMA wizard.

** Install IPMA service (Callmanager Serviciability) and Cisco Tomcat service from Control Panel->Services.

** Run IPMA Wizard

** It creates 3 partitions and 2 CSS.

* Associate manager user with manager phone. Configure Cisco IPMA features for Manager user (Intercom line, IPMA monitored line etc). Associate assistants with Manager. Select Mobile manager and UDP (optional)

* Associate assistant user with the manager, select Intercom line, proxy line etc.

* Set Cisco IPMA service parameters (IPMA Route point, Primary CTI manager, Primary IPMA server etc)

* On Manager phones select Cisco IPMA Manager as soft key template.

* On Assistant phones select Cisco IPMA Assistant as soft key template

* Install Assistant Console software from this URL.

 http://##cmipaddress##/ma/Install/IPMAConsoleInstall.jsp

* Access IPMA Manager config URL http://##cmipaddress##/ma/desktop/maLogin.jsp (Login using manager username and pwd)

Service URLs

For extension mobility, http://##cmipaddress##/emapp/EMAppServlet?device=#DEVICENAME#

IPMA Logon service,http://##cmipaddress##/ma/servlet/MAService?cmd=doPhoneService&Name=#DEVICENAME#

IPMA Assistant console URL http://##cmipaddress##/ma/Install/IPMAConsoleInstall.jsp

IPMA Manager config URL http://##cmipaddress##/ma/desktop/maLogin.jsp

IP Phone Agent URL http://192.168.252.44:6293/ipphone/jsp/sciphonexml/IPAgentInitial.jsp

IP Phone Agent Single button login parameters:

Ext

ID

Pwd

Personal Address Book http://##CallManager hostname or IP address##/ccmpd/xmlAddressBookInput.asp

Parameters

UserID – required

UserPIN – required

PreDial – not required

Personal Fast Dial http://##CallManager hostname or IP address##/ccmpd/xmlFastDials.asp

UserID – required

UserPIN – required

PreDial – not required

Extension mobility

By default EM multiple login is not allowed. Enable this in EM service parameters.

a. Create an IP Phone service for EM

 http://##cmipaddress##/emapp/EMAppServlet?device=#DEVICENAME#

Logout and Login services uses same URL.

b. create a UDP (give it same number as user's phone). Subscribe to Logout EM service.

b. create a username. Associate UDP to the user.

c. enable EM on phone. Select logout settings as current settings on phone

d. Subscribe login service on the phone

Alias static

Alias static routing — this exercise helps you to configure static routing for callmanager endpoints on the gatekeeper as a e164 address. 3001,3002, 5001, 5002 are phones registered to callmanager. The following command helps in registering these endpoints as static.

alias static 10.1.21.37 1720 gkid RACK21 gateway voip ras 10.1.21.37 49707 e164 5002 e164 5001 e164 3002 e164 3001
Remember to specify callmanager as a voip gateway and not a terminal.
PSTNSw#sh gatek end
                    GATEKEEPER ENDPOINT REGISTRATION
                    ================================
CallSignalAddr  Port  RASSignalAddr   Port  Zone Name         Type    Flags
————— —– ————— —– ———         —-    —–
10.1.21.36      1720  10.1.21.36      60812 RACK21            TERM
    E164-ID: 6001
10.1.21.37      1720  10.1.21.37      49707 RACK21            VOIP-GW S
    E164-ID: 5002 (static)
    E164-ID: 5001 (static)
    E164-ID: 3002 (static)
    E164-ID: 3001 (static)
    H323-ID: TrunktoGK_1
    Voice Capacity Max.=  Avail.=  Current.= 1
Total number of active registrations = 2

All endpoints show up as static.
 

Gatekeeper Proxy

proxy h323 ##############global mode enables h323 gk proxy.

interface Loopback0
 ip address 3.3.3.3 255.255.255.255 ########use this for proxy’s ip address. Create a loopback.
 h323 interface
 h323 h323-id GKProxy  ############id of h323 proxy
 h323 gatekeeper id BACKBONE ipaddr 172.16.221.2 ######## id and ip of gatekeeper.
 h323 t120 bypass
end

SITE3-R3#
SITE3-R3#
SITE3-R3#sh proxy h323 status

        H.323 Proxy Status
        ==================
    H.323 Proxy Feature: Enabled
    Proxy interface = Loopback0: UP
    Proxy IP address = 3.3.3.3
    Proxy IP port = 11720
    Application Specific Routing: Disabled
    RAS Initialization: Complete
    Proxy aliases configured:
      H323_ID: GKProxy
    Proxy aliases assigned by Gatekeeper:
      H323_ID: GKProxy
    Gatekeeper multicast discovery: Disabled
    Gatekeeper:
        Gatekeeper ID: BACKBONE
        IP address: 172.16.221.2
    Gatekeeper registration succeeded
    T.120 Mode: BYPASS
    RTP Statistics: OFF
    Number of calls in progress: 0

SITE3-R3#
SITE3-R3#sh gatek end
                    GATEKEEPER ENDPOINT REGISTRATION
                    ================================
CallSignalAddr  Port  RASSignalAddr   Port  Zone Name         Type    Flags
————— —– ————— —– ———         —-    —–
3.3.3.3         11720 172.16.221.2    24999 BACKBONE          H323-GW ####### The endpoint type is H323-GW.
    H323-ID: GKProxy ####################################### The proxy shows up as an endpoint in the GK
192.168.121.240 1720  192.168.121.240 54298 BACKBONE          VOIP-GW
Total number of active registrations = 2

SITE3-R3#

 

BACKBONE gatekeepr should be told to use this proxy:
—————————————————

use-proxy BACKBONE remote-zone RACK21 inbound-to gateway
use-proxy BACKBONE remote-zone RACK21 outbound-from gateway

 

SITE3-R3#sh proxy h323 calls
Call unique key = 1
    ConferenceID = [366BC14B2D6211D6804CC3372EFE2C21]
    Calling endpoint call signalling address = 172.16.121.2
    Calling endpoint aliases:
      E164_ID: 6464214003
    Call state = H245 open logical channels
    Time call was initiated = 731029554 ms

 

Disable auto registration of FXS port

To prevent a fxs from not register with gatekeeper.

dial-peer voice 1 pots
no register e164

Restricting bandwidth – Inter and Intra zone

Restricting bandwidth between zones and with in zones

a. bandwidth interzone – specifies bw between one zone A and any other zone (You can specify zone name. Zone can be local or remote zones)
b. bandwidth remote -specifies bw to all remote zones.
c. bandwidth total – interzone + intrazone
d. bandwidth session – to specify bw per session with in a zone (intrazone)

To restrict between RACK21 and BACKBONE  to just 1 call:

bandwidth remote 16 (this applies to all remote zones defined) — -tRINET ADDED 32 (why)

WITH IN A ZONE THAT USES G711, USE 128 AS BANDWIDTTH 

To restrict bandwidth per session inside zone RACK21:

bandwidth session zone RACk21 128 

Callmanager Service Parameter – To update bandwidth automatically.

To update bandwidth automatically from callmanager for each call use service parameter – BRQ enabled – by default its false. Set it to true and restart callmanager service.

Default bandwidth allocated by Gatekeeper

When a call is placed at g711, gatekeeper allocates 128kbps per call.

To change this behaviour use “emulate cisco h323 bandwidth” in gateway mode in
each gateway. This will set the bw to 64 kbps for g711 and 16 for g729.

SITE3-R3#sh gatek calls
Total number of active calls = 1.
                         GATEKEEPER CALL INFO
                         ====================
LocalCallID                        Age(secs)   BW
10-63087                           40          16(Kbps)  ####### g729 call
 Endpt(s): Alias                 E.164Addr
   src EP:                       6464214003
           CallSignalAddr  Port  RASSignalAddr   Port
           192.168.121.240 1720  192.168.121.240 54298
 Endpt(s): Alias                 E.164Addr
   dst EP:                       4083213001
           CallSignalAddr  Port  RASSignalAddr   Port
           10.1.21.37      1720  10.1.21.37      1720

Interzone routing in Gatekeeper

Gatekeeper A
gatekeeper
zone local RACK21 cisco.com 1.1.1.1
no shut
zone remote BACKBONE 172.16.221.2
zone prefix RACK21 646*
zone prefix BACKBONE 408*
gw-type-prefix 1# default-tech

GATEKEEPER B
gatekeeper
zone local BACKBONE cisco.com 172.16.221.2
no shut
zone remote RACK21 1.1.1.1
zone prefix RACK21 646*
zone prefix BACKBONE 408*
gw-type-prefix 1# default-tech

Port used by Callmanager to register with Gatekeeper

Default port used by callmanager is random.
All h323 gateways use port 1720 to register with gatekeeper.
To force callmanager to use 1720, you have to set service parameter “Device Name of GK-controlled Trunk That Will Use Port 1720″

This service parameter should be set with the same name as given to the Trunk to the gatekeeper. (In this ex: TrunktoGK)

Gatekeeper Proxy call flow