<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Robert,<br>
<br>
>From a colleague:<br>
<br>
<quote><br>
GW should just pass the bearer-cap from the incoming leg to the
outgoing leg for pri-pri scenario. I have a similar setup in my lab
using BRI - PRI.<br>
<br>
Couple of things to try :<br>
<br>
1) If we remove the translation-profile from the voice-ports, do we see
the "unrestricted digital" bearer-cap in the outgoing isdn setup?<br>
<br>
2) we enable the following debugs and collect the output for a failure
call in order to see where bearer-cap is lost :<br>
<br>
no logging console<br>
no logging mon<br>
logging buffered 5000000 debug<br>
<br>
debug voip ccapi inout<br>
debug voice translation<br>
debug isdn q931<br>
debug cdapi event<br>
debug cdapi detail<br>
debug voip tsp default<br>
<br>
sh ver<br>
sh run<br>
sh log<br>
</quote><br>
<br>
/Wes<br>
<br>
On Wednesday, August 18, 2010 10:07:28 AM, Robert Kulagowski
<a class="moz-txt-link-rfc2396E" href="mailto:rkulagow@gmail.com"><rkulagow@gmail.com></a> wrote:<br>
<blockquote
cite="mid:AANLkTinq7uFwM_iemp4KeXHtoDEfz4bZfkr-A1O4_-4G@mail.gmail.com"
type="cite">
<pre wrap="">On Tue, Aug 17, 2010 at 4:45 PM, Wes Sisk <a class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">In that case the router may modify the bearer cap. You may need to use the
new video PRI features in ISR's.
<a class="moz-txt-link-freetext" href="http://www.cisco.com/en/US/docs/ios/12_4t/12_4t11/h320gw.html#wp1234629">http://www.cisco.com/en/US/docs/ios/12_4t/12_4t11/h320gw.html#wp1234629</a>
</pre>
</blockquote>
<pre wrap=""><!---->
That doesn't work. I've got probably 7 or 8 TAC cases over the past 3
years (basically since day Feature+1) trying to get this to work, and
it never does. TAC guys that I've worked with are great, but when
they ask me to change H.225 parameters on the endpoints that's when I
know that it's not ready for primetime. (None of our endpoints have
any knobs that can be tweaked for that sort of stuff, and they "just
work" when they connect using either native ISDN or Codian 3241s,
so...)
</pre>
<blockquote type="cite">
<pre wrap="">Otherwise, you may have applied the workaround for CUVA calls not working
which forces the bearer cap?
<a class="moz-txt-link-freetext" href="http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080569b65.shtml#topic2">http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080569b65.shtml#topic2</a>
</pre>
</blockquote>
<pre wrap=""><!---->
Nope, not that:
voice-port 0/1/0:23
translation-profile incoming Prepend_Sitecode
no comfort-noise
!
voice-port 0/2/0:23
translation-profile incoming Prepend_Sitecode
no comfort-noise
!
voice-port 0/3/0:15
!
voice-port 2/0/0
!
0/3/0 is the cross-over PRI to the equipment, and it's showing a
correct bearer channel of Unrestricted Digital. Both 0/1/0 and 0/2/0
make the call Speech on the outbound leg.
</pre>
</blockquote>
<br>
</body>
</html>