sr-users March 2008

sr-users@lists.kamailio.org

169 participants
237 discussions

[OpenSER-Users] automatically generated aliases with usrloc and ldap

by Lukasz Stelmach

Greetings All. I have managed to set up OpenSER with LDAP authentication. Now I would like it to create memory cached aliases each time a user registers. I do not wan to use any persistent storage because I have it already it is my LDAP directory. However, I would like OpenSER to cache those aliases as doing ldap lookup for every message does not look too apealing to me. Let me explain how I see it: if (is_method("REGISTER")) { if(is_present_hf("Proxy-Authorization")) { if (!ldap_search("ldap://sipaccounts/ou=dept,o=TELMARK,c=PL?uid,mail,uidNumber,userPassword?one?(uid=$f)) { #error handling } ldap_result("uid/$avp(s:username)"); ldap_result("userPassword/$avp(s:password)"); ldap_result("mail/$avp(s:longalias)"); ldap_result("uidNumber/$avp(s:numalias)"); if(pv_proxy_authorize("telmark")) { proxy_challenge("telmark", "1"); exit; } } else { proxy_challenge("telmark", "1"); exit; } if(!save("location")) sl_reply_error(); # And here the big thing! } What to do to make save("aliases"); (called twice) save uidNumber and mail (without @domain, these are transformations, I know) as aliases in usrloc? PS. Please cc answers I am not a subscriber. -- Best regards, >Łukasz<

16 years, 1 month

Re: [OpenSER-Users] Carrierroute... Do I almost have it???

by Douglas Garstang

Ovidiu, Ok, so now it's routing but it's not selecting the carrier by matching the source IP address in the subscriber table against the IP address of the incoming INVITE. Is that even possible? If it's not possible, how do I have a different routing table for each OpenSER system? I was going to use my carrier as my OpenSER instance.... that would have worked... I have these tables... mysql> select * from carrierroute; +----+---------+-------------+--------+------+-------+--------------+----------------+----------------+---------+ | id | carrier | scan_prefix | domain | prob | strip | rewrite_host | rewrite_prefix | rewrite_suffix | comment | +----+---------+-------------+--------+------+-------+--------------+----------------+----------------+---------+ | 1 | 0 | | 1 | 1 | 0 | 200.1.1.1 | | | NULL | | 4 | 0 | | 2 | 1 | 0 | 200.1.1.2 | | | NULL | | 5 | 0 | | 3 | 1 | 0 | 200.1.1.3 | | | NULL | | 9 | 1 | | 1 | 1 | 0 | 100.1.1.1 | | | NULL | | 10 | 1 | | 2 | 1 | 0 | 100.1.1.2 | | | NULL | | 11 | 1 | | 3 | 1 | 0 | 100.1.1.3 | | | NULL | +----+---------+-------------+--------+------+-------+--------------+----------------+----------------+---------+ 6 rows in set (0.00 sec) mysql> select * from route_tree; +----+-----------+ | id | carrier | +----+-----------+ | 1 | Hong Kong | | 0 | default | | 2 | San Jose | +----+-----------+ mysql> select username, domain, cr_preferred_carrier from subscriber; +----------+----------------+----------------------+ | username | domain | cr_preferred_carrier | +----------+----------------+----------------------+ | | 192.168.255.53 | 2 | | | 192.168.1.240 | 1 | +----------+----------------+----------------------+ ----- Original Message ---- From: Ovidiu Sas <osas(a)voipembedded.com> To: Douglas Garstang <dougmig33(a)yahoo.com> Cc: Henning Westerholt <henning.westerholt(a)1und1.de>; users(a)lists.openser.org Sent: Wednesday, March 26, 2008 6:56:15 AM Subject: Re: [OpenSER-Users] Carrierroute... Do I almost have it??? On Wed, Mar 26, 2008 at 2:31 AM, Douglas Garstang <dougmig33(a)yahoo.com> wrote: > > >I am using this module in production with more then 400k routes loaded > >for 8 different providers and it is working like a charm. > >As Henning mentioned, the interface is a little bit cumbersome but usable. > >You can put all the carriers under the same table and prioritize the > >gateway based on domains. Like tis you don't need to hardcode > >anything in the config file. > > > >Carrierroute was designed to deal with a big amount of routing rules > >and it is doing an amazing job. > >LCR was designed to deal with a limited number of routes/gateways but > >it has a different level of flexibility and a more mature interface. > > > >Carrierroute is a brand new module and for sure it will improve in > >flexibility as times go by (just like the lcr did along releases). > > Ovidiu (or anyone else....) > > I think I may almost have it..... If I treat all routes as being in the same > carrier, I can just use cr_rewrite_uri("1","call_id"), and then > cr_rewrite_uri("2","call_id") in failure_route[1] and > cr_rewrite_uri("2","call_id") in failure_route[2], correct? I tested this > and it seems to work. I guess it's up to me then to populate the > rewrite_host column with a gateway belonging to the cheapest carrier for > domain 1, the a gateway from the next cheapest carrier for domain 2 and so > on. Still sound right? finally you got it ;) > Here's where it gets a bit tricky. We have OpenSER running in 6 different > locations. The gateways we use will differ for each location (we always want > to use the closest gateway belonging to a carrier). So, I figured I could > use the 'user' functionality in carrierroute to do this. I could simply put > the domain (IP address) in the domain column, leave the user blank (we don't > have users... calls are forwarded from asterisk), and then associate a > carrier in the cr_preferred_carrier column. You can see all that in my > subscriber table below. > > Doesn't seem to work though. When routing a call, OpenSER complains that it > can't find a default carrier, and then because it seems not to match the > incoming call against an entry in the subscriber table, it can't find a > carrier to use, and fails the call. add a 'default' carrier into the route_tree table > So... how would I be able to use the source IP address of the asterisk box > that sends the calls to OpenSER in the subscriber table so that I could have > different routing entries for each OpenSER system??? > > Here's my db tables... > > > mysql> select * from route_tree; > +----+-----------+ > | id | carrier | > +----+-----------+ > | 1 | Hong Kong | > | 0 | San Jose | > +----+-----------+ > > mysql> select * from carrierroute order by carrier, scan_prefix, domain; > +----+---------+-------------+--------+------+-------+--------------+----------------+----------------+---------+ > | id | carrier | scan_prefix | domain | prob | strip | rewrite_host | > rewrite_prefix | rewrite_suffix | comment | > +----+---------+-------------+--------+------+-------+--------------+----------------+----------------+---------+ > | 1 | 0 | | 1 | 1 | 0 | 200.1.1.1 | > | | NULL | > | 4 | 0 | | 2 | 1 | 0 | 200.1.1.2 | > | | NULL | > | 5 | 0 | | 3 | 1 | 0 | 200.1.1.3 | > | | NULL | > | 9 | 1 | | 1 | 1 | 0 | 100.1.1.1 | > | | NULL | > | 10 | 1 | | 2 | 1 | 0 | 100.1.1.2 | > | | NULL | > | 11 | 1 | | 3 | 1 | 0 | 100.1.1.3 | > | | NULL | > +----+---------+-------------+--------+------+-------+--------------+----------------+----------------+---------+ > > mysql> select id, username, domain, cr_preferred_carrier from subscriber; > +----+----------+----------------+----------------------+ > | id | username | domain | cr_preferred_carrier | > +----+----------+----------------+----------------------+ > | 1 | | 192.168.255.53 | 0 | > | 2 | | 192.168.255.54 | 1 | > +----+----------+----------------+----------------------+ > > > > > > > ________________________________ > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now. ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

16 years, 1 month

[Serusers] [SPAM] Re: pls. help me on my installation

by Martin Hoffmann

Spam detection software, running on the system "h1063274.serverkompetenz.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: ram wrote: > On Mon, Mar 24, 2008 at 3:32 PM, Allan Jardinel <ajardinel2002(a)yahoo.com> > wrote: > > > I'm using ubuntu 7.10 and install ser 0.9.7 and rtp, after the > > installation i test and it can call both users, when i try to restart the > > computer xten can not register anymore so i check the settings and its ok. > > but when i check the /var/run/ser.pid there is no file, also the > > /tmp/ser_fifo has no file so restart the ser using the /etc/ser restart or > > force-reload but still pid and fifo has no file. pls. help me to solve this > > problem.... > > > > > Hi > > you try run manuall with > > ser -c -f config file > > see you see any errrors [...] Content analysis details: (2.3 points, 2.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.3 MAILTO_TO_SPAM_ADDR URI: Includes a link to a likely spammer email 2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [80.218.12.224 listed in dnsbl.sorbs.net]

16 years, 1 month

Re: [OpenSER-Users] To-tag of 200 for CANCEL

by Andreas Granig

Corrected list address. Andreas Granig wrote: > Hi Bogdan, > > Yes, and I also read some older discussions about this topic like > http://www.ietf.org/mail-archive/web/sipping/current/msg03071.html but > still I'm quite uneasy regarding the phrasing in RFC3261 saying "that > the To tag of the response to the CANCEL and the To tag in the response > to the original request SHOULD be the same". It doesn't clearly state to > which response it refers - the final 487 for the INVITE or maybe to > possible 180/183 (although I understand the consequences and > implications of parallel forking etc.). > > I currently don't have a trace available, but is the To-tag in the 200 > to the CANCEL really the same as the To-tag in 487 to the INVITE, as the > RFC suggests, or is the 487 just passed through? > > Andreas > > Bogdan-Andrei Iancu wrote: >> Hi Andreas, >> >> Have you went through this: >> >> http://sourceforge.net/tracker/index.php?func=detail&aid=1818469&group_id=1… >> >> There is also a reference to a discussion (on the topic) on sip >> implementers list. >> >> Regards, >> Bogdan >> >> Andreas Granig wrote: >>> Hi, >>> >>> Actually, someone pointed out a previous discussion about that issue. >>> Interesting read. >>> http://www.openser.org/pipermail/users/2007-October/014049.html >>> >>> Andreas >>> >>> Andreas Granig wrote: >>>> Hi, >>>> >>>> One more question regarding the CANCEL processing: >>>> >>>> RFC says in §9.2 regarding the 200 for a CANCEL: >>>> >>>> #+ >>>> This response is >>>> constructed following the procedures described in Section 8.2.6 >>>> noting that the To tag of the response to the CANCEL and the To tag >>>> in the response to the original request SHOULD be the same. >>>> #- >>>> >>>> OpenSER (1.3.1) on the other hand does generate a different To-tag >>>> and doesn't use the one from the response of the original request. >>>> Why is that? Anything we can do about this? >>>> >>>> Best regards, >>>> Andreas >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)lists.openser.org >>>> http://lists.openser.org/cgi-bin/mailman/listinfo/users >>> >> >

16 years, 1 month

Re: [OpenSER-Users] Carrierroute... Do I almost have it???

by Douglas Garstang

>I am using this module in production with more then 400k routes loaded >for 8 different providers and it is working like a charm. >As Henning mentioned, the interface is a little bit cumbersome but usable. >You can put all the carriers under the same table and prioritize the >gateway based on domains. Like tis you don't need to hardcode >anything in the config file. > >Carrierroute was designed to deal with a big amount of routing rules >and it is doing an amazing job. >LCR was designed to deal with a limited number of routes/gateways but >it has a different level of flexibility and a more mature interface. > >Carrierroute is a brand new module and for sure it will improve in >flexibility as times go by (just like the lcr did along releases). Ovidiu (or anyone else....) I think I may almost have it..... If I treat all routes as being in the same carrier, I can just use cr_rewrite_uri("1","call_id"), and then cr_rewrite_uri("2","call_id") in failure_route[1] and cr_rewrite_uri("2","call_id") in failure_route[2], correct? I tested this and it seems to work. I guess it's up to me then to populate the rewrite_host column with a gateway belonging to the cheapest carrier for domain 1, the a gateway from the next cheapest carrier for domain 2 and so on. Still sound right? Here's where it gets a bit tricky. We have OpenSER running in 6 different locations. The gateways we use will differ for each location (we always want to use the closest gateway belonging to a carrier). So, I figured I could use the 'user' functionality in carrierroute to do this. I could simply put the domain (IP address) in the domain column, leave the user blank (we don't have users... calls are forwarded from asterisk), and then associate a carrier in the cr_preferred_carrier column. You can see all that in my subscriber table below. Doesn't seem to work though. When routing a call, OpenSER complains that it can't find a default carrier, and then because it seems not to match the incoming call against an entry in the subscriber table, it can't find a carrier to use, and fails the call. So... how would I be able to use the source IP address of the asterisk box that sends the calls to OpenSER in the subscriber table so that I could have different routing entries for each OpenSER system??? Here's my db tables... mysql> select * from route_tree; +----+-----------+ | id | carrier | +----+-----------+ | 1 | Hong Kong | | 0 | San Jose | +----+-----------+ mysql> select * from carrierroute order by carrier, scan_prefix, domain; +----+---------+-------------+--------+------+-------+--------------+----------------+----------------+---------+ | id | carrier | scan_prefix | domain | prob | strip | rewrite_host | rewrite_prefix | rewrite_suffix | comment | +----+---------+-------------+--------+------+-------+--------------+----------------+----------------+---------+ | 1 | 0 | | 1 | 1 | 0 | 200.1.1.1 | | | NULL | | 4 | 0 | | 2 | 1 | 0 | 200.1.1.2 | | | NULL | | 5 | 0 | | 3 | 1 | 0 | 200.1.1.3 | | | NULL | | 9 | 1 | | 1 | 1 | 0 | 100.1.1.1 | | | NULL | | 10 | 1 | | 2 | 1 | 0 | 100.1.1.2 | | | NULL | | 11 | 1 | | 3 | 1 | 0 | 100.1.1.3 | | | NULL | +----+---------+-------------+--------+------+-------+--------------+----------------+----------------+---------+ mysql> select id, username, domain, cr_preferred_carrier from subscriber; +----+----------+----------------+----------------------+ | id | username | domain | cr_preferred_carrier | +----+----------+----------------+----------------------+ | 1 | | 192.168.255.53 | 0 | | 2 | | 192.168.255.54 | 1 | +----+----------+----------------+----------------------+ ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

16 years, 1 month

[OpenSER-Users] To-tag of 200 for CANCEL

by Andreas Granig

Hi, One more question regarding the CANCEL processing: RFC says in §9.2 regarding the 200 for a CANCEL: #+ This response is constructed following the procedures described in Section 8.2.6 noting that the To tag of the response to the CANCEL and the To tag in the response to the original request SHOULD be the same. #- OpenSER (1.3.1) on the other hand does generate a different To-tag and doesn't use the one from the response of the original request. Why is that? Anything we can do about this? Best regards, Andreas

16 years, 1 month

[OpenSER-Users] UA Cant Connect To TLS

by Ali Jawad

Hi All My UA cant connect to tls on my openser server, as per logs everything seems fine ..I don't know why it disconnects in the end ..the log is http://java.pastebin.ca/948774 My TLS settings are /* uncomment the following lines to enable TLS support (default off) */ #disable_tls = yes disable_tls = no listen = tls:xx.xx.x.xx.x tls_verify_server = 1 tls_verify_client = 1 tls_require_client_certificate = 0 tls_method = TLSv1 #tls_certificate = "/usr/local/eyeball/license/cert.pem" #tls_private_key = "/usr/local/eyeball/license/privkey.pem" #tls_ca_list = "/usr/local/eyeball/license/splendor3.crtpvk.pem" tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem" tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem" tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem" #port=5060 /* uncomment and configure the following line if you want openser to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:87.236.144.13:5060 #listen=tcp:87.236.144.12:5060 sip_warning=yes

16 years, 1 month

Re: [OpenSER-Users] OpenSER sending 483: Too many Hops

by Bogdan-Andrei Iancu

Marcio, you need the following line: alias=""spo.voip.br" Right now you have only: alias=""vmw02-src.spo.voip.br" Regards, Bogdan Marcio wrote: > Thanks Bogdan..but didn't work....I set the > "alias"(alias="vmw02-src.spo.voip.br <http://vmw02-src.spo.voip.br> > <http://vmw02-src.spo.voip.br>" into "openser.cfg" and it`s > ok...passed in "vmw02-srv~#openser -c" but with the parameter "listen" > didn't accept....(listen=udp:192.168.0.10:5060 > <http://192.168.0.10:5060> < http://192.168.0.10:5060>) > > regards > Marcio > > > 2008/3/25, Bogdan-Andrei Iancu <bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro>>: > > Hi Marcio, > > Try setting spo.voip.br <http://spo.voip.br> <http://spo.voip.br> > as alias in your cfg. > > Regards, > Bogdan > > Marcio wrote: > > Hi, > > > > If anybody can take a look openser.cfg below. I`m working vmware > > (enviroments virtual)...Whenever I try a "register" a client I get > > 483: Too many Hops....as if he had a loop (config file) but I am > > unable to find the problem... > > > > I use OpenSER 1.3-notls, client softphone: twincle or xlite... > > > > OpenSER - 192.168.0.10 <http://192.168.0.10> <http://192.168.0.10> > > Client - 192.168.0.25 <http://192.168.0.25> <http://192.168.0.25> > > > > Bind9/named.conf(SRV, A): spo.voip.br <http://spo.voip.br> > <http://spo.voip.br> > > > > > > Does anyone know how to fix this ? > > > > Any hints.....?? > > > > thx... > > > > > > > > *OpenSER File:* > > ** > > > > ####### Global Parameters ######### > > > > alias="vmw02-srv.spo.voip.br <http://vmw02-srv.spo.voip.br> > <http://vmw02-srv.spo.voip.br>" > > > > debug=6 > > > > log_stderror=no > > > > log_facility=LOG_LOCAL0 > > > > log_name="Openser" > > > > fork=yes > > > > children=8 > > > > tcp_children=4 > > > > group="openser" > > > > user="openser" > > > > /* uncomment the following lines to enable debugging */ > > > > #debug=6 > > > > #fork=no > > > > #log_stderror=yes > > > > /* uncomment the next line to disable TCP (default on) */ > > > > disable_tcp=yes > > > > /* uncomment the next line to enable the auto temporary > blacklisting of > > > > not available destinations (default disabled) */ > > > > #disable_dns_blacklist=no > > > > /* uncomment the next line to enable IPv6 lookup after IPv4 dns > > > > lookup failures (default disabled) */ > > > > #dns_try_ipv6=yes > > > > /* uncomment the next line to disable the auto discovery of > local aliases > > > > based on revers DNS on IPs (default on) */ > > > > #auto_aliases=no > > > > /* uncomment the following lines to enable TLS support (default > off) */ > > > > #disable_tls = no > > > > #listen = tls:your_IP:5061 > > > > #tls_verify_server = 1 > > > > #tls_verify_client = 1 > > > > #tls_require_client_certificate = 0 > > > > #tls_method = TLSv1 > > > > #tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem" > > > > #tls_private_key = > "/usr/local/etc/openser/tls/user/user-privkey.pem" > > > > #tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem" > > > > > > > > port=5060 > > > > /* uncomment and configure the following line if you want openser to > > > > bind on a specific interface/port/proto (default bind on all > available) */ > > > > #listen=udp:192.168.1.2:5060 <http://192.168.1.2:5060> > <http://192.168.1.2:5060> > > > > listen=udp:192.168.0.10:5060 <http://192.168.0.10:5060> > <http://192.168.0.10:5060> > > > > > > > > ####### Modules Section ######## > > > > #set module path > > > > mpath="/usr/local/lib/openser/modules/" > > > > /* uncomment next line for MySQL DB support */ > > > > loadmodule "mysql.so" > > > > loadmodule "sl.so" > > > > loadmodule "tm.so" > > > > loadmodule "rr.so" > > > > loadmodule "maxfwd.so" > > > > modparam("maxfwd", "max_limit", 256) > > > > loadmodule "usrloc.so" > > > > loadmodule "registrar.so" > > > > loadmodule "textops.so" > > > > loadmodule "mi_fifo.so" > > > > loadmodule "uri_db.so" > > > > loadmodule "uri.so" > > > > loadmodule "xlog.so" > > > > loadmodule "acc.so" > > > > loadmodule "avpops.so" > > > > /* uncomment next lines for MySQL based authentication support > > > > NOTE: a DB (like mysql) module must be also loaded */ > > > > loadmodule "auth.so" > > > > loadmodule "auth_db.so" > > > > /* uncomment next line for aliases support > > > > NOTE: a DB (like mysql) module must be also loaded */ > > > > loadmodule "alias_db.so" > > > > /* uncomment next line for multi-domain support > > > > NOTE: a DB (like mysql) module must be also loaded > > > > NOTE: be sure and enable multi-domain support in all used modules > > > > (see "multi-module params" section ) */ > > > > loadmodule "domain.so" > > > > /* uncomment the next two lines for presence server support > > > > NOTE: a DB (like mysql) module must be also loaded */ > > > > #loadmodule "presence.so" > > > > #loadmodule "presence_xml.so" > > > > > > > > # ----------------- setting module-specific parameters > --------------- > > > > > > > > # ----- mi_fifo params ----- > > > > modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo") > > > > > > > > # ----- rr params ----- > > > > # add value to ;lr param to cope with most of the UAs > > > > modparam("rr", "enable_full_lr", 1) > > > > # do not append from tag to the RR (no need for this script) > > > > #modparam("rr", "append_fromtag", 0) > > > > > > > > # ----- rr params ----- > > > > #modparam("registrar", "method_filtering", 1) > > > > /* uncomment the next line to disable parallel forking via > location */ > > > > # modparam("registrar", "append_branches", 0) > > > > /* uncomment the next line not to allow more than 10 contacts > per AOR */ > > > > #modparam("registrar", "max_contacts", 10) > > > > > > > > # ----- uri_db params ----- > > > > /* by default we disable the DB support in the module as we do > not need it > > > > in this configuration */ > > > > modparam("uri_db", "use_uri_table", 0) > > > > modparam("uri_db", "db_url", "") > > > > > > > > # ----- acc params ----- > > > > /* what sepcial events should be accounted ? */ > > > > modparam("acc", "early_media", 1) > > > > modparam("acc", "report_ack", 1) > > > > modparam("acc", "report_cancels", 1) > > > > /* by default ww do not adjust the direct of the sequential > requests. > > > > if you enable this parameter, be sure the enable "append_fromtag" > > > > in "rr" module */ > > > > modparam("acc", "detect_direction", 0) > > > > /* account triggers (flags) */ > > > > modparam("acc", "failed_transaction_flag", 3) > > > > modparam("acc", "log_flag", 1) > > > > modparam("acc", "log_missed_flag", 2) > > > > /* uncomment the following lines to enable DB accounting also */ > > > > modparam("acc", "db_flag", 1) > > > > modparam("acc", "db_missed_flag", 2) > > > > > > > > # ----- usrloc params ----- > > > > #modparam("usrloc", "db_mode", 0) > > > > /* uncomment the following lines if you want to enable DB > persistency > > > > for location entries */ > > > > modparam("usrloc", "db_mode", 2) > > > > modparam("usrloc", "db_url", > > "mysql://openser:openserrw@192.168.0.10/openser") > > > > modparam("usrloc", "user_column", "username") > > > > modparam("usrloc", "domain_column", "domain") > > > > modparam("usrloc", "contact_column", "contact") > > > > modparam("usrloc", "expires_column", "expires") > > > > modparam("usrloc", "q_column", "q") > > > > modparam("usrloc", "callid_column", "callid") > > > > modparam("usrloc", "cseq_column", "cseq") > > > > modparam("usrloc", "methods_column", "methods") > > > > modparam("usrloc", "flags_column", "flags") > > > > modparam("usrloc", "user_agent_column", "user_agent") > > > > modparam("usrloc", "received_column", "received") > > > > modparam("usrloc", "socket_column", "socket") > > > > modparam("usrloc", "use_domain", 0) > > > > modparam("usrloc", "desc_time_order", 0) > > > > modparam("usrloc", "timer_interval", 60) > > > > modparam("usrloc", "matching_mode", 0) > > > > modparam("usrloc", "cseq_delay", 20) > > > > # ----- auth_db params ----- > > > > /* uncomment the following lines if you want to enable the DB based > > > > authentication */ > > > > #modparam("auth_db", "calculate_ha1", yes) > > > > #modparam("auth_db", "password_column", "password") > > > > modparam("auth_db", "db_url", > > "mysql://openser:openserrw@192.168.0.10/openser") > > > > #modparam("auth_db", "load_credentials", "") > > > > > > > > # ----- alias_db params ----- > > > > /* uncomment the following lines if you want to enable the DB based > > > > aliases */ > > > > modparam("alias_db", "db_url", > > "mysql://openser:openserrw@192.168.0.10/openser") > > > > > > > > # ----- domain params ----- > > > > /* uncomment the following lines to enable multi-domain detection > > > > support */ > > > > modparam("domain", "db_url", > > "mysql://openser:openserrw@192.168.0.10/openser") > > > > modparam("domain", "db_mode", 1) # Use caching > > > > # ----- multi-module params ----- > > > > /* uncomment the following line if you want to enable > multi-domain support > > > > in the modules (dafault off) */ > > > > modparam("alias_db|auth_db|usrloc|uri_db", "use_domain", 1) > > > > > > > > # ----- presence params ----- > > > > /* uncomment the following lines if you want to enable presence */ > > > > #modparam("presence|presence_xml", "db_url", > > > > # "mysql://openser:openserrw@192.168.1.3/openser_1_3") > > > > #modparam("presence_xml", "force_active", 1) > > > > #modparam("presence", "server_address", "sip:192.168.1.2:5060 > <http://192.168.1.2:5060> > > <http://192.168.1.2:5060>") > > > > > > > > ####### Routing Logic ######## > > > > > > > > # main request routing logic > > > > route{ > > > > if (!mf_process_maxfwd_header("10")) { > > > > sl_send_reply("483","Too Many Hops"); > > > > exit; > > > > } > > > > if (has_totag()) { > > > > # sequential request withing a dialog should > > > > # take the path determined by record-routing > > > > if (loose_route()) { > > > > if (is_method("BYE")) { > > > > setflag(1); # do accouting ... > > > > setflag(3); # ... even if the transaction fails > > > > } > > > > route(1); > > > > } else { > > > > sl_send_reply("404","Not here"); > > > > } > > > > exit; > > > > } > > > > #initial requests > > > > # CANCEL processing > > > > if (is_method("CANCEL")) > > > > { > > > > if (t_check_trans()) > > > > t_relay(); > > > > exit; > > > > } > > > > t_check_trans(); > > > > # DESCOMENTEI O BLOCO IF{} > > > > # authenticate if from local subscriber (uncomment to enable auth) > > > > if (!(method=="REGISTER") && from_uri==myself) > > > > { > > > > if (!proxy_authorize("", "subscriber")) { > > > > proxy_challenge("", "0"); > > > > exit; > > > > } > > > > if (!check_from()) { > > > > sl_send_reply("403","Forbidden auth ID"); > > > > exit; > > > > } > > > > consume_credentials(); > > > > # caller authenticated > > > > } > > > > # record routing > > > > if (!is_method("REGISTER|MESSAGE")) > > > > record_route(); > > > > # account only INVITEs > > > > if (is_method("INVITE")) { > > > > setflag(1); # do accouting > > > > } > > > > if (!uri==myself) > > > > /* replace with following line if multi-domain support is used */ > > > > ##if (!is_uri_host_local()) > > > > { > > > > append_hf("P-hint: outbound\r\n"); > > > > # if you have some interdomain connections via TLS > > > > ##if($rd=="tls_domain1.net") { > > > > ## t_relay("tls:domain1.net <http://domain1.net> > <http://domain1.net>"); > > > > ## exit; > > > > ##} else if($rd=="tls_domain2.net") { > > > > ## t_relay("tls:domain2.net <http://domain2.net> > <http://domain2.net>"); > > > > ## exit; > > > > ##} > > > > route(1); > > > > } > > > > # requests for my domain > > > > /* uncomment this if you want to enable presence server > > > > and comment the next 'if' block > > > > NOTE: uncomment also the definition of route[2] from below */ > > > > ##if( is_method("PUBLISH|SUBSCRIBE")) > > > > ## route(2); > > > > if (is_method("PUBLISH")) > > > > { > > > > sl_send_reply("503", "Service Unavailable"); > > > > exit; > > > > } > > > > if (is_method("REGISTER")) > > > > { > > > > # ACRESCENTEI O IP ADDR - MRG > > > > # authenticate the REGISTER requests (uncomment to enable auth) > > > > #if (!www_authorize("vmw02-srv", "subscriber")) > > > > #{ > > > > # www_challenge("vmw02-srv", "0"); > > > > # exit; > > > > #} > > > > # > > > > #if (!check_to()) > > > > ##{ > > > > ## sl_send_reply("403","Forbidden auth ID"); > > > > ## exit; > > > > ##} > > > > if (!save("location")) > > > > sl_reply_error(); > > > > exit; > > > > } > > > > if ($rU==NULL) { > > > > # request with no Username in RURI > > > > sl_send_reply("484","Address Incomplete"); > > > > exit; > > > > } > > > > # apply DB based aliases (uncomment to enable) > > > > alias_db_lookup("dbaliases"); > > > > if (!lookup("location")) { > > > > switch ($retcode) { > > > > case -1: > > > > case -3: > > > > t_newtran(); > > > > t_reply("404", "Not Found"); > > > > exit; > > > > case -2: > > > > sl_send_reply("405", "Method Not Allowed"); > > > > exit; > > > > } > > > > } > > > > # when routing via usrloc, log the missed calls also > > > > setflag(2); > > > > route(1); > > > > } > > > > > > > > route[1] { > > > > # for INVITEs enable some additional helper routes > > > > if (is_method("INVITE")) { > > > > t_on_branch("2"); > > > > t_on_reply("2"); > > > > t_on_failure("1"); > > > > } > > > > if (!t_relay()) { > > > > sl_reply_error(); > > > > }; > > > > exit; > > > > } > > > > > > > > # Presence route > > > > /* uncomment the whole following route for enabling presence > > > > NOTE: do not forget to enable the call of this route from the main > > > > route */ > > > > ##route[2] > > > > ##{ > > > > ## if (!t_newtran()) > > > > ## { > > > > ## sl_reply_error(); > > > > ## exit; > > > > ## }; > > > > ## > > > > ## if(is_method("PUBLISH")) > > > > ## { > > > > ## handle_publish(); > > > > ## t_release(); > > > > ## } > > > > ## else > > > > ## if( is_method("SUBSCRIBE")) > > > > ## { > > > > ## handle_subscribe(); > > > > ## t_release(); > > > > ## } > > > > ## > > > > ## exit; > > > > ##} > > > > > > > > branch_route[2] { > > > > xlog("new branch at $ru\n"); > > > > } > > > > > > > > onreply_route[2] { > > > > xlog("incoming reply\n"); > > > > } > > > > > > > > failure_route[1] { > > > > if (t_was_cancelled()) { > > > > exit; > > > > } > > > > # uncomment the following lines if you want to block client > > > > # redirect based on 3xx replies. > > > > ##if (t_check_status("3[0-9][0-9]")) { > > > > ##t_reply("404","Not found"); > > > > ## exit; > > > > ##} > > > > # uncomment the following lines if you want to redirect the failed > > > > # calls to a different new destination > > > > ##if (t_check_status("486|408")) { > > > > ## sethostport("192.168.2.100:5060 <http://192.168.2.100:5060> > <http://192.168.2.100:5060>"); > > > > ## append_branch(); > > > > ## # do not set the missed call flag again > > > > ## t_relay(); > > > > ##} > > > > } > > > > > > > > *Ngrep -d eth1 -qt -W byline port 5060* > > > > root@vmw02-srv:~# ngrep -d eth1 -qt -W byline port 5060 > > > > interface: eth1 (192.168.0.0/255.255.255.0 > <http://192.168.0.0/255.255.255.0> > > <http://192.168.0.0/255.255.255.0>) > > > > filter: (ip or ip6) and ( port 5060 ) > > > > U 2008/03/20 13:57:31.763060 192.168.0.25:5060 > <http://192.168.0.25:5060> > > <http://192.168.0.25:5060> -> 192.168.0.10:5060 > <http://192.168.0.10:5060> <http://192.168.0.10:5060> > > > > REGISTER sip:spo.voip.br <http://spo.voip.br> > <http://spo.voip.br> SIP/2.0. > > > > Via: SIP/2.0/UDP 192.168.0.25 <http://192.168.0.25> > > <http://192.168.0.25>;rport;branch=z9hG4bKignjupsg. > > > > Max-Forwards: 70. > > > > To: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>. > > > > From: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>;tag=dcoan. > > > > Call-ID: iswtwciijecswfp(a)192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25> > > <mailto:iswtwciijecswfp@192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25>>. > > > > CSeq: 883 REGISTER. > > > > Contact: <sip:vmwcli03@192.168.0.25 > <mailto:sip:vmwcli03@192.168.0.25> > > <mailto:sip <mailto:sip>:vmwcli03@192.168.0.25 > <mailto:vmwcli03@192.168.0.25>>>;expires=3600. > > > > Allow: > INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO. > > > > User-Agent: Twinkle/1.0. > > > > Content-Length: 0. > > > > . > > > > > > > > U 2008/03/20 13:57:32.333159 192.168.0.25:5060 > <http://192.168.0.25:5060> > > <http://192.168.0.25:5060> -> 192.168.0.10:5060 > <http://192.168.0.10:5060> <http://192.168.0.10:5060> > > > > REGISTER sip:spo.voip.br <http://spo.voip.br> > <http://spo.voip.br> SIP/2.0. > > > > Via: SIP/2.0/UDP 192.168.0.25 <http://192.168.0.25> > > <http://192.168.0.25>;rport;branch=z9hG4bKignjupsg. > > > > Max-Forwards: 70. > > > > To: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>. > > > > From: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>;tag=dcoan. > > > > Call-ID: iswtwciijecswfp(a)192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25> > > <mailto:iswtwciijecswfp@192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25>>. > > > > CSeq: 883 REGISTER. > > > > Contact: <sip:vmwcli03@192.168.0.25 > <mailto:sip:vmwcli03@192.168.0.25> > > <mailto:sip <mailto:sip>:vmwcli03@192.168.0.25 > <mailto:vmwcli03@192.168.0.25>>>;expires=3600. > > > > Allow: > INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO. > > > > User-Agent: Twinkle/1.0. > > > > Content-Length: 0. > > > > . > > > > > > > > U 2008/03/20 13:57:33.321952 192.168.0.25:5060 > <http://192.168.0.25:5060> > > <http://192.168.0.25:5060> -> 192.168.0.10:5060 > <http://192.168.0.10:5060> <http://192.168.0.10:5060> > > > > REGISTER sip:spo.voip.br <http://spo.voip.br> > <http://spo.voip.br> SIP/2.0. > > > > Via: SIP/2.0/UDP 192.168.0.25 <http://192.168.0.25> > > <http://192.168.0.25>;rport;branch=z9hG4bKignjupsg. > > > > Max-Forwards: 70. > > > > To: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>. > > > > From: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>;tag=dcoan. > > > > Call-ID: iswtwciijecswfp(a)192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25> > > <mailto:iswtwciijecswfp@192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25>>. > > > > CSeq: 883 REGISTER. > > > > Contact: <sip:vmwcli03@192.168.0.25 > <mailto:sip:vmwcli03@192.168.0.25> > > <mailto:sip <mailto:sip>:vmwcli03@192.168.0.25 > <mailto:vmwcli03@192.168.0.25>>>;expires=3600. > > > > Allow: > INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO. > > > > User-Agent: Twinkle/1.0. > > > > Content-Length: 0. > > > > . > > > > > > > > *U 2008/03/20 13:57:35.309584 192.168.0.25:5060 > <http://192.168.0.25:5060> > > <http://192.168.0.25:5060> -> 192.168.0.10:5060 > <http://192.168.0.10:5060> > > <http://192.168.0.10:5060>* > > > > *REGISTER sip:spo.voip.br <http://spo.voip.br> > <http://spo.voip.br> SIP/2.0.* > > > > Via: SIP/2.0/UDP 192.168.0.25 <http://192.168.0.25> > > <http://192.168.0.25>;rport;branch=z9hG4bKignjupsg. > > > > Max-Forwards: 70. > > > > To: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>. > > > > From: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>;tag=dcoan. > > > > Call-ID: iswtwciijecswfp(a)192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25> > > <mailto:iswtwciijecswfp@192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25>>. > > > > CSeq: 883 REGISTER. > > > > Contact: <sip:vmwcli03@192.168.0.25 > <mailto:sip:vmwcli03@192.168.0.25> > > <mailto:sip <mailto:sip>:vmwcli03@192.168.0.25 > <mailto:vmwcli03@192.168.0.25>>>;expires=3600. > > > > Allow: > INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO. > > > > User-Agent: Twinkle/1.0. > > > > Content-Length: 0. > > > > . > > > > > > > > *U 2008/03/20 13:57:37.026703 192.168.0.10:5060 > <http://192.168.0.10:5060> > > <http://192.168.0.10:5060> -> 192.168.0.25:5060 > <http://192.168.0.25:5060> > > <http://192.168.0.25:5060>* > > > > *SIP/2.0 483 Too Many Hops.* > > > > Via: SIP/2.0/UDP 192.168.0.25 <http://192.168.0.25> > > <http://192.168.0.25>;rport=5060;branch=z9hG4bKignjupsg. > > > > To: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>;tag=1333af5435552d3677a0ca954c3a6e9f.6889. > > > > From: "vmwcli03" <sip:vmwcli03@spo.voip.br > <mailto:sip:vmwcli03@spo.voip.br> > > <mailto:sip <mailto:sip>:vmwcli03@spo.voip.br > <mailto:vmwcli03@spo.voip.br>>>;tag=dcoan. > > > > Call-ID: iswtwciijecswfp(a)192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25> > > <mailto:iswtwciijecswfp@192.168.0.25 > <mailto:iswtwciijecswfp@192.168.0.25>>. > > > > CSeq: 883 REGISTER. > > > > Server: OpenSER (1.3.0-notls (i386/linux)). > > > > Content-Length: 0. > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > Users(a)lists.openser.org <mailto:Users@lists.openser.org> > > http://lists.openser.org/cgi-bin/mailman/listinfo/users > >

16 years, 1 month

Re: [OpenSER-Users] Info about redirect function

by Bogdan-Andrei Iancu

Hi Valerio, not sure if this will be sufficient as, as far I understood, you take care only on signalling part. You should also look for RTP stream. Regards, Bogdan Valerio Di Marino wrote: > Hi Andrei, > thanks for your answer: I already seen the file redirect.cfg. > > My doubt is about the possibility to solve the problem with NAT. > > Using a public proxy I need to open several ports on the canopy router > (see my first message): in other case I can't listen the caller. > Mi idea is to install a redirect server in my network, on a my public > machine, pointing my ATA on this: redirect server will redirect data > to the public proxy server. Is it possible to do this, and should this > configuration solve my problem ? > > In this moment, I cant try this solution... > > Thanks > Valerio > > 2008/3/25, Bogdan-Andrei Iancu <bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro>>: > > Hi Valerio, > > If you want to learn how to do redirect with openser, take a look at: > examples/redirect.cfg > > in the SVN tree. > > Regards, > Bogdan > > > Valerio Di Marino wrote: > > Good morning to all. > > > > I am Valerio, and this im my first post. > > I was never using OPENSER: I discovered it this morning, > searcing for > > a solution. > > > > I have this situation: I am using Motorola Canopy wireless > antennas to > > deploy internet connection, but it implements a symmetric NAT which > > make not operating STUN protocol. > > I think that one of solution should be to install a proxy server > which > > redirects registering and calls to the public proxy (euteliavoip). > > I thought that OPENSER should be a good solution: can you > confirm this? > > Thanks for every your suggestions. > > Valerio > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > Users(a)lists.openser.org <mailto:Users@lists.openser.org> > > http://lists.openser.org/cgi-bin/mailman/listinfo/users > > > >

16 years, 1 month

Re: [OpenSER-Users] Carrierroute

by Douglas Garstang

> > >I am using this module in production with more then 400k routes loaded >for 8 different providers and it is working like a charm. >As Henning mentioned, the interface is a little bit cumbersome but usable. >You can put all the carriers under the same table and prioritize the >gateway based on domains. Like tis you don't need to hardcode >anything in the config file. > >Carrierroute was designed to deal with a big amount of routing rules >and it is doing an amazing job. >LCR was designed to deal with a limited number of routes/gateways but >t has a different level of flexibility and a more mature interface. Ovidiu, ok... but I'm still a bit confused. How do you simulate LCR with carrierroute? Doug. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

16 years, 1 month

← Newer
1
...
4
5
6
7
8
9
10
...
24
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users March 2008