[OpenSER-Users] kagoor voiceflow replacement

Ovidiu Sas osas at voipembedded.com
Wed Apr 16 17:37:32 CEST 2008


OpenSER was not designed to act as an upper registrar.
Under certain conditions, it can emulate an upper registrar (with
certain restrictions, of course).
It all depends on the requirements: some tasks can be accomplished,
but others can't.


Regards,
Ovidiu Sas

On Tue, Apr 15, 2008 at 10:11 AM, Jens Thiele <karme at berlios.de> wrote:
> Klaus Darilion <klaus.mailinglists at pernau.at> writes:
>
>  > Gentrice's kaiser schrieb:
>  >> Hi,
>  >>
>  >> The hard part is upper register . It means user auth information is
>  >> stored in Broadsoft instead of your mysql DB.
>  >
>  > If broadsoft supports "Path" then it should be easy by forwarding the
>  > REGISTER to broadsoft and adding a Path header. Further, save() (before
>  > or after forwarding) for NAT pinging.
>
>  1. Path may disclose information you do not want to forward (internal
>    network address)
>
>  2. You probably don't want to forward arbitrary SIP packets into your
>    internal network
>
>
>  > If Path is not supported then it is more complicated (but doable).
>
>  I would say (but please correct me ;-):
>
>  If Path is not supported by your upstream registrar, which is quite
>  likely, then it is much more complicated and at the moment, depending on
>  your security requirements, not doable without modifying openser code.
>
>
>  > You have to save() the original contact and the public socket of the
>  > client. Further you have to rewrite the contact header before
>  > forwarding, so that the URI points to openser. Further, you have to put
>  > some identifier into the user part which will then be used to lookup the
>  > usrloc table. I think this can be done with raw DB queries.
>
>  The problem is that you want to populate your usrloc at least only on
>  successful replies to a register and that IMHO is not possible.
>  Otherwise any client in your network may populate your usrlow without
>  credentials and depending on your setup just grab other users accounts.
>
>  But once more: please correct me - post some example config.
>  My point is: I wasted a lot of time with that and I think it is really
>  bad to make people believe this is easily doable.
>  I ended up using asterisk for this.
>
>  Greetings
>  Jens
>
>  PS: the closest match I did find is milkfish [1] which has IMHO the problem
>  described above.
>  http://www.milkfish.org/
>  http://packages.milkfish.org/boozy/Milkfish_Sources_for_OpenWrt-SDK/OpenWrt-SDK/package/milkfish-sip/files/etc/openser/milkfish_openser.cfg
>
>
>
>  _______________________________________________
>  Users mailing list
>  Users at lists.openser.org
>  http://lists.openser.org/cgi-bin/mailman/listinfo/users
>




More information about the Users mailing list