Hi,
I'm having a bit of trouble getting a hierarchical dial plan to
work with the Cisco MCM gatekeeper.
I want H.323 clients to be able to register with their local
gatekeeper using their H.323 alias and their local extension as
their E.164 number. This is no problem in itself.
But I also want endpoints to be globally reachable via their
complete dial string (not just the extension). The prefixes
pointing to the local gatekeepers are stored on a directory
gatekeeper which will forward lrq queries to the local gatekeeper
to which a particular prefix has been assigned.
An example:
I register my H.323 endpoint to my local gatekeeper with the
E.164 numer 6621. Anyone within the same zone should be able
to dial 6621 and reach me. People outside my local zone would
need to dial 89376621 to reach me by going through the directory
gatekeeper.
Unfortunately I am only able to maintain global reachability if I
register endpoints with the full E.164 string (in the example
this would be 8937 6621).
I seem to need some sort of mechanism on the local gatekeeper to
strip off the prefix, and look clients up by extesion only. Of
course this will only work if each local gatekeeper only handles
one prefix (or the extension would not be unique).
I am not using gateways or proxies, just native H.323 endpoints
that register directly with the gatekeeper, and communicate
directly with each other (or through an MCU).
Has anyone managed to make such a scenario work with Cisco
gatekeepers?
Cheers,
-Dan
PS. This is the configuration that works only when endpoints
register with the full E.164 dial string:
Directory gatekeeper:
gatekeeper
zone local dir-gk net.uni-c.dk 192.168.0.1
zone remote local1-gk uni-c.dk 192.168.1.1 1719
zone remote local2-gk uni-c.dk 192.168.2.1 1719
zone prefix local1-gk 8937*
zone prefix local2-gk 3587*
lrq forward-queries
no use-proxy dir-gk default inbound-to terminal
no use-proxy dir-gk default outbound-from terminal
no shutdown
Local gatekeeper:
gatekeeper
zone local local1-gk uni-c.dk 192.168.1.1
zone remote dir-gk net.uni-c.dk 192.168.0.1 1719
zone prefix local1-gk 8937*
zone prefix dir-gk *
no use-proxy local1-gk default inbound-to terminal
no use-proxy local1-gk default outbound-from terminal
no shutdown
_________________________________________________________________
Dan Mønster, PhD E-mail: Dan.Monster@uni-c.dk
UNI·C, Research Phone: (+45) 8937 6621
Olof Palmes Allé 38 Fax: (+45) 8937 6677
DK-8200 Århus N, Denmark WWW: http://www.uni-c.dk
_________________________________________________________________
I'm having a bit of trouble getting a hierarchical dial plan to
work with the Cisco MCM gatekeeper.
I want H.323 clients to be able to register with their local
gatekeeper using their H.323 alias and their local extension as
their E.164 number. This is no problem in itself.
But I also want endpoints to be globally reachable via their
complete dial string (not just the extension). The prefixes
pointing to the local gatekeepers are stored on a directory
gatekeeper which will forward lrq queries to the local gatekeeper
to which a particular prefix has been assigned.
An example:
I register my H.323 endpoint to my local gatekeeper with the
E.164 numer 6621. Anyone within the same zone should be able
to dial 6621 and reach me. People outside my local zone would
need to dial 89376621 to reach me by going through the directory
gatekeeper.
Unfortunately I am only able to maintain global reachability if I
register endpoints with the full E.164 string (in the example
this would be 8937 6621).
I seem to need some sort of mechanism on the local gatekeeper to
strip off the prefix, and look clients up by extesion only. Of
course this will only work if each local gatekeeper only handles
one prefix (or the extension would not be unique).
I am not using gateways or proxies, just native H.323 endpoints
that register directly with the gatekeeper, and communicate
directly with each other (or through an MCU).
Has anyone managed to make such a scenario work with Cisco
gatekeepers?
Cheers,
-Dan
PS. This is the configuration that works only when endpoints
register with the full E.164 dial string:
Directory gatekeeper:
gatekeeper
zone local dir-gk net.uni-c.dk 192.168.0.1
zone remote local1-gk uni-c.dk 192.168.1.1 1719
zone remote local2-gk uni-c.dk 192.168.2.1 1719
zone prefix local1-gk 8937*
zone prefix local2-gk 3587*
lrq forward-queries
no use-proxy dir-gk default inbound-to terminal
no use-proxy dir-gk default outbound-from terminal
no shutdown
Local gatekeeper:
gatekeeper
zone local local1-gk uni-c.dk 192.168.1.1
zone remote dir-gk net.uni-c.dk 192.168.0.1 1719
zone prefix local1-gk 8937*
zone prefix dir-gk *
no use-proxy local1-gk default inbound-to terminal
no use-proxy local1-gk default outbound-from terminal
no shutdown
_________________________________________________________________
Dan Mønster, PhD E-mail: Dan.Monster@uni-c.dk
UNI·C, Research Phone: (+45) 8937 6621
Olof Palmes Allé 38 Fax: (+45) 8937 6677
DK-8200 Århus N, Denmark WWW: http://www.uni-c.dk
_________________________________________________________________