I have an interesting one here that I can't seem to work around.

Lets say CallManager goes down but the gatekeepers stay up.  The remote
sites will go into SRST and register to the local gateway.  The gateway
will then register its phones as e164 address to the gatekeeper.

The problem is that once the phones come out of SRST, the gatekeeper now
has these e164 address registered to the gatekeeper and it causes problems
with call routing.

I don't see any way under call-manager-fallback to tell the gateway to not
register its ephones with the gatekeeper.  You can add no-reg after the
dialplan command but the actual ephone dn's themselves will still register
with the gatekeeper.

I have tried adding the command "no rrq dynamic-prefixes-accept" to the
gatekeeper but they still register to the gateekeper.

**This is SRST, not CME so I can't add no-reg after the ephone
configuratio because these ephones are dynamic with SRST.

tia,

Andrew B. Dignan, CCIE Voice #16528

[ Post a follow-up to this message ]

Hey Andy
How about "security e164" under the GK config? I've
not set it up but I was reading about it a few months
back and if I remember correctly it sounds like it
might be what you're looking for? Just a thought.

Ted


--- Andrew Dignan <cisco@dignans.com> wrote:

> I have an interesting one here that I can't seem to
> work around.
>
> Lets say CallManager goes down but the gatekeepers
> stay up.  The remote
> sites will go into SRST and register to the local
> gateway.  The gateway
> will then register its phones as e164 address to the
> gatekeeper.
>
> The problem is that once the phones come out of
> SRST, the gatekeeper now
> has these e164 address registered to the gatekeeper
> and it causes problems
> with call routing.
>
> I don't see any way under call-manager-fallback to
> tell the gateway to not
> register its ephones with the gatekeeper.  You can
> add no-reg after the
> dialplan command but the actual ephone dn's
> themselves will still register
> with the gatekeeper.
>
> I have tried adding the command "no rrq
> dynamic-prefixes-accept" to the
> gatekeeper but they still register to the
> gateekeper.
>
> **This is SRST, not CME so I can't add no-reg after
> the ephone
> configuratio because these ephones are dynamic with
> SRST.
>
> tia,
>
> Andrew B. Dignan, CCIE Voice #16528
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>


 ________________________________________
__________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[ Post a follow-up to this message ]

Turned out to be a bug...I thought it was strange that I had never run
into this before:

------------------------------------------------------------
CSCsd69027
Externally found moderate defect: Resolved (R)
SRST does not Unregisters E164 number from Gatekeeper when CCM comes up

Release Notes:

Description:
When CCM is available again and IP Phone unregisteres from SRST, the SRST
router does not unregisters the E164 number from Gatekeeper.

This issue has been seen in 12.4(3a) and 12.4(5a), but not on 12.3(8)T6

Workaround:
Use 12.3(8)T6

------------------------------------------------------------

Andy

> Hey Andy
> How about "security e164" under the GK config? I've
> not set it up but I was reading about it a few months
> back and if I remember correctly it sounds like it
> might be what you're looking for? Just a thought.
>
> Ted
>
>
> --- Andrew Dignan <cisco@dignans.com> wrote:
> 
>
>
>  ________________________________________
__________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>

[ Post a follow-up to this message ]