Re: Re: Re: Rewriting E164 numbers after GW selection

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

 



When u will include in 2.2 beta ,i need it in extreme emergency
Regards,

________________
Engr. Rafat Subhan
Software Developer
Advanced Communications
House no 423 F-11/3
Islamabad
mail: rafat@advcomm.net
MSN: qudrat2210@hotmail.com
Cell : +92-300-5195822
http://www.advcomm.net

----- Original Message -----
From: "Jan Willamowius" <jan@willamowius.de>
To: <openh323gk-users@lists.sourceforge.net>
Cc: <Ian.Campbell@band-x.com>
Sent: Thursday, January 22, 2004 4:39 PM
Subject: Re:  Re: Re: Rewriting E164 numbers after GW
selection


> Hi,
>
> I had a chance to talk to Michal in person on the OpenSource Telephony
> Summit and we decided that we want to be strict on the feature freeze
> for the 2.0.x branch. We must get 2.2 out and all new 2.0 features stand
> in the way of that.
>
> I would suggest implementing this rewriting into 2.2 now, and then do a
> backport to 2.0 after it has been proven stable in 2.2.
>
> Regards,
> Jan
>
> Ian.Campbell@band-x.com wrote:
> > Hello All,
> > I have finally got round to implementing per gateway E164 number
> > rewriting as discussed in this thread in early November. Attached is a
> > patch providing it for version 2.0.6. The code provides triple stage
> > rewriting:
> >
> > per gw input E164 rewriting -> standard E164 rewriting -> (endpoint
> > selection) -> per gw output E164 rewriting
> >
> > This is configured in a new configuration section as follows:
> >
> > [RasSrv::GWRewriteE164]
> > foo=out=1223=2323
> > foo=out=13=4444
> > foo=in=777=8888
> > bar=in=777=9999
> >
> > And so on. The first element in the line is the GW that the rule is
> > being applied to the second the direction (whether it is applied
> > before the standard rewriting and the endpoint selection or after) and
> > finally the rule itself in the same as the standard rewriting
> > ([RasSrv::RewriteE164]). All this allows much more sophisticated
> > control of what is sent to the endpoint for example an authentication
> > prefix and per endpoint routing policies to be constructed. The code
> > has been tested by me, but should probably be considered alpha quality
> > for now.
> >
> > Jan et al. is there anything I need to do (beyond applying this to the
> > 2.2 CVS archive) to get this included in a future release?
> >
> > Regards,
> >
> > Ian Campbell
> > Band-X Ltd.
>
> --
> Jan Willamowius, jan@willamowius.de, http://www.willamowius.de/
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> List: Openh323gk-users@lists.sourceforge.net
> Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
> Homepage: http://www.gnugk.org/



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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