sr-users

sr-users@lists.kamailio.org

52 participants
37559 discussions

Start a nNew thread

[Users] Help Me ? (urgent)
by fusheng.lin＠gmail.com 07 Jun '06

07 Jun '06

Do anyone help me to solve the problem where OPENSER server behind NAT ?

2 3

[Serusers] uac module
by olivier.taylor 07 Jun '06

07 Jun '06

Does the uac module exist in Ser? I have ser0.9.6 and I dont see it... Olivier

2 1

[Serusers] RE: Authorizing IM requests
by İlker Aktuna (Koç.net) 07 Jun '06

07 Jun '06

Hi Vaclav, Did you have time to check usrloc for db support ? Thanks, ilker -----Original Message----- From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] Sent: Wednesday, May 31, 2006 12:57 PM To: İlker Aktuna (Koç.net) Cc: samuel; serusers(a)iptel.org Subject: Re: Authorizing IM requests The file format is different! You really CAN NOT set these rules from EyeBeam. The filename is given as parameter to authorize_message function (in CVS version; not snapshot). If you need it quickly you really have to correct it somewhere in sources (I don't know where). Vaclav On Wed, May 31, 2006 at 10:52:42AM +0300, ?lker Aktuna (Koç.net) wrote: > Hi Vaclav, > > On which file does Ser look for when authorizing messages ? > According to that maybe I can link privacy-lists file to im-rules file > (which Ser looks for) Would that work ? > > Usrloc problem is very important for me. Please tell me anything I can > do to find out the problem (if there is anything that I can do) > > Thanks, > ilker > > -----Original Message----- > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > Sent: Wednesday, May 31, 2006 9:29 AM > To: ?lker Aktuna (Koç.net) > Cc: samuel; serusers(a)iptel.org > Subject: Re: Authorizing IM requests > > Hi, > yes I did, but I had forgotten... > > You can NOT use EyeBeam to work with message authorization - it will NEVER set the rules which are needed by SER. You can do this only manually on XCAP server. > > I try to look on the userloc problem, but don't know when. > > Vaclav > > On Tue, May 30, 2006 at 05:29:27PM +0300, ?lker Aktuna (Koç.net) wrote: > > Hi Vaclav, > > > > Did you receive my following email ? > > > > Btw, I still couldn't find the neccessary db structure for using > > usrloc with db support. Can you point me to the right person who > > knows the required db structure ? > > > > Thanks, > > ilker > > > > ________________________________ > > > > From: ?lker Aktuna (Koç.net) > > Sent: Monday, May 29, 2006 12:52 PM > > To: 'Vaclav Kubart' > > Cc: samuel; serusers(a)iptel.org > > Subject: RE: Authorizing IM requests > > > > > > > > > > Well, then what can I use in the following line to authorize IM messages ? > > > > if (authorize_message("https://sip.koc.net/xcap")) { > > > > Eyebeam updates file /xcap/privacy-lists/user/privacy-lists.xml when I change the "privacy" configuration on Eyebeam client. > > > > Thanks, > > ilker > > > > -----Original Message----- > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > > Sent: Friday, May 26, 2006 4:48 PM > > To: ?lker Aktuna (Koç.net) > > Cc: samuel; serusers(a)iptel.org > > Subject: Re: Authorizing IM requests > > > > Yes, I meant, that this will not work together. > > > > I don't know. Privacy-lists are something eyeBeam's internal or something standardized? > > > > Im-rules are SER internal. > > > > Vaclav > > > > On Fri, May 26, 2006 at 04:43:35PM +0300, ?lker Aktuna (Koç.net) wrote: > > > Do you mean it won't work with privacy-lists ? > > > What can I try ? > > > > > > Thanks, > > > ilker > > > > > > -----Original Message----- > > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > > > Sent: Friday, May 26, 2006 4:40 PM > > > To: ?lker Aktuna (Koç.net) > > > Cc: samuel; serusers(a)iptel.org > > > Subject: Re: Authorizing IM requests > > > > > > EyeBeam won't use im-rules and SER won't use with privacy-lists. It something else. > > > > > > Vaclav > > > > > > On Fri, May 26, 2006 at 02:24:42PM +0300, ?lker Aktuna (Koç.net) wrote: > > > > Hi Samuel, > > > > > > > > Now that presence is working I'm checking xcap possibilities. > > > > I see that IM xcap authorization is not working. > > > > > > > > I don't know what to use in: > > > > >if (authorize_message("im-rules.xml")){ > > > > > > > > My client (Eyebeam) does not use im-rules.xml , but it uses > > > > privacy-lists.xml and that file is in privacy-lists folder. How > > > > should I change the configuration line to use this file ? > > > > > > > > Regards, > > > > ilker > > > > > > > > -----Original Message----- > > > > From: samuel [mailto:samu60@gmail.com] > > > > Sent: Tuesday, May 16, 2006 5:26 PM > > > > To: Vaclav Kubart > > > > Cc: ?lker Aktuna (Koç.net); serusers(a)iptel.org > > > > Subject: Re: [Serusers] PA error sending notifies > > > > > > > > 2006/5/16, Vaclav Kubart <vaclav.kubart(a)iptel.org>: > > > > > reply inline... > > > > > > If you are using XCAP authentication for MESSAGEs, there's a > > > > > > function called authorize_message that needs to have as > > > > > > parameter the file name of the IM ruleset. > > > > > > For user sam, in xcap-root/im-rules/users/sam/im-rules.xml > > > > > > there are the rules for this function. The XML file is > > > > > > similar to the presence-rules but has important differences > > > > > > (correct me if I'm wrong, > > > > > > Vaclav!!!): > > > > > > *it only has a blacklist parameter (no whitelist!!) > > > > > > > > > > It doesn't depend on name of the rule > > > > > (blacklist/whitelist/...) it depends on the action (block, > > > > > ...). You can have as many rules as you want, but to > > > > > explicitly enable something > > > > > (whitelist) is needless because MESSSAGEs are allowed by > > > > > default (at the end of the presence handbook I tried to > > > > > describe im-rules the same way as presence-rules are described in their draft). > > > > > > > > > > > *the namespace is different (so be carefull in copy&paste > > > > > > from the > > > > > > presence-rules!!!) and, as Vaclav poitned out "proprietary" > > > > > > from iptel. > > > > > > > > > > And the action element name differs: <im-handling> is used > > > > > instead of <sub-handling>. > > > > > > > > > > > > > Uops...I haven't noticed :P thanks! > > > > > > > > > Vaclav > > > > > > > > > > > > > > > > > About the structure I have: x86 debian testing. Libraries > > > > > > versions I don't know exactly but the ones in the testing > > > > > > repository EXCEPT a library which I had to get for serweb > > > > > > from the stable version...but it's not affecting SER part. > > > > > > > > > > > > Samuel. > > > > > > 2006/5/16, ?lker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >Hi, > > > > > > > > > > > > > >What did you mean by following: > > > > > > > > > > > > > >>Instead of > > > > > > >>> > > > > > > >>> if (authorize_message("http://localhost/xcap")) { > > > > > > >> > > > > > > >>there should be > > > > > > >> > > > > > > >>if (authorize_message("im-rules.xml")){ > > > > > > > > > > > > > >Btw, did you receive my email with following questions : > > > > > > > > > > > > > >>> I have the same problem with notification and other > > > > > > >>> presence messages > > > > > > >with you. > > > > > > >>> Can you tell me which Linux distribution you are using Ser on ? > > > > > > >>> Also please include version numbers for libraries that > > > > > > >>> are required by > > > > > > >Ser. > > > > > > >>> > > > > > > >>> I am trying to find similarities between yours and my ser server. > > > > > > > > > > > > > >Regards, > > > > > > >ilker > > > > > > > > > > > > > <http://387555.sigclick.mailinfo.com/sigclick/06090304/030C4A09/020148 > 03/15141696.jpg> > ______________________________________________________________________ > ______________________________________________________________________ > _ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor > olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. > This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. > ______________________________________________________________________ > ______________________________________________________________________ > _ <http://387555.sigclick.mailinfo.com/sigclick/010C0102/0604490B/01024A05/224…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

2 1

[Serusers] Problem with Presence
by Alois Schafferhofer 07 Jun '06

07 Jun '06

Hi, If I want to send a Publish request to the SIP Express Router, it doesn't store the status into the "presentity"-table. I get following lines into the log-file: /usr/sbin/ser[10124]: handle publish request /usr/sbin/ser[10124]: get_pres_uri: _puri=sip:PDA_User at mydomain.com /usr/sbin/ser[10124]: handle_publish -4- p_uri= p_uri.len=23 /usr/sbin/ser[10124]: handle_publish -5- presentity=0x4069e0b8 /usr/sbin/ser[10124]: publish_presentity: no tuple for PDA_User at mydomain.com /usr/sbin/ser[10124]: handle_publish -8- paerrno=0 /usr/sbin/ser[10124]: handled publish Best regards, Alois

2 1

[Serusers] Starting problems
by Zenone 07 Jun '06

07 Jun '06

Hi, I have two problems: I wonder why my registar doesn't work although the module 'registar.so'is loaded in the file 'ser.cfg'. And I don't understand why uncommenting the 'mysql.so' line, in the file ser.cfg' make ser failes (rights problem with mysql?). I work on a fedora4 and ser version is 0.9.6. If somebody can help me it would be great! Thanks, Michel ________________________________________________ Message sent using UebiMiau 2.7.8

1 0

[Serusers] Proxy to Proxy between different realm/domain
by Chahn John Kim 07 Jun '06

07 Jun '06

Hi all, Need you experts' help on SIP design. I've setup a testbed composed of two SER Registrar/Proxies in two different realm/domain(s) as below; <--Internal Private(192.168.x.0----><----External Public(x.x.x.0)---------> UA1<-----------------> SER1 <---------------------> SER2 <------------> UA2 Mydomain.org Registrar/Proxy Theirdomain.org Registrar/Proxy What is the right way to pass the user credential of UA1 to SER2 so that "INVITE" to UA2 will be accepted at SER2, knowing that UA1 user has its login ID/password to SER2 but it is locally "REGISTER"ed at SER1 in private domain? I guess I am having trouble understanding working mechanism of "inter" SIP realm or domain. Any comments will be appreciated. John Kim email: johnk(a)koreanet.us johnk(a)netcomusa.us

2 1

[Users] Memory Leak in latest cvs version?
by Douglas Garstang 06 Jun '06

06 Jun '06

I'm wondering if there's a memory leak or something in the latest cvs version of openser. Only been running it for a while, processing very few calls, and this was appearing... Jun 6 15:58:52 apollo /usr/local/sbin/openser[15208]: ERROR:tm:print_uac_request: no pkg_mem Jun 6 15:58:52 apollo /usr/local/sbin/openser[15208]: ERROR:tm:t_forward_nonack: failure to add branches Jun 6 15:58:52 apollo /usr/local/sbin/openser[15208]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 426 Jun 6 15:58:52 apollo /usr/local/sbin/openser[15208]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 426 Jun 6 15:58:52 apollo /usr/local/sbin/openser[15204]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:52 apollo /usr/local/sbin/openser[15207]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:53 apollo /usr/local/sbin/openser[15206]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:53 apollo /usr/local/sbin/openser[15209]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:53 apollo /usr/local/sbin/openser[15211]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:54 apollo /usr/local/sbin/openser[15205]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:54 apollo /usr/local/sbin/openser[15210]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:54 apollo /usr/local/sbin/openser[15208]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:55 apollo /usr/local/sbin/openser[15204]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:55 apollo /usr/local/sbin/openser[15207]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:55 apollo /usr/local/sbin/openser[15206]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:56 apollo /usr/local/sbin/openser[15209]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:56 apollo /usr/local/sbin/openser[15211]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:56 apollo /usr/local/sbin/openser[15205]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:57 apollo /usr/local/sbin/openser[15210]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:57 apollo /usr/local/sbin/openser[15208]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:58 apollo /usr/local/sbin/openser[15204]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:58:59 apollo /usr/local/sbin/openser[15207]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:02 apollo /usr/local/sbin/openser[15206]: ERROR: dns_cname_parser: out of memory Jun 6 15:59:02 apollo /usr/local/sbin/openser[15206]: ERROR: get_record: rdata parse error Jun 6 15:59:02 apollo /usr/local/sbin/openser[15206]: ERROR: get_record Jun 6 15:59:02 apollo /usr/local/sbin/openser[15206]: ERROR: build_req_buf_from_sip_req: out of memory Jun 6 15:59:02 apollo /usr/local/sbin/openser[15206]: ERROR:tm:print_uac_request: no pkg_mem Jun 6 15:59:02 apollo /usr/local/sbin/openser[15206]: ERROR:tm:t_forward_nonack: failure to add branches Jun 6 15:59:02 apollo /usr/local/sbin/openser[15206]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 442 Jun 6 15:59:02 apollo /usr/local/sbin/openser[15206]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 442 Jun 6 15:59:04 apollo /usr/local/sbin/openser[15205]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:05 apollo /usr/local/sbin/openser[15208]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:06 apollo /usr/local/sbin/openser[15204]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:06 apollo /usr/local/sbin/openser[15207]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:07 apollo /usr/local/sbin/openser[15206]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:07 apollo /usr/local/sbin/openser[15209]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:07 apollo /usr/local/sbin/openser[15211]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:07 apollo /usr/local/sbin/openser[15205]: ERROR: dns_cname_parser: out of memory Jun 6 15:59:07 apollo /usr/local/sbin/openser[15205]: ERROR: get_record: rdata parse error Jun 6 15:59:07 apollo /usr/local/sbin/openser[15205]: ERROR: get_record Jun 6 15:59:07 apollo /usr/local/sbin/openser[15205]: ERROR: build_req_buf_from_sip_req: out of memory Jun 6 15:59:07 apollo /usr/local/sbin/openser[15205]: ERROR:tm:print_uac_request: no pkg_mem Jun 6 15:59:07 apollo /usr/local/sbin/openser[15205]: ERROR:tm:t_forward_nonack: failure to add branches Jun 6 15:59:07 apollo /usr/local/sbin/openser[15205]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 426 Jun 6 15:59:07 apollo /usr/local/sbin/openser[15205]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 426 Jun 6 15:59:08 apollo /usr/local/sbin/openser[15210]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:08 apollo /usr/local/sbin/openser[15204]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:08 apollo /usr/local/sbin/openser[15207]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:09 apollo /usr/local/sbin/openser[15206]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:09 apollo /usr/local/sbin/openser[15209]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:09 apollo /usr/local/sbin/openser[15205]: ERROR: build_res_buf_from_sip_req: out of memory ; needs 379 Jun 6 15:59:09 apollo /usr/local/sbin/openser[15210]: ERROR: dns_cname_parser: out of memory Jun 6 15:59:09 apollo /usr/local/sbin/openser[15210]: ERROR: get_record: rdata parse error

1 0

[Serusers] SER + RTPPROXY incorrect UPD checksum
by Tuan Pham 06 Jun '06

06 Jun '06

All, When I enabled rtpproxy, it noticed that all the RTP messages sent out from SER to the UA has incorrect UDP checksum. What am I missing? Do I need to configure anything to resolve this problem? Thanks, Tuan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

RE: [Users] Openser 1.1 and Dispatacher Failover
by Douglas Garstang 06 Jun '06

06 Jun '06

Thanks Carsten. With your help, I think I got it working. One final thing is that I'd like to log what's happening. What pseudo variable could I use in failure_route to show what destination I was trying? Doug. > -----Original Message----- > From: Douglas Garstang > Sent: Tuesday, June 06, 2006 10:09 AM > To: Carsten Bock > Cc: Users(a)openser.org > Subject: RE: [Users] Openser 1.1 and Dispatacher Failover > > > Thanks Carsten. > > What does ds_next_domain() do? Is failure_route[1] supposed > to be calling itself? Why don't you call ds_next_dst() instead? > > Douglas. > > > -----Original Message----- > > From: Carsten Bock [mailto:openser-list@qbiz.de] > > Sent: Tuesday, June 06, 2006 9:47 AM > > To: Douglas Garstang > > Cc: Users(a)openser.org > > Subject: Re: [Users] Openser 1.1 and Dispatacher Failover > > > > > > Hi Douglas, > > > > It's quite simple. Here an except from a possible Main-Route: > > > > [...] > > # Choose a Proxy (Round-Robin, PSTN-Gateways) > > ds_select_domain("2", "4"); > > > > # On Failure: Choose next Proxy > > t_on_failure("1"); > > > > # Relay to the Proxy > > if (!t_relay()) { > > sl_reply_error(); > > } > > [...] > > > > And here the corresponding failure-route: > > failure_route[1] { > > # Choose another gateway > > if (t_check_status("408")) { > > if (ds_next_domain()) { > > # On Failure: Choose next Proxy > > t_on_failure("1"); > > # Relay to Proxy > > t_relay(); > > } else { > > t_reply("503", "Service not available"); > > return; > > } > > } > > } > > > > And here the modparam for the dispatcher: > > # Dispatcher: Enable Failover-Support > > modparam("dispatcher", "flags", 2) > > That's it. > > > > Carsten > > > > Douglas Garstang schrieb: > > > Carston. > > > > > > Thanks for the info. Unfortunately, none of this stuff is > > documented. I really don't have a clue how to implement any of this. > > > > > > Douglas. > > > > > > > > >> -----Original Message----- > > >> From: Carsten Bock [mailto:openser-list@qbiz.de] > > >> Sent: Tuesday, June 06, 2006 9:34 AM > > >> To: Douglas Garstang > > >> Cc: Users(a)openser.org > > >> Subject: Re: [Users] Openser 1.1 and Dispatacher Failover > > >> > > >> > > >> Hi Douglas, > > >> > > >> Yes you're right, it does. You just cannot do a simple > (stateless) > > >> forward for failover, you need to establish a transaction (e. g. > > >> t_relay()) and you need a failure-route handling the error > > >> (if there is > > >> any error). And don't forget the flags of the dispatcher > > >> (Flag 2 needs > > >> to be enabled). > > >> > > >> Carsten > > >> > > >> Douglas Garstang schrieb: > > >> > > >>> I was under the impression that the dispatcher module in > > >>> > > >> Openser 1.1 did failover? > > >> > > >>> I just tried it. I put an invalid IP in my dispatcher.list > > >>> > > >> file. When the dispatcher selects that invalid IP, it looks > > >> like it never times out and tries another. > > >> > > >>> # PSTN > > >>> 2 sip:216.187.140.217 # INVALID > > >>> 2 sip:216.187.141.246 > > >>> 2 sip:216.187.140.216 > > >>> > > >>> What special steps do I need to take to ensure the > > >>> > > >> dispatcher does failover? > > >> > > >>> Here's a piece of my openser.cfg file... > > >>> > > >>> # > > >>> # Outgoing PSTN Calls - Dispatch to Audiocodes > > >>> # > > >>> if ( src_ip == 216.187.142.203 || > > >>> src_ip == 216.187.142.204 || > > >>> src_ip == 216.187.142.232 || > > >>> src_ip == 216.187.142.201 || > > >>> src_ip == 216.187.142.231 ) { > > >>> sl_send_reply("100","Trying"); > > >>> xlog ("L_INFO","Outbound PSTN call. Dispatching > > >>> > > >> to Audiocodes"); > > >> > > >>> ds_select_dst("2","0"); > > >>> forward(); > > >>> return; > > >>> } > > >>> > > >>> Doug. > > >>> > > >>> _______________________________________________ > > >>> Users mailing list > > >>> Users(a)openser.org > > >>> http://openser.org/cgi-bin/mailman/listinfo/users > > >>> > > >>> > > >>> > > >> > > > > > > > > > > > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users >

1 0

RE: [Users] Openser 1.1 and Dispatacher Failover
by Douglas Garstang 06 Jun '06

06 Jun '06

Thanks Carsten. What does ds_next_domain() do? Is failure_route[1] supposed to be calling itself? Why don't you call ds_next_dst() instead? Douglas. > -----Original Message----- > From: Carsten Bock [mailto:openser-list@qbiz.de] > Sent: Tuesday, June 06, 2006 9:47 AM > To: Douglas Garstang > Cc: Users(a)openser.org > Subject: Re: [Users] Openser 1.1 and Dispatacher Failover > > > Hi Douglas, > > It's quite simple. Here an except from a possible Main-Route: > > [...] > # Choose a Proxy (Round-Robin, PSTN-Gateways) > ds_select_domain("2", "4"); > > # On Failure: Choose next Proxy > t_on_failure("1"); > > # Relay to the Proxy > if (!t_relay()) { > sl_reply_error(); > } > [...] > > And here the corresponding failure-route: > failure_route[1] { > # Choose another gateway > if (t_check_status("408")) { > if (ds_next_domain()) { > # On Failure: Choose next Proxy > t_on_failure("1"); > # Relay to Proxy > t_relay(); > } else { > t_reply("503", "Service not available"); > return; > } > } > } > > And here the modparam for the dispatcher: > # Dispatcher: Enable Failover-Support > modparam("dispatcher", "flags", 2) > That's it. > > Carsten > > Douglas Garstang schrieb: > > Carston. > > > > Thanks for the info. Unfortunately, none of this stuff is > documented. I really don't have a clue how to implement any of this. > > > > Douglas. > > > > > >> -----Original Message----- > >> From: Carsten Bock [mailto:openser-list@qbiz.de] > >> Sent: Tuesday, June 06, 2006 9:34 AM > >> To: Douglas Garstang > >> Cc: Users(a)openser.org > >> Subject: Re: [Users] Openser 1.1 and Dispatacher Failover > >> > >> > >> Hi Douglas, > >> > >> Yes you're right, it does. You just cannot do a simple (stateless) > >> forward for failover, you need to establish a transaction (e. g. > >> t_relay()) and you need a failure-route handling the error > >> (if there is > >> any error). And don't forget the flags of the dispatcher > >> (Flag 2 needs > >> to be enabled). > >> > >> Carsten > >> > >> Douglas Garstang schrieb: > >> > >>> I was under the impression that the dispatcher module in > >>> > >> Openser 1.1 did failover? > >> > >>> I just tried it. I put an invalid IP in my dispatcher.list > >>> > >> file. When the dispatcher selects that invalid IP, it looks > >> like it never times out and tries another. > >> > >>> # PSTN > >>> 2 sip:216.187.140.217 # INVALID > >>> 2 sip:216.187.141.246 > >>> 2 sip:216.187.140.216 > >>> > >>> What special steps do I need to take to ensure the > >>> > >> dispatcher does failover? > >> > >>> Here's a piece of my openser.cfg file... > >>> > >>> # > >>> # Outgoing PSTN Calls - Dispatch to Audiocodes > >>> # > >>> if ( src_ip == 216.187.142.203 || > >>> src_ip == 216.187.142.204 || > >>> src_ip == 216.187.142.232 || > >>> src_ip == 216.187.142.201 || > >>> src_ip == 216.187.142.231 ) { > >>> sl_send_reply("100","Trying"); > >>> xlog ("L_INFO","Outbound PSTN call. Dispatching > >>> > >> to Audiocodes"); > >> > >>> ds_select_dst("2","0"); > >>> forward(); > >>> return; > >>> } > >>> > >>> Doug. > >>> > >>> _______________________________________________ > >>> Users mailing list > >>> Users(a)openser.org > >>> http://openser.org/cgi-bin/mailman/listinfo/users > >>> > >>> > >>> > >> > > > > > >

1 0

Jump to page:

2025

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