E.164 assignment through Radius

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

 



The latest cvs 2.0.7 contains code to assign endpoint
aliases from a Radius server.
This feature works with RadAuth/RadAliasAuth modules
and returns a possibly modified list of aliases in RCF messages.

As with other Radius features, this one is optional. Read docs/radauth.txt
to see how it should be enabled. Basically it is triggered by Cisco-AVPair "h323-ivr-in=..."
attribute in Access-Accept.

Remarks:
This feature should be used with care - it may appear that not all endpoints
support alias reassignemt through RCF message.
The H.323/H.225.0 standard states that endpoints should overwrite its aliases
send in RRQ with the ones received in RCF, so well behaved endpoints should
work fine with this feature.
I've tested it with OpenH323 stack based soft phones (like ohphone, for example)
and it works perfect.

When the alias reassignment may be considered useful:
1. To configure fixed E.164 number for registering endpoints.
    Example: I am registering with alias 'zvision' and receiving addition alias '48586259732'.
2. To totally configure endpoint aliases based on its IP or something else.
    Example: Endpoint registering from 192.168.1.1 always receives aliases 'zvision','48586259732'.

---
Michal Zygmuntowicz


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
List: Openh323gk-users@lists.sourceforge.net
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/

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

  Powered by Linux