Re: can I map a "number" for an unregistered endpoint?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jan,

Thanks for the info!  yes I only want to remove the dialed prefix, and "myMCU=out=11=" mentioned in your email works very well and now I can handle any length of room-passcode now Thanks a lot !! 

Regards,
Bo




>Hi,
>do you really want to convert the digits to Post-Dial-Digits (DTMF) ?

>If you only want to remove the dialed prefix, a simple rule to match all
>lengths would be

>[RasSrv::GWRewriteE164]
>myMCU=out=11=

>Regards,
>Jan


On Thu, Sep 15, 2016 at 11:54 AM, Bo Xu <boxuscience@xxxxxxxxx> wrote:
Hi Jan,

Thanks for the info!  yes I added GWRewriteE164 into my gk.ini according to the document you mentioned as the following:
[RasSrv::PermanentEndpoints]
10.4.34.36:1720=myMCU;11
[RasSrv::GWRewriteE164]
myMCU=out=11III=PPP
and now when I dial "GnuGN-IP##11567" then I can join the room-567 Thanks!

I just have a question for the syntax of "I and P":  now I only can match the fixed width of call number, for example: 
if I define "myMCU=out=11III=PPP",        then I can join 3-digits room like 567
if I define "myMCU=out=11IIIII=PPPPP",  then I can join 5-digits room like 56789
but if I define them together like "myMCU=out=11III=PPP, myMCU=out=11IIIII=PPPPP", it seems only the first (3-digit) can call OK, but the second (5-digit) cannot call

could you tell me if I can define a rule to match any digit-width call? because sometime users will define a 3-digit room like 567, sometimes they will define 5-digit room like 56789, can I just set one rule of GWRewriteE164 to macth different digit-width room-passcode (i.e., math 567 and 56789 at same time) ? Thanks!

Regards,
Bo






Think of the special characters as wildcards:
"0.7" means "prefix 007 and prefix 017 and prefix 027...".

If you want to rewrite the destination number before it is sent out by GnuGk,
check out the [RasSrv::GWRewriteE164] section and add an out rule for your MCU.

See http://www.gnugk.org/gnugk-manual-6.html#ss6.4

Regards,
Jan

-- 
Jan Willamowius, Founder of the GNU Gatekeeper Project
EMail  : jan@...
Website: http://www.gnugk.org
Support: http://www.willamowius.com/gnugk-support.html

Relaxed Communications GmbH
Frahmredder 91
22393 Hamburg
Geschäftsführer: Jan Willamowius
HRB 125261 (Amtsgericht Hamburg)
USt-IdNr: DE286003584

On Thu, Sep 15, 2016 at 10:07 AM, Bo Xu <boxuscience@xxxxxxxxx> wrote:

in 7.3 Section [RasSrv::PermanentEndpoints] I find the following:

...
Special characters . and ! can be used with prefixes here to match any digit and disable the prefix

Example:
For gateway,
10.0.1.5=MyGW;009,008:=2,0.7:=3
...

can I use "." and "!" to remove the prefix?  could you tell me the meaning of  "0.7" in above example Thanks!

Thanks,
Bo





On Thu, Sep 15, 2016 at 9:43 AM, Bo Xu <boxuscience@xxxxxxxxx> wrote:

I just have a question:  can I set the perm-Alias so GnuGK will automatically remove the prefix when routing the call? for example:

I config a perm-Alias as the following:
[RasSrv::PermanentEndpoints]
10.4.34.32:1720=myMCU;111

and in myMCU there is a conference-room whose passcode is 111567, now if I call GnuGK-IP##111567 it join the room successfully

my question is: if in myMCU there is a conference-room whose passcode is 567, now if I call GnuGK-IP##111567, can GnuGK help me remove prefix "111", and join the 567-room?

I just want to know if it is possible to let the room-passcode doesn't have to include the prefix, because sometimes the conference-room is created by users and they might not know the prefix I set for myMCU

Thanks for you help!
Bo








On Wed, Sep 14, 2016 at 12:18 PM, Bo Xu <boxuscience@xxxxxxxxx> wrote:
Hi Robert,

Thanks for the info!  yes I updated my gatekeeper.ini as yours and now I can call the unregistered-EP with perm-Alias or Rewrite-W164 successfully!  the following is my new config:

[RasSrv::PermanentEndpoints]
10.4.34.32:1720=MCU1;5006

[RasSrv::RewriteE164]
222=5006

the reason I can not call before is because I thought 5006 is the Alias itself but it actually is Prefix (i.e., 5006 is the room-passcode of my MCU, not that MCU itself),  after I updated my config as yours now I can directly join the conference-room with "GnuGK-IP##5006" or GnuGK-IP##222". 

also just want to let you know that I tested the calls from both registered/unregistered Polycom-PVX, they all can call successfully as the following:
from unregistered Polycom-PVX:   GnuGK-IP##5006 or GnuGK-IP##222
from registered Polycom-PVX:       directly call 5006 or 222 is fine,    (also call GnuGK-IP##5006 or GnuGK-IP##222 same as the above registered case)

Thanks for your help!
Bo







>That sounds very similar.  Here is what I did with both of the IP's being
>external.

>I'm not sure if it matters, but this is with polycom HDX's and QDX's being
>registered.  Calling 999 (basically 1016) then hits a remote Lifesize unit.

>[RasSrv::PermanentEndpoints]
>1.2.3.4=COMPANY_X;1016
>4.3.2.1=COMANY_Z;4444

>[RasSrv::RewriteE164]
>; internal
>999=1016
>; another test
>998=1016
>;
>997=4444



On Wed, Sep 14, 2016 at 10:08 AM, Bo Xu <boxuscience@xxxxxxxxx> wrote:

Hi Robert,

Thanks for the info! yes our case is same as yours and the following is our details:

epA registers on GnuGK with alias 8
epB(10.4.34.32) doesn't registers on GnuGK, I set perm-Alias 5006 for it as the following:
[RasSrv::PermanentEndpoints]
10.4.34.32:1720=5006

now with Polycom-PVX:
I can call epA with GnuGK-IP##8
but I cannot call epB with GnuGK-IP##5006

from your email can I add E164-RewriteE164 in gk.ini so I can call "##5006"? could you tell me if the following is right?
[RasSrv::RewriteE164]
111=5006

then after adding E164-RewriteE164 can I call epB with GnuGK-IP##111?  

Thanks for your time!
Bo




>When I get back to a computer I'll post what I did, maybe that will help.
>Essentially I want our registered polycom units to call an unregistered
>device at another location/company. The catch is to do it via a 3 digit
>number so I used e164 rewriting.
>Eg: 999 == 1.2.3.4##1016 (The perm alias)
>999 and 1016 both work.
>998 is a room on a Polycom mcu at a different company, and so on..



On Tue, Sep 13, 2016 at 3:38 PM, Bo Xu <boxuscience@xxxxxxxxx> wrote:

I also tested Polycom-HDX6000 and AVer-HVC110, they are same with Polycom-PVX as the following:
they all can use GnuGK-IP##registered-Alias to call a registered-terminals
they cannot use GnuGK-IP##permanent-Alias to call an unregistered-terminals (already set permanent-Alias for them in GnuGK)

in our application we want to use the above "##"-syntax to call both registered/unregistered terminals, could you tell me if it is possible? do I need to set some parameters for that? or could you tell me which part of the source code causes this difference of registered-Alias and permanent-Alias? is that possible to do a little bit modify of the source code so we can use "##"-syntax to call both registered/unregistered terminals? Thanks!

Regards,
Bo






On Tue, Sep 13, 2016 at 2:12 PM, Bo Xu <boxuscience@xxxxxxxxx> wrote:

sorry I forgot to  introduce that the terminal I am using is Polycom-PVX(8.0.16),  when I try to call GnuGK-IP##permanent-Alias, then wireshark shows the folowing:
got admissionConfirm
then terminal send out setup-message,  in this setup-message, Called Party Number in Q.931 is the permanent-Alias, and this permanent-Alias is also in H.225's destinationAddress's dialledDigits
the calll is not successful; if I change it to "GnuGK-IP##active-register-Alias", then the call is successful.

do I need to set some parameters in gatekeeper.ini so I can call both register-Alias and permanent-Alias with "##"? Thanks!

Regards,
Bo






On Tue, Sep 13, 2016 at 9:49 AM, Bo Xu <boxuscience@xxxxxxxxx> wrote:
Hi Sergey,

Thanks for the info!    yes alias@IP and IP##alias are implemented by different vendors, my question is about how to use them in GnuGK for permanent-Alias and registered-Alias, i.e:

I can use "GnuGK-IP##registered-Alias" to call a terminal which is registered to GnuGK
but I cannot use "GnuGK-IP##permanent-Alias" to call a terminal which is not registered to GnuGK but I set a permanent-Alias for it (but I can use permanent-Alias@GnuGK-IP to call it)

because I want to use "GnuGK-IP##Alias" to call both registered-Alias and permanent-Alias Thanks!

Regards,
Bo





Hi Bo!

I think there is some misunderstanding: the "aaa@..." and "bbb##aaa" 
notations are the same thing, implemented by different vendors.

For example: to call "aaa" on "bbb" from Cisco codec, I should use 
"aaa@..." form and to call the same device on the same gatekeeper I'm 
using "bbb##aaa" form for Sony codecs.

If you want I can attach my configuration.

Kind regards, Sergey.

Tune-IT Logo
Sergey.Zhmylove@...
12.09.2016 23:33, Bo Xu пишет:
> Hi Jan,
>
> I can call a permanent-Alias with the following "@" command:
> permanent-Alias@...
>
> also I can call a register-Alias(a terminal who registered to my 
> GnuGK) with the following "##" command:
> GnuGKIP##registered-Alias
>
> but I cannot call permanent-Alias with the above "##" command,  cold 
> you tell me how I can call a permanent-Alias with "##" like 
> "GnuGKIP##permanent-Alias"? Thanks!
>
>
> Regards,
> Bo
>


On Mon, Sep 12, 2016 at 4:33 PM, Bo Xu <boxuscience@xxxxxxxxx> wrote:
Hi Jan,

I can call a permanent-Alias with the following "@" command:
permanent-Alias@GnuGKIP

also I can call a register-Alias(a terminal who registered to my GnuGK) with the following "##" command:
GnuGKIP##registered-Alias

but I cannot call permanent-Alias with the above "##" command,  cold you tell me how I can call a permanent-Alias with "##" like "GnuGKIP##permanent-Alias"? Thanks!


Regards,
Bo



On Wed, Aug 31, 2016 at 1:25 PM, Bo Xu <boxuscience@xxxxxxxxx> wrote:
Hi Jan,

yes I added "[RasSrv::PermanentEndpoints]" you mentioned into my gatekeeper.ini and it works fine now, Thanks a lot!

Regards,
Bo





Hi Bo,

GnuGk calls those endpoints that don't actively register "permanent
endpoints":

[RasSrv::PermanentEndpoints]
10.1.11.116=8000

Regards,
Jan

-- 
Jan Willamowius, Founder of the GNU Gatekeeper Project
EMail  : jan@...
Website: http://www.gnugk.org
Support: http://www.willamowius.com/gnugk-support.html

Relaxed Communications GmbH
Frahmredder 91
22393 Hamburg
Geschäftsführer: Jan Willamowius
HRB 125261 (Amtsgericht Hamburg)
USt-IdNr: DE286003584

Bo Xu wrote:
> Hi,
> 
> if I have a endpoint whose IP is 10.1.11.116, but it is not registered to
> my GnuGK, in this case, can I set the gatekeeper.ini so GnuGK can "map"
> that endpoint's IP(10.1.11.116) to an "number"(for example 8000), then
> later on when I want to call that endpoint I will call GnuGK like
> "GnuGKIP##8000"?
> 
> can I do the above with GnuGK? or I must register that endpoint to GnuGK
> then after that I can call it with "GnuGKIP##Alias"? Thanks!
> 
> Regards,
> Bo Xu













------------------------------------------------------------------------------
_______________________________________________________

Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users
Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux