|
Home > Archive > Voice over IP Cisco > November 2007 > Pinging 6608 gateways ...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Pinging 6608 gateways ...
|
|
| Biffle, Gerrad 2007-11-07, 1:11 pm |
| Hoping someone currently running 6608 PRI cards can help verify
something for me. Are you able to ping your 6608 ports when they show a
"connected" state? This is when they are registered with the
CallManager, D-channel is up and everything is running as it should. We
do notreceive a reply while the port is "connected". If the port is
"enabled" (meaning it is built with no cable plugged in - and not
registeredwith CallManager) - we receive a reply to our ping. We also
receive a reply when pinging our ports setup for HW Conferencing - these
also show an "enabled" state.
If anyone is running 6608's and don't mind giving them a ping - I would
be interested to see if you receive the same thing.
Thanks in advance for the help.
========================================
===============
Please note that email sent to and from this address is subject
to the North Carolina Public Records Law and may be disclosed to
third parties.
| |
| Lelio Fulgenzi 2007-11-07, 1:11 pm |
| Pinging 6608 gateways ...I can ping connected ports no problem.
You might want to check ACLs, etc. Try pinging from the gateway of the device.
----- Original Message -----
From: Biffle, Gerrad
To: cisco-voip@puck.nether.net
Sent: Wednesday, November 07, 2007 9:32 AM
Subject: [cisco-voip] Pinging 6608 gateways ...
Hoping someone currently running 6608 PRI cards can help verify something for me. Are you able to ping your 6608 ports when they show a "connected" state? This is when they are registered with the CallManager, D-channel is up and everything is running as it should. We do not receive a reply while the port is "connected". If the port is "enabled" (meaning it is built with no cable plugged in - and not registered with CallManager) - we receive a reply to our ping. We also receive a reply when pinging our ports setup for HW Conferencing - these also show an "enabled" state.
If anyone is running 6608's and don't mind giving them a ping - I would be interested to see if you receive the same thing.
Thanks in advance for the help.
========================================
===============
Please note that email sent to and from this address is subject
to the North Carolina Public Records Law and may be disclosed to
third parties.
------------------------------------------------------------------------------
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Bill Simon 2007-11-07, 1:11 pm |
| Interesting, I can only ping the supervisor card, not the PRI ports...
Lelio Fulgenzi wrote:
> I can ping connected ports no problem.
> =
> You might want to check ACLs, etc. Try pinging from the gateway of the =
> device.
> =
> =
> ----- Original Message -----
> *From:* Biffle, Gerrad <mailto:Gerrad.Biffle@greensboro-nc.gov>
> *To:* cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> *Sent:* Wednesday, November 07, 2007 9:32 AM
> *Subject:* [cisco-voip] Pinging 6608 gateways ...
> =
> Hoping someone currently running 6608 PRI cards can help verify
> something for me. Are you able to ping your 6608 ports when they
> show a =93connected=94 state? This is when they are registered with =
the
> CallManager, D-channel is up and everything is running as it
> should. We do not receive a reply while the port is =93connected=94. =
> If the port is =93enabled=94 (meaning it is built with no cable plugg=
ed
> in =96 and not registered with CallManager) =96 we receive a reply to
> our ping. We also receive a reply when pinging our ports setup for
> HW Conferencing =96 these also show an =93enabled=94 state.
> =
> If anyone is running 6608=92s and don=92t mind giving them a ping =96=
I
> would be interested to see if you receive the same thing.
> =
> Thanks in advance for the help.
> =
> =
> =
> =
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
> Please note that email sent to and from this address is subject =
> to the North Carolina Public Records Law and may be disclosed to =
> third parties.
> =
> ---------------------------------------------------------------------=
---
> =
> ________________________________________
_______
> 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
-- =
Bill Simon - bills@psu.edu - (814) 865-2270
http://tns.its.psu.edu/
| |
| Keith Klevenski 2007-11-07, 1:11 pm |
| I'm able to ping all of my ports with PRIs and conference bridges no
problem.
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Biffle, Gerrad
Sent: Wednesday, November 07, 2007 8:33 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Pinging 6608 gateways ...
Hoping someone currently running 6608 PRI cards can help verify
something for me. Are you able to ping your 6608 ports when they show a
"connected" state? This is when they are registered with the
CallManager, D-channel is up and everything is running as it should. We
do not receive a reply while the port is "connected". If the port is
"enabled" (meaning it is built with no cable plugged in - and not
registered with CallManager) - we receive a reply to our ping. We also
receive a reply when pinging our ports setup for HW Conferencing - these
also show an "enabled" state.
If anyone is running 6608's and don't mind giving them a ping - I would
be interested to see if you receive the same thing.
Thanks in advance for the help.
========================================
===============
Please note that email sent to and from this address is subject
to the North Carolina Public Records Law and may be disclosed to
third parties.
|
|
|
|
|