79753-Cisco - VZB IP Trunking - Guide
79753-Cisco - VZB IP Trunking - Guide
This document details the p rocess to configure Cisco Unified Communications Manager ( UC
Manager to be short - aka CallManager) with Cisco Unified Border Element ( CUBE to be short - aka
IP-to-IP G ateway ) to sup p ort SIP trunking to V eriz on V oIP Serv ices.
CUBE is configured to sup p ort H .323 to SIP interworking for the following reasons:
1 . Sup p ort of G .7 29 through the SIP trunk to V eriz on W ITH SIP Early O ffer sup p ort. Please
note that UC Manager 5 .0 and later does sup p ort SIP trunking with G .7 29 ; howev er, when
Early O ffer is req uired, UC Manager can only sup p ort G .7 1 1 ( µ - or a-law), and Early O ffer is
the V z B defacto standard.
2. Eliminates the use of D SPs on routers for transcoding to reduce cost.
Tested elements:
+ UC Manager: 5 .1 ( 1 a)
+ CUBE: Cisco 38 25 1 2.4 ( 1 1 )T Integrated V oice/V ideo, IPIPG W , TD MIP G W AES F eature Set.
Prior to O ctober 20 0 7 , CUBE was only sup p orted on Integrated V oice/V ideo, IPIPG W ,
TD MIP, G W images. These images hav e “ iv s” in the image names ( e.g., c28 0 0 nm-
ip v oice_ iv s-mz .1 24 -1 5 .T1 .bin). As of O ctober 20 0 7 , CUBE is sup p orted on other IO S
feature sets, starting with IP V oice.
Step 1 . R eq uired media resources. UC Manager uses media resources such as Music on H old
serv ers, conference bridges, transcoders, and media termination p oints. The use of most of these
resources are self ev ident; some are not. Please refer to the following link for more detailed
information on the use of these resources.
http : //www.cisco.com/en/US/p roducts/sw/v oicesw/p s5 5 6 /p roducts_ imp lementation_ design_ guide
_ chap ter0 9 1 8 6 a0 0 8 0 6 37 4 27 .html
In order to p rov ide SIP Early O ffer to V eriz on’ s network with the use of the H .323 p rotocol, H .323
F astStart must be configured on UC Manager, and this req uires a Media Termination Point ( MTP).
An MTP is an entity that accep ts two full dup lex R TP streams. It bridges the media streams
together and allows them to be set up and torn down indep endently . The MTP resource is inv oked
by the H .323 G ateway whenev er a call is routed to it ( v ia the route p attern). UC Manager can act as
the MTP if only G .7 1 1 codec is req uired.
A hardware ( D SP-based) conferencing resource may also be needed. UC Manager can act as a
conferencing resource ( co-resident) but only G .7 1 1 is sup p orted. Since we are using G .7 29 , a
hardware resource ( i.e., IO S D SPs) must be av ailable whenev er a UC Manager p hone inv okes
conferencing.
If music-on-hold is desired, a music resource must be av ailable. More than likely , if the customer
wanted MO H , this resource is already configured. This resource is inv oked by the p hone when the
user p laces the other p arty on H O L D . A tone is used to indicate a call is on hold if MO H is not
configured.
As stated abov e, MTPs are req uired for H .323 F astStart. This resource does not hav e to be D SP-
based and can be j ust Cisco IO S. To make a Cisco IO S MTP resource be av ailable for UC Manager,
the resource must be defined in IO S and register to UC Manager.
voice-ca r d 0
d s p f a r m
d s p s er vices d s p f a r m
Page 1 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Page 2 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
A D SP-based conference resource will be needed if y ou need to sup p ort conferencing with non-
G .7 1 1 codec p arties.
Configuring the conference bridge on a Cisco router with PV D M2 D SPs is detailed abov e in Step
1 a. H owev er, if using older D SPs ( i.e., N M-H D V which uses PV D Ms), then refer to the following
link.
http : //www.cisco.com/en/US/p roducts/sw/v oicesw/p s5 5 6 /p roducts_ configuration_ ex amp le0 9 1 8 6 a0
0 8 0 334 29 4 .shtml# conf
Step 1 c. V erify that the MTP and conference resources registered to UC Manager.
F rom the router’ s p ersp ectiv e, use s h ow s c c p . Below is a samp le. N ote that the op eration state is
A CT I V E and the UC Managers that it is using. The p rotocol between UC Manager and the router is
SCCP. If SCCP is disrup ted between the router and UC Manager, it is recommended that SCCP be
reset on the router ( i.e., use n o s c c p then s c c p in the configuration mode).
cu b e# s ho s ccp
SCCP A d m in St a t e: U P
G a t ew a y I P A d d r es s : 192. 16 8 . 0. 10, P or t N u m b er : 2000
I P P r eced en ce: 5
U s er M a s k ed Cod ec l is t : N on e
Ca l l M a n a g er : 192. 16 8 . 0. 4, P or t N u m b er : 2000
P r ior it y : 1, V er s ion : 5 . 0. 1, I d en t if ier : 5
Ca l l M a n a g er : 192. 16 8 . 0. 6 , P or t N u m b er : 2000
P r ior it y : 2, V er s ion : 5 . 0. 1, I d en t if ier : 2
Sof t w a r e M T P O p er St a t e: A CT I V E - Ca u s e Cod e: N O N E
A ct ive Ca l l M a n a g er : 192. 16 8 . 0. 4, P or t N u m b er : 2000
T CP L in k St a t u s : CO N N E CT E D , P r of il e I d en t if ier : 10
R ep or t ed M a x St r ea m s : 24, R ep or t ed M a x O O S St r ea m s : 0
Page 3 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Step 2. Media R esource G roup ( MR G ) and Media R esource G roup L ist ( MR G L ). In order to use
media resources, they must be p laced into an MR G . MR G s are p laced into MR G L s. An MR G L must
be associated with a dev ice, such as a p hone, gateway or trunk in UC Manager, so that that entity
can use the resources configured and that are av ailable. Please refer to the following link for more
detailed information on MR G and MR G L s.
http : //www.cisco.com/en/US/p roducts/sw/v oicesw/p s5 5 6 /p roducts_ imp lementation_ design_ guide
_ chap ter0 9 1 8 6 a0 0 8 0 6 37 4 27 .html# wp 1 0 9 4 9 9 8
As stated abov e in Step 1 , the MTP resource is inv oked by the H .323 gateway whereas the MO H
and conference resources are inv oked by the p hone. Thus, we need to define two MR G s and p lace
them into two MR G L s. Sp ecifically , the MTP and its associated MR G and MR G L should be
accessible by the H .323 gateway ; and, the conference bridge and MO H resource and their
associated MR G s should be p laced in the MR G L for the UC Manager p hones.
If there are multip le MTP resources, there are two way s to group the resources to control how
they are used.
• Place all the resource ( e.g., IO S software MTP, UC Manager MTP) into the same MR G . UC
Manager will allocate the cap acity of these resources in a round-robin fashion.
• Each resource is p laced into its own MR G . In the case, UC Manager will use a resource
until its cap acity is reached before mov ing to the nex t resource.
Page 4 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
The group ing of resources into MR G s/MR G L s are also used to control how the resources should
be allocated dep ending on location. Please refer to the link abov e for more information.
Page 5 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Then, the final step is to associate the MR G L to the dev ices so that the dev ices can inv oke the
resource when needed.
Page 6 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Similarly , rep eat these step s for the conference and MO H resources and make these resources
av ailable to the p hone.
Page 7 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Page 8 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Step 3. D efine an H .323 G ateway and Select Codec. As stated in the beginning, to achiev e G .7 29
H .323 must be used by UC Manager. Thus, define an H .323 G ateway . The following must be
configured on the G ateway
• The D ev ice N ame is the IP address of the router interface that has been “ binded” to source
H .323. Please refer to the router configuration for more details.
• MR G L must use the p rev iously -configured MR G L with the MTP.
• “ MTP Termination Point R eq uired” must be checked, which is req uired for H .323 F astStart.
• “ W ait for F ar End H .24 5 Terminal Cap ability Set” must be unchecked. This allows media
location information to be sent in the initial call set up messages.
• “ Enable Inbound F astStart” and “ Enable O utbound F astStart” must be checked.
• “ Codec F or O utbound F astStart” should be set to “ G 7 29 ” .
W e will not discuss in detail how UC Manager imp lement Call Admission Control ( CAC). H owev er,
it is imp ortant to note that UC Manager uses two methods for CAC.
• Top ogy un-aware method: Use of locations and regions
• Top ology aware method: Use of R esource R eserv ation Protocol ( R SV P)
Please refer to the following link in the Solution R eference D esign G uide ( SR N D ) for more details.
http : //www.cisco.com/en/US/p roducts/sw/v oicesw/p s5 5 6 /p roducts_ imp lementation_ design_ guide
_ chap ter0 9 1 8 6 a0 0 8 0 6 37 5 f0 .html
It is relev ant to discuss locations and regions briefly here. D ev ices, gateway s, and trunks are
p laced into “ locations” , and locations are defined with audio and v ideo bandwidth limits. R egions
are used to define the codec that should be used between locations. The combination of the two
controls how many calls can trav erse between locations. CAC is critical when remote sites ex ist
and IP trunks are used.
W hen defining an H .323 gateway , it is recommended that it be p laced in a different location and
dev ice p ool from the p hones that will use it to make offnet calls. [ R egions are p laced into D ev ice
Pools and D ev ice Pools are associated with each dev ice.]
Page 9 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Page 10 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Step 4 . R outing Calls. Configure a R oute Pattern that would p oint to the H .323 G ateway for
outbound calls.
A router p attern can p oint directly to the gateway or a route list. A route list is used if y ou hav e
multip le gateway s.
Page 11 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Call treatments such as discard digits and transform masks may change dep ending how V z B
p resent dialed digits to CUBE/UC Manager and what the customer internal dial p lan is. L eav e this
to the customer after discussing the dial p lan with the customer.
W hen multip le gateway s/trunks are av ailable to route calls offnet, route group s and route lists are
used to p rioritiz e and control the usage of these resources. Indiv idual resources are p laced into
route group s and route group s are p laced into route lists.
Please refer to the following link for more detailed information on R oute G roup s and R oute L ists.
http : //www.cisco.com/en/US/p roducts/sw/v oicesw/p s5 5 6 /p roducts_ administration_ guide_ chap ter0
9 1 8 6 a0 0 8 0 8 a8 7 9 7 .html# wp 1 0 4 5 31 1
Configure a R oute G roup and p lace the H .323 G ateway s into the R oute G roup .
Page 12 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
Then, define a R oute L ist and p lace the R oute G roup into the R oute L ist.
Page 13 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
O nce the route list is defined, make sure it has registered to UC Manager; otherwise, it cannot be
used.
Page 14 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
• dial-p eers ( R eq uired): D efine the targets ( i.e., UC Manager and the SIP Serv ice Prov ider)
Page 15 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
• sip -ua ( op tional): Allows customiz ation of the SIP methods ( e.g., retransmissions, target,
etc.).
s ip -u a
r et r y in vit e 2
r et r y b y e 2
r et r y ca n cel 2
r et r y op t ion s 0
s ip -s er ver d n s : a b c. com
g 7 29-a n n ex b over r id e
!I n 12. 4T , Cis co im p l em en t ed a s t r ict com p l ia n ce t o G . 7 29 I E T F s p ecif ica t ion s .
H ow ever , w it h t his im p l em en t a t ion , t her e is n o b a ck w a r d s com p a t ib il it y t o
d evices t ha t a r e n ot in s t r ict com p l ia n ce. T her ef or e, a d d t his com m a n d t o
im p l em en t I O S b eha vior in t he 12. 3 T I O S t r a in .
• call admission control ( op tional): CAC can be configured to limit the concurrent number of
calls sup p orted on a single p latform using total calls, CPU utiliz ation, memory utiliz ation,
IP call cap acity with an H .323 gatekeep er, and max imum connections. More than one
element may be used to p rov ide a more comp rehensiv e CAC result. F or ex amp le, total
calls with CPU and memory utiliz ation can be used together so that the router is not
ov erwhelmed. Thus, either the total concurrent calls or high CPU or high memory
utiliz ation would trigger the router to rej ect the call req uest.
The goal is to p ush the router to its limits and not cause a flap p ing situation.
Page 16 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
• H .225 timers ( op tional): H .225 is the signaling control p rotocol in the H .323 p rotocol suite.
Cisco IO S allows custom configuration of some timers to allow faster communications to
another H .323 endp oint ( UC Manager, in our case). This is highly recommended when
there are more than one UC Manager serv er.
As p rev iously discussed, a dial-p eer is req uired for each UC Manager serv er when the
targets are defined with IPv 4 addresses. W ith the ex cep tion of the IPv 4 address, all other
asp ects of the dial-p eer configuration is ex actly the same; therefore, to set a p reference on
which UC Manager serv er to send a call to, IO S uses the p r ef er en ce command.
There are two different ty p es of timers that are used to redirect a call if the p referred UC
Manager serv er is unav ailable. In order to get the desired behav ior of going from on UC
Manager to another ( i.e., one dial-p eer to another), the H .225 timer should be adj usted
( from the default).
voice cl a s s h3 23 1
!cr ea t e a voice cl a s s t o b e a b l e t o a p p l y t o m u l t ip l e d ia l -p eer s
h225 t im eou t t cp es t a b l is h 3
!w hen t his t im er is s et t o t hr ee s econ d s , t he r ou t er a t t em p t s a con n ect ion t o
t he p r im a r y U C M a n a g er s er ver . I f it d oes n ot r eceive a r es p on s e in t hr ee
s econ d s , it f a l l s b a ck t o t he s econ d a r y U C M a n a g er s er ver .
h225 t im eou t s et u p 3
!t his is t he t im eou t va l u e f or a r es p on s e f or a n ou t g oin g SE T U P m es s a g e.
!
d ia l -p eer voice 205 voip
d es cr ip t ion d ia l -p eer t o U C M a n a g er
p r ef er en ce 5
d es t in a t ion -p a t t er n 1. . .
voice-cl a s s cod ec 1
s es s ion t a r g et ip v4: 192. 16 8 . 0. 6
in com in g ca l l ed -n u m b er .
d t m f -r el a y h245 -a l p ha n u m er ic
voice-cl a s s h3 23 1 !a p p l y t he voice cl a s s t o t he d ia l -p eer
!
d ia l -p eer voice 200 voip
d es cr ip t ion d ia l -p eer t o U C M a n a g er
p r ef er en ce 2
d es t in a t ion -p a t t er n 1. . .
voice-cl a s s cod ec 1
s es s ion t a r g et ip v4: 192. 16 8 . 0. 4
in com in g ca l l ed -n u m b er .
d t m f -r el a y h245 -a l p ha n u m er ic
voice-cl a s s h3 23 1 !a p p l y t he voice cl a s s t o t he d ia l -p eer
A full samp le configuration is below. This configuration has op tional comp onents:
• The router p rov iding D H CP serv er serv ices
• The router p rov iding MTP and Conference bridge serv ices
B u il d in g con f ig u r a t ion . . .
Cu r r en t con f ig u r a t ion : 3 7 43 b y t es
!
ver s ion 12. 4
Page 17 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
s er vice t im es t a m p s d eb u g d a t et im e m s ec
s er vice t im es t a m p s l og d a t et im e m s ec
n o s er vice p a s s w or d -en cr y p t ion
s er vice s eq u en ce-n u m b er s
!
hos t n a m e cu b e
!
b oot -s t a r t -m a r k er
b oot -en d -m a r k er
!
l og g in g b u f f er ed 200000
n o l og g in g con s ol e
en a b l e p a s s w or d x x x x
!
n o a a a n ew -m od el
n o n et w or k -cl ock -p a r t icip a t e s l ot 2
n o n et w or k -cl ock -p a r t icip a t e w ic 0
n o ip d hcp u s e vr f con n ect ed
ip d hcp ex cl u d ed -a d d r es s 192. 16 8 . 0. 0 192. 16 8 . 0. 100
!
ip d hcp p ool I P P H O N E S
n et w or k 192. 16 8 . 0. 0 25 5 . 25 5 . 25 5 . 0
d ef a u l t -r ou t er 192. 16 8 . 0. 10
op t ion 15 0 ip 192. 16 8 . 0. 6
!
ip cef
!
n o ip d om a in l ook u p
ip n a m e-s er ver 16 6 . 3 4. 8 7 . 108
ip n a m e-s er ver 16 6 . 3 4. 8 7 . 49
!
m u l t il in k b u n d l e-n a m e a u t hen t ica t ed
!
voice-ca r d 0
d s p f a r m
d s p s er vices d s p f a r m
!
voice-ca r d 2
d s p f a r m
!
voice s er vice voip
a l l ow -con n ect ion s h3 23 t o s ip
a l l ow -con n ect ion s s ip t o h3 23
h3 23
s ip
b in d con t r ol s ou r ce-in t er f a ce G ig a b it E t her n et 0/ 1
b in d m ed ia s ou r ce-in t er f a ce G ig a b it E t her n et 0/ 1
!
voice cl a s s cod ec 1
cod ec p r ef er en ce 1 g 7 29r 8
cod ec p r ef er en ce 2 g 7 11u l a w
cod ec p r ef er en ce 3 g 7 11a l a w
!
voice cl a s s h3 23 1
h225 t im eou t t cp es t a b l is h 3
h225 t im eou t s et u p 3
!
!
in t er f a ce G ig a b it E t her n et 0/ 0
d es cr ip t ion CU B E in s id e in t er f a ce
ip a d d r es s 192. 16 8 . 0. 10 25 5 . 25 5 . 25 5 . 0
ip vir t u a l -r ea s s em b l y
l oa d -in t er va l 3 0
Page 18 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
d u p l ex ha l f
s p eed a u t o
m ed ia -t y p e r j 45
n o k eep a l ive
h3 23 -g a t ew a y voip b in d s r ca d d r 192. 16 8 . 0. 10
!
in t er f a ce G ig a b it E t her n et 0/ 1
d es cr ip t ion CU B E ou t s id e in t er f a ce
ip a d d r es s 16 6 . 3 8 . 98 . 3 1 25 5 . 25 5 . 25 5 . 0
ip vir t u a l -r ea s s em b l y
l oa d -in t er va l 6 00
d u p l ex a u t o
s p eed a u t o
m ed ia -t y p e r j 45
n o k eep a l ive
!
ip r ou t e 0. 0. 0. 0 0. 0. 0. 0 16 6 . 3 8 . 98 . 1
!
ip ht t p s er ver
n o ip ht t p s ecu r e-s er ver
!
con t r ol -p l a n e
!
ca l l t hr es hol d g l ob a l t ot a l -ca l l s l ow 9 hig h 12
ca l l t hr es hol d g l ob a l cp u -a vg l ow 6 8 hig h 7 5
ca l l t hr es hol d g l ob a l t ot a l -m em l ow 7 5 hig h 8 0
ca l l t r ea t m en t ca u s e-cod e n o-r es ou r ce
ca l l t r ea t m en t on
!
s ccp l oca l G ig a b it E t her n et 0/ 0
s ccp ccm 192. 16 8 . 0. 4 id en t if ier 5 p r ior it y 1 ver s ion 5 . 0. 1
s ccp ccm 192. 16 8 . 0. 6 id en t if ier 2 p r ior it y 2 ver s ion 5 . 0. 1
s ccp
!
s ccp ccm g r ou p 10
a s s ocia t e ccm 5 p r ior it y 1
a s s ocia t e ccm 2 p r ior it y 2
a s s ocia t e p r of il e 12 r eg is t er CO N 001193 48 48 10
a s s ocia t e p r of il e 10 r eg is t er R T P 001193 48 48 10
!
d s p f a r m p r of il e 12 con f er en ce
d es cr ip t ion con f er en ce b r id g e
cod ec g 7 11u l a w
cod ec g 7 11a l a w
cod ec g 7 29a r 8
cod ec g 7 29a b r 8
cod ec g 7 29r 8
cod ec g 7 29b r 8
m a x im u m s es s ion s 10
a s s ocia t e a p p l ica t ion SCCP
!
d s p f a r m p r of il e 10 m t p
cod ec g 7 29r 8
m a x im u m s es s ion s s of t w a r e 12
a s s ocia t e a p p l ica t ion SCCP
!
!
d ia l -p eer voice 100 voip
d es cr ip t ion voip d ia l p eer t o V er iz on
d es t in a t ion -p a t t er n . T
voice-cl a s s cod ec 1
s es s ion p r ot ocol s ip v2
s es s ion t a r g et s ip -s er ver
Page 19 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
in com in g ca l l ed -n u m b er 1. . .
d t m f -r el a y r t p -n t e d ig it -d r op
n o va d
!
d ia l -p eer voice 205 voip
d es cr ip t ion d ia l -p eer t o U C M a n a g er
p r ef er en ce 5
d es t in a t ion -p a t t er n 1. . .
voice-cl a s s cod ec 1
s es s ion t a r g et ip v4: 192. 16 8 . 0. 6
in com in g ca l l ed -n u m b er .
voice-cl a s s h3 23 1
d t m f -r el a y h245 -a l p ha n u m er ic
!
d ia l -p eer voice 200 voip
d es cr ip t ion d ia l -p eer t o U C M a n a g er
p r ef er en ce 2
d es t in a t ion -p a t t er n 1. . .
voice-cl a s s cod ec 1
s es s ion t a r g et ip v4: 192. 16 8 . 0. 4
in com in g ca l l ed -n u m b er .
voice-cl a s s h3 23 1
d t m f -r el a y h245 -a l p ha n u m er ic
!
s ip -u a
r et r y in vit e 2
r et r y b y e 2
r et r y ca n cel 2
r et r y op t ion s 0
s ip -s er ver d n s : a b c. com
g 7 29-a n n ex b over r id e
!
!
!
l in e con 0
ex ec-t im eou t 0 0
s t op b it s 1
l in e a u x 0
s t op b it s 1
l in e vt y 0 4
ex ec-t im eou t 0 0
p a s s w or d x x x x
l og in
!
s ched u l er a l l oca t e 20000 1000
!
en d
Troubleshooting
This document’ s goal is to help identify troublesome/p roblematic areas with some basic
troubleshooting techniq ues for this top ology . This is not meant to be an ex haustiv e resource for
all ty p es of p roblems.
There are four main comp onents in troubleshooting UC Manager SIP trunking with CUBE ( H .323 to
SIP):
Page 20 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
• UC Manager
The only way to see how UC Manager is behav ing is to enable traces on UC Manager.
Analy z ing these traces are best left to Cisco TAC and software dev elop ers. The
recommendation for this p rocess is to make sure the configuration is correct.
Sof t w a r e M T P O p er St a t e: A CT I V E - Ca u s e Cod e: N O N E
A ct ive Ca l l M a n a g er : 192. 16 8 . 0. 4, P or t N u m b er : 2000
T CP L in k St a t u s : CO N N E CT E D , P r of il e I d en t if ier : 10
R ep or t ed M a x St r ea m s : 24, R ep or t ed M a x O O S St r ea m s : 0
!24 s t r ea m s a r e d ou b l e t he con f ig u r ed m a x im u m s es s ion s . T w o M T P r es ou r ces w il l
a l l oca t ed p er ca l l . H ow ever , on l y con f ig u r e m a x im u m s es s ion s t o cor r el a t e w it h
t he n u m b er of ca l l s n eed ed .
Su p p or t ed Cod ec: g 7 29r 8 , M a x im u m P a ck et iz a t ion P er iod : 6 0
Su p p or t ed Cod ec: r f c28 3 3 d t m f , M a x im u mP a ck et iz a t ion P er iod : 3 0
Su p p or t ed Cod ec: r f c28 3 3 p a s s -t hr u , M a x im u m P a ck et iz a t ion P er iod : 3 0
Su p p or t ed Cod ec: in b a n d -d t m f t o r f c28 3 3 con ver s ion , M a x im u m P a ck et iz a t ion
P er iod : 3 0
Page 21 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
H ow UC Manager allocates the MTPs can only be seen on traces. Again, engage Cisco
TAC to help troubleshoot those issues.
If an MTP is not allocated, the result is a SIP delay ed offer ( i.e., IN V ITE without SD P).
o Check to see if the MTP resource is registered on UC Manager.
o Check to see if the router also shows registration to UC Manager
o Make sure the codec configured for the MTP ( on the router) matches the codec that
y ou see in the SIP SD P.
o Make sure the H .323 gateway has been configured p rop erly ( i.e., checks and
unchecks, F astStart codec selection.
o Make sure the MR G L associated to the H .323 gateway contains the MTP resource
configured.
• CUBE H .323
Step 1 . Make sure y ou are matching the dial p eers as designed. There should be two dial
p eers for each call. D ial p eer matching should be deterministic and p redictable. Use d e b u g
v oip d ia l p e e r in ou t . The matched dial p eer determines how y ou call will be treated.
Page 22 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
va l u e H 3 23 _ U s er I n f or m a t ion : : =
{
h3 23 -u u -p d u
{
h3 23 -m es s a g e-b od y s et u p :
{
p r ot ocol I d en t if ier { 0 0 8 225 0 0 5 }
s ou r ceA d d r es s
{
d ia l ed D ig it s : " 1016 " ,
h3 23 -I D : {" 1016 . . . " }
}
s ou r ceI n f o
{
ven d or
{
ven d or
{
t 3 5 Cou n t r y Cod e 18 1
t 3 5 E x t en s ion 0
m a n u f a ct u r er Cod e 18
}
p r od u ct I d ' 43 6 97 3 6 3 6 F 43 6 16 C6 C4D 6 16 E 6 16 7 6 5 7 2' H
ver s ion I d ' 3 1' H
}
t er m in a l
{
}
m c F A L SE
u n d ef in ed N od e F A L SE
}
d es t in a t ion A d d r es s
{
d ia l ed D ig it s : " 5 3 03 5 215 20"
}
a ct iveM C F A L SE
con f er en ceI D ' 8 0D 4D 2945 6 8 6 5 17 003 001101C0A 8 006 C' H
con f er en ceG oa l cr ea t e : N U L L
ca l l T y p e p oin t T oP oin t : N U L L
s ou r ceCa l l Sig n a l A d d r es s ip A d d r es s :
{
ip ' C0A 8 0006 ' H
p or t 17 20
}
ca l l I d en t if ier
{
g u id ' 8 0D 4D 2945 6 8 6 5 17 003 001101C0A 8 006 C' H
}
f a s t S t a r t
Page 23 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
{
' 0000000D 40018 00A 04000100C0A 8 000A 41D 1' H ,
' 40F F F E 06 0401004D 40018 01114000100C0A 8 000A . . . ' H
}
m e d i a W a i t F o r C o n n e c t F A L S E
ca n O ver l a p Sen d F A L SE
m u l t ip l eCa l l s F A L SE
m a in t a in Con n ect ion F A L SE
}
h245 T u n n el in g F A L SE
n on St a n d a r d Con t r ol
{
{
n on St a n d a r d I d en t if ier h221N on St a n d a r d :
{
t 3 5 Cou n t r y Cod e 18 1
t 3 5 E x t en s ion 0
m a n u f a ct u r er Cod e 18
}
d a t a ' 8 0A 4000400010200' H
}
}
}
}
Step 4 . Use d e b u g h 2 4 5 a s n 1 to see the codec offered. Unfortunately , this does not
p rov ide the sp ecific flav or of G .7 29 .
va l u e O p en L og ica l Cha n n el : : =
{
f or w a r d L og ica l Cha n n el N u m b er 1
f or w a r d L og ica l Cha n n el P a r a m et er s
{
d a t a T y p e a u d ioD a t a : g 7 2 9 : 2
m u l t ip l ex P a r a m et er s h225 0L og ica l Cha n n el P a r a m et er s :
{
s es s ion I D 1
m ed ia Con t r ol Cha n n el u n ica s t A d d r es s : iP A d d r es s :
{
n et w or k ' C0A 8 000A ' H
t s a p I d en t if ier 16 8 49
}
}
}
}
• CUBE SIP. Use d e b u g c c s ip m e s s a g e s to see the SIP messages being sent out to
V eriz on.
Page 24 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
v= 0
o= Cis coSy s t em s SI P -G W -U s er A g en t 5 025 1992 I N I P 4 16 6 . 3 8 . 98 . 3 1
s = SI P Ca l l
c= I N I P 4 16 6 . 3 8 . 98 . 3 1
t = 0 0
m = a u d io 18 43 0 R T P / A V P 18 101
c= I N I P 4 16 6 . 3 8 . 98 . 3 1
a = r t p m a p : 18 G 7 29/ 8 000
a = f m t p : 18 a n n ex b = n o
a = r t p m a p : 101 t el ep hon e-even t / 8 000
a = f m t p : 101 0-15
a = p t im e: 20
Page 25 o f 26 R ev 1. Pr ep ar ed b y : V i V u
Configuring and Troubleshooting Cisco UC Manager SIP Trunking with Cisco Unified Border Element
L ast-ditch effort
If y ou are able to get any send or receiv e of SIP message to/from V eriz on, y ou can use the
disconnect cause in the 20 0 O k message ( from d e b u g c c s ip m e s s a g e ) to p oint y ou in the right
direction.
SI P / 2. 0 200 O K
V ia : SI P / 2. 0/ U D P 16 6 . 3 4. 8 4. 8 8 : 5 07 2; b r a n ch= z 9hG 4b K vc0a p 8 3 08 g f hk d cj 7 7 k 1s d s 8 l 1p m 3 . 1
F r om : < s ip : 5 3 03 5 20012@ s chid a n 0017 . ip t r u n k s it 1. g s iv. com > ; t a g = 140213 6 203 -11928 209413 99
T o: < s ip : 1016 @ 16 6 . 3 8 . 98 . 3 1> ; t a g = 3 8 28 8 6 0C-1D E F
D a t e: F r i, 19 O ct 2007 19: 13 : 5 9 G M T
Ca l l -I D : 43 3 C2B F 4-7 D A E 11D C-8 F 08 8 5 22-1445 06 E 5 @ 16 6 . 3 8 . 98 . 3 1
Ser ver : Cis co-SI P G a t ew a y / I O S-12. x
CSeq : 48 3 7 5 8 3 17 B Y E
R ea s on : Q . 8 5 0; ca u s e= 16
Con t en t -L en g t h: 0
The most common disconnect cause is 1 6 , which indicates a normal call clearing condition.
H owev er, 6 5 eq uates to bearer cap ability not imp lemented, which is most likely due to a codec
mismatch.
Page 26 o f 26 R ev 1. Pr ep ar ed b y : V i V u