[Serusers] Configuring SER to work as SIP proxy
Greger V. Teigre
greger at teigre.com
Tue Jul 24 16:42:05 CEST 2007
forward does what you want, so skip rewritehostport.
g-)
dzus at mat.uni.torun.pl wrote:
> Thanks, this only partialy solved the problem.
>
> What I am looking for is function which can send (forward) message to
> a specified IP:port based on URI but not changing URI itself.
> rewritehostport() and t_relay() unfortunately does it. I have found
> someting like forward() but not know how to use it. What is the
> difference between:
> rewritehostport("192.168.1.2:5060");
> t_relay();
> and
> rewritehostport("192.168.1.2:5060");
> forward(forward(uri:host, uri:port);
> ?
>
> Thanks, Andrzej
>
> Quoting "Greger V. Teigre" <greger at teigre.com>:
>
>
>> Try to just t_relay in loose route...
>>
>> And if that does not work, what type of messages are looped back? 200
>> OKs? ACKs? BYEs?
>> g-)
>>
>> dzus at mat.uni.torun.pl wrote:
>>
>>> All,
>>>
>>> I am trying to configure SER to work as SIP proxy (not registar and
>>> not redirect). I tried to modify simple ser.cfg which comes with
>>> SER by adding one line in route[0]:
>>>
>>> rewritehostport("192.168.1.2:5060");
>>>
>>> This unfortunately doesn't work. The message to my SIP server
>>> 192.168.1.2 are indeed forwarded. But message comming back from
>>> 192.168.1.2 are looped by my SIP proxy (192.168.1.3) back to SIP
>>> server (192.168.1.2).
>>>
>>> Can someone help me? Or send a working cfg for SIP proxy, I cannot find any.
>>>
>>> This is my complete ser.cfg:
>>> #
>>> # $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 andrei Exp $
>>> #
>>> # simple quick-start config script
>>> #
>>>
>>> # ----------- global configuration parameters ------------------------
>>>
>>> #debug=3 # debug level (cmd line: -dddddddddd)
>>> #fork=yes
>>> #log_stderror=no # (cmd line: -E)
>>>
>>> /* Uncomment these lines to enter debugging mode
>>> fork=no
>>> log_stderror=yes
>>> */
>>>
>>> check_via=no # (cmd. line: -v)
>>> dns=no # (cmd. line: -r)
>>> rev_dns=no # (cmd. line: -R)
>>> port=5060
>>> children=4
>>> fifo="/tmp/ser_fifo"
>>>
>>> # ------------------ module loading ----------------------------------
>>>
>>> # Uncomment this if you want to use SQL database
>>> #loadmodule "//lib/ser/modules/mysql.so"
>>>
>>> loadmodule "//lib/ser/modules/sl.so"
>>> loadmodule "//lib/ser/modules/tm.so"
>>> loadmodule "//lib/ser/modules/rr.so"
>>> loadmodule "//lib/ser/modules/maxfwd.so"
>>> loadmodule "//lib/ser/modules/usrloc.so"
>>> loadmodule "//lib/ser/modules/registrar.so"
>>> loadmodule "//lib/ser/modules/textops.so"
>>>
>>> # Uncomment this if you want digest authentication
>>> # mysql.so must be loaded !
>>> #loadmodule "//lib/ser/modules/auth.so"
>>> #loadmodule "//lib/ser/modules/auth_db.so"
>>>
>>> # ----------------- setting module-specific parameters ---------------
>>>
>>> # -- usrloc params --
>>>
>>> modparam("usrloc", "db_mode", 0)
>>>
>>> # Uncomment this if you want to use SQL database
>>> # for persistent storage and comment the previous line
>>> #modparam("usrloc", "db_mode", 2)
>>>
>>> # -- auth params --
>>> # Uncomment if you are using auth module
>>> #
>>> #modparam("auth_db", "calculate_ha1", yes)
>>> #
>>> # If you set "calculate_ha1" parameter to yes (which true in this config),
>>> # uncomment also the following parameter)
>>> #
>>> #modparam("auth_db", "password_column", "password")
>>>
>>> # -- rr params --
>>> # add value to ;lr param to make some broken UAs happy
>>> modparam("rr", "enable_full_lr", 1)
>>>
>>> # ------------------------- request routing logic -------------------
>>>
>>> # main routing logic
>>>
>>> route{
>>>
>>> # initial sanity checks -- messages with
>>> # max_forwards==0, or excessively long requests
>>> if (!mf_process_maxfwd_header("10")) {
>>> sl_send_reply("483","Too Many Hops");
>>> break;
>>> };
>>> if (msg:len >= 2048 ) {
>>> sl_send_reply("513", "Message too big");
>>> break;
>>> };
>>>
>>>
>>> # we record-route all messages -- to make sure that
>>> # subsequent messages will go through our proxy; that's
>>> # particularly good if upstream and downstream entities
>>> # use different transport protocol
>>> if (!method=="REGISTER") record_route();
>>>
>>> # subsequent messages withing a dialog should take the
>>> # path determined by record-routing
>>> if (loose_route()) {
>>> # mark routing logic in request
>>> append_hf("P-hint: rr-enforced\r\n");
>>> route(1);
>>> break;
>>> };
>>>
>>> if (!uri==myself) {
>>> # mark routing logic in request
>>> append_hf("P-hint: outbound\r\n");
>>> route(1);
>>> break;
>>> };
>>>
>>> # if the request is for other domain use UsrLoc
>>> # (in case, it does not work, use the following command
>>> # with proper names and addresses in it)
>>> if (uri==myself) {
>>>
>>> if (method=="REGISTER") {
>>>
>>> # Uncomment this if you want to use digest authentication
>>> # if (!www_authorize("iptel.org", "subscriber")) {
>>> # www_challenge("iptel.org", "0");
>>> # break;
>>> # };
>>>
>>> save("location");
>>> break;
>>> };
>>>
>>> lookup("aliases");
>>> if (!uri==myself) {
>>> append_hf("P-hint: outbound alias\r\n");
>>> route(1);
>>> break;
>>> };
>>>
>>> # native SIP destinations are handled using our USRLOC DB
>>> if (!lookup("location")) {
>>> sl_send_reply("404", "Not Found");
>>> break;
>>> };
>>> };
>>> append_hf("P-hint: usrloc applied\r\n");
>>> route(1);
>>> }
>>>
>>> route[1]
>>> {
>>> # send it out now; use stateful forwarding as it works reliably
>>> # even for UDP2TCP
>>>
>>> # Dzus
>>> rewritehostport("192.168.1.2:5060");
>>>
>>> if (!t_relay()) {
>>> sl_reply_error();
>>> };
>>> }
>>>
>>>
>>>
>>> ----------------------------------------------------------------
>>> This message was sent using IMP, the Internet Messaging Program.
>>>
>>> _______________________________________________
>>> Serusers mailing list
>>> Serusers at lists.iptel.org
>>> http://lists.iptel.org/mailman/listinfo/serusers
>>>
>>>
>>>
>>>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20070724/6720c562/attachment.htm>
More information about the sr-users
mailing list