Why integrate

Cisco CallManager

and

Asterisk

?

• Features: Asterisk provides features that CallManager by itself does not.
• Migration: Allow a gradual migration from a closed source PBX to open source PBX.

There are two ways to accomplish this:

1. Using H.323: In CCM Asterisk appears as a H.323 Gateway.
2. Using SIP (only in CCM 4.X+):
   1. Open up the CallManager Administration web page.
   2. Since a SIP trunk requires MTP, make sure you have one:
      1. Service -> Media Resource -> Media Termination Point
      2. Normally your CallManager server should appear there if you do an empty query
      3. if not, go to the CallManager Serviceabilty web page, and activate the Cisco IP Voice Media Streaming App service
   3. Select Device->Trunk from the menu.
      
   4. Select the "Add a New Trunk" link from the upper right hand corner of the "Find and List Trunks" page.
      
   5. Select "SIP Trunk" as the "Trunk type" and "SIP" as the "Device Protocol". Click on the "Next" button.
      
   6. Enter a name in the "Device Name". Valid characters are letters, numbers, dashes, dots (periods), and underscores. The device name is only used internally in Call Manager so it can be anything you want.
   7. Enter a description in the "Description" field.
   8. Select a device pool.
   9. Enter the IP address of your Asterisk server in the "Destination Address" field.
   10. Select "UDP" as the "Outgoing Transport Type".
   11. Modify any other settings as needed for your ((CiscoCallManager|CallManager) installation.
   12. Click on the "Insert" button.
   13. Add route patterns in CallManager that send calls to Asterisk using the SIP trunk that you just created.
   14. In sip.conf:

It is important to use "qualify" in sip.conf since

Call Manager

does not support registration for SIP trunks.

Here is a simple example of how to send calls to

Call Manager

in

extensions.conf

:

Cisco Call Manager Express 3.3

CCME can be configured as follows:

Configure a dial-peer pointing to your asterisk server on the CCME 3.3 router:

And configure asterisk exactly the same as above for Call Manager 3.2, except for voicemail to work add:

Into your sip.conf entry.

Cisco Call Manager 6.1

It' very simitar to 4.1, but you must change the UDP protocol of sip in this menu:

System > Security Profile > SIP Trunk Security Profile

Outgoing Transport Type: UDP

Here is the step by step guide for h323 trunk to cisco call manager.

(valid for both for asterisk and trixbox)

First of all do this:

cp /etc/asterisk-1.2.8-samples/ooh323.conf /etc/asterisk

amportal stop

amportal start

Then apply the followings as stated.

A- Here is my working ooh323.conf file;

; Objective System's H323 Configuration example for Asterisk

; ooh323c driver configuration

;

; general section defines global parameters

;

; This is followed by profiles which can be of three types - user/peer/friend

; Name of the user profile should match with the h323id of the user device.

; For peer/friend profiles, host ip address must be provided as "dynamic" is

; not supported as of now.

;

; Syntax for specifying a H323 device in extensions.conf is

For Registered peers/friends profiles

; OOH323/name where name is the name of the peer/friend profile.

;

For unregistered H.323 phones

OOH323/ip:port OR if gk is used OOH323/alias where alias can be any H323

; alias

;

; For dialing into another asterisk peer at a specific exten

; OOH323/exten/peer OR OOH323/exten@ip

;

; Domain name resolution is not yet supported.

;

; When a H.323 user calls into asterisk, his H323ID is matched with the profile

; name and context is determined to route the call

;

; The channel driver will register all global aliases and aliases defined in

; peer profiles with the gatekeeper, if one exists. So, that when someone

; outside our pbx (non-user) calls an extension, gatekeeper will route that

; call to our asterisk box, from where it will be routed as per dial plan.

general

;Define the asetrisk server h323 endpoint

;The port asterisk should listen for incoming H323 connections.

;Default - 1720

port=1720

;The dotted IP address asterisk should listen on for incoming H323

;connections

;Default - tries to find out local ip address on it's own

bindaddr=10.1.23.101

;This parameter indicates whether channel driver should register with

;gatekeeper as a gateway or an endpoint.

;Default - no

gateway=no

;Whether asterisk should use fast-start and tunneling for H323 connections.

;Default - yes

;faststart=no

;h245tunneling=no

;H323-ID to be used for asterisk server

;Default - Asterisk PBX

h323id=ObjSysAsterisk

e164=100

;CallerID to use for calls

;Default - Same as h323id

callerid=asterisk

;Whether this asterisk server will use gatekeeper.

;Default - DISABLE

;gatekeeper = DISCOVER

;gatekeeper = a.b.c.d

gatekeeper = DISABLE

;Location for H323 log file

;Default - /var/log/asterisk/h323_log

;logfile=/var/log/asterisk/h323_log

;Following values apply to all users/peers/friends defined below, unless

;overridden within their client definition

;Sets default context all clients will be placed in.

;Default - default

context=default

;Sets rtptimeout for all clients, unless overridden

;Default - 60 seconds

;rtptimeout=60 ; Terminate call if 60 seconds of no RTP activity

; when we're not on hold

rtptimeout=3

;do not drop this below 3 nor increase much...other wise

;you will not able to call same number again for some time because

;it hangs.Now 3 seconds waiting is needed and it is acceptable.

;Type of Service

;Default - none (lowdelay, thoughput, reliability, mincost, none)

;tos=lowdelay

;amaflags = default

;The account code used by default for all clients.

;accountcode=h3230101

;The codecs to be used for all clients.Only ulaw and gsm supported as of now.

;Default - ulaw

; ONLY ulaw, gsm, g729 and g7231 supported as of now

disallow=all ;Note order of disallow/allow is important.

allow=gsm

allow=ulaw

allow=g729

allow=g723

; dtmf mode to be used by default for all clients. Supports rfc2833, q931keypad

; h245alphanumeric, h245signal.

;Default - rfc 2833

dtmfmode=rfc2833

User/peer/friend definitions

; User config options Peer config options

; ------------------ -------------------

; context

; disallow disallow

; allow allow

; accountcode accountcode

; amaflags amaflags

; dtmfmode dtmfmode

; rtptimeout ip

; port

; h323id

; email

; url

; e164

; rtptimeout

;

;Define users here

;Section header is extension

myuser1

type=user

context=context1

disallow=all

allow=gsm

allow=ulaw

mypeer1

type=peer

context=context2

ip=a.b.c.d ; UPDATE with appropriate ip address

port=1720 ; UPDATE with appropriate port

e164=101

myfriend1

type=friend

context=default

ip=10.0.0.82 ; UPDATE with appropriate ip address

port=1820 ; UPDATE with appropriate port

disallow=all

allow=ulaw

e164=12345

rtptimeout=60

dtmfmode=rfc2833

B-here is the trunk configuration to cisco call manager;

Dial rules:8XXXX

custom dial string:OOH323/$OUTNUM$@10.8.23.5:1720

C-here is outbond routes

Route name:h323trunk

Dial rules:8XXXX

OOH323/$OUTNUM$@10.8.23.5:1720

D-For cisco call manager

first create a h323 gateway with asterisk ip

then create route patern and route to this gateway

be carefull abaout regions codecs because you must allow these codecs in oh323.conf as i stated in the beginning conf file.

Brothers i recommend you update your trixbox to version 1.2.3

as described in update trixbox section in that way your addon versions will be change and you will have more stable h323 trunk in long term.(you will just change addon versions in the upper part.)