<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Cisco Call Manager and H323 trunk correction (MTP)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">I posted a couple weeks back about our experiences with H323 trunks on CCM.</FONT>
<BR><FONT SIZE=2 FACE="Arial">As of version 4.0, the Cisco documents state that a 3rd party H323 gateway</FONT>
<BR><FONT SIZE=2 FACE="Arial">requires a Media Termination Point..</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">At the time I said that I have Asterisk working with the ooH323c version of</FONT>
<BR><FONT SIZE=2 FACE="Arial">chan_h323 with out an MTP. I just found that another engineer had been</FONT>
<BR><FONT SIZE=2 FACE="Arial">twiddling with the CCM config, and we were using a MTP.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">I retested chan_h323 without the MTP, and indeed per the Cisco docs,</FONT>
<BR><FONT SIZE=2 FACE="Arial">when a phone connected to CCM puts a call placed through chan_h323 on</FONT>
<BR><FONT SIZE=2 FACE="Arial">hold, the call is disconnected. This IS NOT a bug with asterisk or the</FONT>
<BR><FONT SIZE=2 FACE="Arial">chan_h323, but a known Cisco quirk.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Cisco's own H323 gateways are capable of dynamically creating/connecting</FONT>
<BR><FONT SIZE=2 FACE="Arial">to a MTP. Which permits calls to/through them to allow rtp re-invites and</FONT>
<BR><FONT SIZE=2 FACE="Arial">still preserve a call during media transitions.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">I thought I should post this for the archives in case anyone searching for</FONT>
<BR><FONT SIZE=2 FACE="Arial">details about connecting CCM to Asterisk found my earlier misinformation.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Dan</FONT>
</P>
</BODY>
</HTML>