| Jason Aarons \(US\) 2006-12-28, 7:11 pm |
| If you select use MTP resource it may work (CCMAdmin/Gateway), but this
is bad as it uses MTP resources. I'd only test with it and open a TAC
case.
This is a hairpinned call. I've seen caveats in 12.4T with this
scenario only using Unity to forward back out same H323/PRI.
TAC/Multiservice Voice Team never had a fix and we gave up on the
problem.
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Thursday, December 28, 2006 2:53 PM
To: Wydra, Jason
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Routing calls from PRI inbound MGCP to
outboundMGCP T1 CAS
Calls getting dropped on connect are usually a sign of codec
mismatch. What is the disconnect cause on the PRI side?
-Ryan
On Dec 28, 2006, at 2:32 PM, Wydra, Jason wrote:
Hello - I am trying to place an inbound call into a 2851 using a MGCP
controlled PRI. When this call gets to CCM, I have a translation
pattern that translates the called number to a 4 digit extension on
my legacy IVR. The 4 digit extension is then sent out a H323
controlled T1 CAS trunk on the same 2851. I can see the call go
through when I call the number from my cell phone. It seizes a PRI
channel and a CAS channel. I hear 1 ring from the IVR and then the
call disconnects. I can see on the IVR GUI that a channel is also
seized and it starts to play a greeting. I don't believe the IVR is
hanging up because I lose my connection while I still see the IVR
playing a greeting. Any thoughts on how I can fix this?
Thanks,
Jason
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
|