<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-7" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000066">
<font face="Times New Roman">Try the command:<br>
<i> network-clock-select 1 BRI x/x/x</i><br>
<br>
also, make sure that you can call using <br>
<i>isdn test call interface brix/x/x <number></i><br>
<br>
if you can, then issue also the command:<br>
<i><br>
no dial-peer outbound status-check pots</i><br>
<br>
</font><br>
Lemon wrote:
<blockquote
cite="mid:94e031d30808120631s620f8674jb39beb28998fada6@mail.gmail.com"
type="cite">
<pre wrap="">hi,
On Tue, Aug 12, 2008 at 2:26 PM, Dustin S. Fowler
<a class="moz-txt-link-rfc2396E" href="mailto:dustin.s.fowler@gmail.com"><dustin.s.fowler@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Lemon,
This is most likely a physical problem. Possibly on the carriers end. It is
also one of the questions on the TUC exam.
</pre>
</blockquote>
<pre wrap=""><!---->
thanks, we suspected that but telco claims it is fine. also this was
working fine untill yesterday when we started to set it up as h323
gateway. and now customer is leaning towards telco saying it can't be
that. *sigh*
thnx
charl
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</body>
</html>