From: Robert Neil (RNeil@nova-data.com)
Date: Mon Nov 11 2002 - 17:47:16 GMT-3
You could try debug vtsp all and debug vpm all to see how the voice port is
behaving. The port seems to recognize that you have gone offhook and sends
dial tone, but for some reason the dtmf tones are not breaking the dial
tone. It might be a bug in the IOS.
-----Original Message-----
From: Nathan Kleven [mailto:nkleven@intellinet.ws]
Sent: Monday, November 11, 2002 2:50 PM
To: 'Jaroslaw Zak'; 'ccielab@groupstudy.com'
Subject: RE: Voice question
Do you have any "input gain" or "output attenuation" parameters set on the
FXS port? I have seen this issue when the DTMF signals are getting
attenuated to a point where the router does not recognize them.
__________
Nate Kleven
Senior Network Engineer, CCNP Voice Access, MCSE
Expanets
6020 So 190th ST
Kent, WA 98032
(206)219.6135
"Experienced at Networked Solutions"
-----Original Message-----
From: Jaroslaw Zak [mailto:jaroslawz@hotmail.com]
Sent: Wednesday, November 06, 2002 2:59 AM
To: ccielab@groupstudy.com
Subject: Voice question
Hi,
Suppose you have simple case where IP phone is plugged to FXS port of your
router, you have completed standard voice config:
dial-peer voice 1 pots
destination-pattern 111
port 1/0/0
dial-peer voice 2 voip
destination pattern 222
session target...
then when you pick up the hook and try to dial 222 you get constant signal
all the time, even during dialing and of course call is not placed. Any idea
what could that be?
Cheers
Jarek
>From: "Donny MATEO" <donny.mateo@sg.ca-indosuez.com>
>Reply-To: "Donny MATEO" <donny.mateo@sg.ca-indosuez.com>
>To: "Szeto Jeff" <jytszeto@hotmail.com>
>CC: ccielab@groupstudy.com, nobody@groupstudy.com
>Subject: Re: 3550 root guard and loop guard
>Date: Wed, 6 Nov 2002 18:02:27 +0800
>
>Root guard, is used to make sure the port will never become a root
>port. It
>works in such as way
>that if the spanning tree calculation result on the port with the root
>guard configured selected as
>the rootport (meaning a bpdu is received on this interface with higher
>bridge ID), the port is put
>in incosistent state (read as blocked), and the spanning tree will select
>another port as the root
>port.
>
>For loopguard, what it do is to make sure that your Root port and
>alternate
>will never become a
>Designated port for "other" switch.
>So in other words, your switch will never be the switch in the root path
>for others. Imagine if
>you're on access switch and suddenly the uplink of the access switch became
>the Designated port of
>the distribution switch, something must be wrong. Use loopguard to prevent
>this from happening.
>
>That is my understanding, perhaps other can give more.
>Donny
>
>
>
> "Szeto Jeff"
> <jytszeto@hotmail To:
>ccielab@groupstudy.com
> .com> cc:
> Sent by: Subject: 3550 root guard
>and loop guard
> nobody@groupstudy
> .com
>
>
> 06-11-2002 16:45
> Please respond to
> "Szeto Jeff"
>
>
>
>
>
>
>Hi Group,
>
>I am reading the config guide and do not clear about the root and loop
>guard.
>
>Why root guard prevent the remote switch that connecting to the local
>switch
>from becoming the root?
>The following, about the loop guard, is copied from the guide:
>"You can use loop guard to prevent alternate or root ports from becoming
>designated ports because of a failure that leads to a unidirectional link"
>Actually, what the loop guard do?
>
>Thank you in advance.
>
>Jeff
>
>_________________________________________________________________
>Tired of spam? Get advanced junk mail protection with MSN 8.
>http://join.msn.com/?page=features/junkmail
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:22:56 GMT-3