sr-users

sr-users@lists.kamailio.org

52 participants
37559 discussions

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

06 Jun '06

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 > > > > > >

2 1

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

06 Jun '06

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.

2 1

RE: [Users] Openser 1.1 and forward()
by Douglas Garstang 06 Jun '06

06 Jun '06

> -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Tuesday, June 06, 2006 8:30 AM > To: Douglas Garstang > Cc: Users(a)openser.org > Subject: Re: [Users] Openser 1.1 and forward() > > > Hi Douglas, > > the prototype of the forward function was changes to align it > with the > TM functions. > Shortly, use forward() to do fwd based on RURI or > forward("[proto:]host[:port]"). See the wikipage also. Bogdan, Err... can you be more specific with your example? How do I know the host if it's all controlled by the dispatcher? Doug.

2 1

RE: [Users] Openser 1.1 and forward()
by Douglas Garstang 06 Jun '06

06 Jun '06

Thanks Bogdan. Maybe someone could update the docs at http://www.openser.org/docs/modules/1.1.x/dispatcher.html ? Doug. > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Tuesday, June 06, 2006 8:30 AM > To: Douglas Garstang > Cc: Users(a)openser.org > Subject: Re: [Users] Openser 1.1 and forward() > > > Hi Douglas, > > the prototype of the forward function was changes to align it > with the > TM functions. > Shortly, use forward() to do fwd based on RURI or > forward("[proto:]host[:port]"). See the wikipage also. > > regard, > bogdan > > Douglas Garstang wrote: > > >I just upgraded from 1.0.1 to the current cvs version. > > > >Ran openser and got this: > > > >Jun 5 11:54:47 apollo openser: parse error (156,21-24): > syntax error > >Jun 5 11:54:47 apollo openser: parse error (156,39-40): bad > forwardargument > > > >Here's the relevant section of openser.cfg. Line 156 is the > line with: forward(uri:host, uri:port); > > > > # > > # Outgoing PSTN Calls - Dispatch to Audiocodes > > # > > if ( src_ip == xxx.187.142.203 || > > src_ip == xxx.187.142.204 || > > src_ip == xxx.187.142.232 || > > src_ip == xxx.187.142.201 || > > src_ip == xxx.187.142.231 ) { > > sl_send_reply("100","Trying"); > > xlog ("L_INFO","Outbound PSTN call. Dispatching > to Audiocodes"); > > ds_select_dst("2","0"); > > forward(uri:host, uri:port); > > return; > > } > > > >What's wrong with this? The example in the 1.1 documentation > has the same use of the forward() command! > > > >Douglas. > > > >_______________________________________________ > >Users mailing list > >Users(a)openser.org > >http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > > >

2 1

[Users] get_redirects("*"), serialize_branches(0), next_branches() not working for me
by Greg Fausak 06 Jun '06

06 Jun '06

I'm trying to play around with the current cvs head but can't get it to work. I wonder if somebody could give me a hint! I built a redirect server: It basically does: rewritehost("ab5350.node-1.com"); sl_send_reply("302", "Redirect"); I forward to the redirect server setting up a failure block: if(is_method("INVITE")) { _QLOG(L_INFO, OUTBOUNDCALL, OUT); t_on_failure("3"); record_route(); setflag(1); setflag(2); rewritehostport(_QSTR (REDIRECTOBGATEWAYIP:REDIRECTOBGATEWAYPORT)); if(!t_relay()) { sl_reply_error(); } } The response below comes back from my redirect server: SIP/2.0 302 Redirect Via: SIP/2.0/UDP 12.46.104.47;branch=z9hG4bKa86.09801851.0 Via: SIP/2.0/UDP 12.46.104.62:5061;branch=z9hG4bKa86.191c2c81.0 Via: SIP/2.0/UDP 12.46.104.59;branch=z9hG4bKa86.dafc0771.0 Via: SIP/2.0/UDP 71.252.176.37:5060;branch=z9hG4bK-d0702751 From: +19722200434 <sip:+19722200434@var-2.com>;tag=3a553a2b9373c699 To: <sip:2143357976@var-2.com>;tag=5531b0101f56e37a4889ece4b0eb40fa.417f Call-ID: f27483a5-50532031(a)71.252.176.37 CSeq: 101 INVITE Contact: sip:+12143357976@ab5350.node-1.com:5060 Content-Length: 0 My failure_route block picks up the routing: failure_route[3] { _QLOG(L_WARN, FAILUREROUTE, here we are); if(status =~ "3[0-9][0-9]") { _QLOG(L_WARN, FAILUREROUTE, status is 3xx); get_redirects("*"); serialize_branches(0); } if(next_branches()) { _QLOG(L_WARN, FAILUREROUTE, next branch); t_on_failure("3"); t_relay(); } _QLOG(L_WARN, FAILUREROUTE, no branches left); if(!t_reply("404", "Not Found")) { _QLOG(L_WARN, FAILUREROUTE, Error); } } My syslog shows QLOG messages. I see the 'status is 3xx' message, which shows the next command to be get_redirects("*"); The next output I see in my syslog is 'no branches left', which indicates that the serialize_branches(0) and next_branches() aren't working as I expected. I've also tried getting rid of the serialize_branches and next_branches and just doing a t_relay() after the get_redirects(), that doesn't work either. Since I'm trying to simulate the redirect server, and the redirect client, I'm sure I got one of them wrong. Can somebody give me a hint? Thanks! -g -- Greg Fausak greg(a)thursday.com

3 12

[Users] Openser 1.1 and forward()
by Douglas Garstang 06 Jun '06

06 Jun '06

I just upgraded from 1.0.1 to the current cvs version. Ran openser and got this: Jun 5 11:54:47 apollo openser: parse error (156,21-24): syntax error Jun 5 11:54:47 apollo openser: parse error (156,39-40): bad forwardargument Here's the relevant section of openser.cfg. Line 156 is the line with: forward(uri:host, uri:port); # # Outgoing PSTN Calls - Dispatch to Audiocodes # if ( src_ip == xxx.187.142.203 || src_ip == xxx.187.142.204 || src_ip == xxx.187.142.232 || src_ip == xxx.187.142.201 || src_ip == xxx.187.142.231 ) { sl_send_reply("100","Trying"); xlog ("L_INFO","Outbound PSTN call. Dispatching to Audiocodes"); ds_select_dst("2","0"); forward(uri:host, uri:port); return; } What's wrong with this? The example in the 1.1 documentation has the same use of the forward() command! Douglas.

2 1

[Serusers] ser to ser relay
by Szabolcs Szasz 06 Jun '06

06 Jun '06

Hi I have 2 SIP networks with 2 SERs like on this diagramm: UA1---------SER1-----------SER----------UA2 I authenticate all UAs and all calls (local, long distance and international) on both SERs. How can I relay the call from UA1 to UA2 ? If for example UA1 has local privileges, is there a posibility to relay the call to UA2 without any more authentication? There is an error 407 (Proxy Authentication Required). Thank you in advance. Szasz Szabolcs -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://linux.bitdefender.com/

1 0

[Users] cant see Bye when the call is diconnected
by Padmaja RV 06 Jun '06

06 Jun '06

Hi all! i have openser running and supports authentication and calling,. i made calls and verified that the media session is established both ways. now if i disconnect the call, i cant see the BYE request sent. in the ethereal i dont see any call related messages after ACK is sent for the INVITE. please help me..... i have a line in the openser.cfg file for the BYE request processing if ( method =="BYE || method==CANCEL") { end_media_session(); }; i have also loaded the mediaproxy.so module. however i dont have media proxy installed. is that y i am not getting to see BYE? i tried removing the above lines from the code. with or without them i dont see any difference in the behavior and i dont see BYE when i hang up. Please help!! Thanks and Regards, Padmaja ----- Original Message ----- From: <users-request(a)openser.org> To: <users(a)openser.org> Sent: Tuesday, June 06, 2006 3:30 PM Subject: Users Digest, Vol 13, Issue 23 > Send Users mailing list submissions to > users(a)openser.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://openser.org/cgi-bin/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request(a)openser.org > > You can reach the person managing the list at > users-owner(a)openser.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Re: Starting and stopping openser (ram) > 2. Re: Starting and stopping openser (Padmaja RV) > 3. Who can help me to make it work when openser is behind NAT. > (fusheng.lin(a)gmail.com) > 4. lookup problem (Jean-Michel Foucher) > 5. Bug in branch handling? (Federico Giannici) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 6 Jun 2006 11:32:21 +0530 > From: ram <talk2ram(a)gmail.com> > Subject: Re: [Users] Starting and stopping openser > To: "Padmaja RV" <padmaja.rv(a)vodcalabs.com> > Cc: users(a)openser.org > Message-ID: > <b74751490606052302g5261be6fsa746d34eb7114712(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi > > check this URL for you to install and running open ser > its easy step by steps > > http://www.openser.org/dokuwiki/doku.php?id=install_and_maintain_openser_fr… > > start from /etc/init.d > > go with this doc, its very usefull for starters > > http://www.openser.org/dokuwiki/doku.php?id=install_and_maintain_openser_fr… > > ram > > > On 6/6/06, Padmaja RV <padmaja.rv(a)vodcalabs.com> wrote: >> >> Hi all! >> since i had problems with running openser thru init.d script., i tried to >> run it thru openserctl. however, the file /var/run/openser.pid is not >> found >> there and it too was not running. so i started running openser with >> /usr/local/sbin/openser start. it works fine this way. also since >> /usr/local/sbin is in my PATH variable, i can directly type openser start >> and this way also it runs. however, after starting openser, it does not >> return the command prompt back. if i have to stop running openser, i have >> to >> hit ctrl+c. there is no other way to stop it.... please let me know how >> to >> start and stop openser directly (not thru init or openserctl because both >> of >> them give me trouble). also how can i see which is the main pid of >> openser >> as when i run the ps command , it shows me some 3-4 pids for different >> subprocesses............ >> >> Thanks in advance, >> Padmaja >> >> >> >

1 0

[Serusers] non-responsive SER 0.9.6
by Cesc 06 Jun '06

06 Jun '06

Hi, I think this issue was already risen a while back, but seen that there is no answer, i will insist :D My SER becomes completely unresponsive (UDP and TCP) after a while. I started it 3 days ago and have a monitoring script that sends 1 REGISTER every 10 secs (plus a few other phones). This morning that SER was totally stoned! :( I have tried sending via UDP and TCP ... same answer (that is, no answer). But, the fifo (thus, part of SER) still works (i can do a serctl moni). I am trying to investigate myself ... what can i do? can i force a core dump from the shell (sending some kill signal) to the already stoned SER? Regards, Cesc

1 0

RE: [Serusers] PA error sending notifies
by İlker Aktuna (Koç.net) 06 Jun '06

06 Jun '06

Hi Samuel, What is your client ? If you use Eyebeam, it updates the file : xcap-root/privacy-lists/users/sam/privacy-lists.xml What is the format used in your im-rules.xml file ? Thanks, ilker -----Original Message----- From: samuel [mailto:samu60@gmail.com] Sent: Friday, June 02, 2006 1:29 PM To: İlker Aktuna (Koç.net) Cc: serusers(a)iptel.org Subject: Re: [Serusers] PA error sending notifies As I said, unfortunately, I ran out of time and I could not go further experimenting with presence & IM...... The path of the file depends on the username, for the user sam, the rules of the IM are located in the next file: xcap-root/im-rules/users/sam/im-rules.xml and what you put within the brackets is just the file name: im-rules.xml. I would say it worked but now i'm not 100% sure, only 99.99% :P and without any modification in the code. The code might have changed since I tried it last time. Samuel. 2006/5/31, İlker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > > Hi Samuel, > > Did you manage to get message rules from im-rules file ? > Do you know which path does SER check if you write the > authorize_message command as in below ? > > if (authorize_message("im-rules.xml")){ > > If you managed to make it work, which client do you use for this ? Did > you make any change in the source ? > > Thanks, > ilker > > -----Original Message----- > From: samuel [mailto:samu60@gmail.com] > Sent: Tuesday, May 16, 2006 10:53 AM > To: İlker Aktuna (Koç.net) > Cc: Vaclav Kubart; serusers(a)iptel.org > Subject: Re: [Serusers] PA error sending notifies > > 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!!) *the namespace is > different (so be carefull in copy&paste from the > presence-rules!!!) and, as Vaclav poitned out "proprietary" from iptel. > > > 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 > > > > -----Original Message----- > > From: serusers-bounces(a)iptel.org > > [mailto:serusers-bounces@iptel.org] On Behalf Of samuel > > Sent: Monday, May 15, 2006 7:13 PM > > To: Vaclav Kubart > > Cc: serusers(a)iptel.org > > Subject: Re: [Serusers] PA error sending notifies > > > > Let's see if I can finish the e-mail before gmail decides it's > > enough...:P > > > > 006/5/15, samuel <samu60(a)gmail.com>: > > > Following with the handbook... > > > > > > > > the authorize message in the sample confgi files has as parameter > > > the xcap root while it should have the xml file containing the > auth.rules. > > > > > > Instead of > > > > > > > > if (authorize_message("http://localhost/xcap")) { > > > > there should be > > > > if (authorize_message("im-rules.xml")){ > > > > > > > > > > > > > > 2006/5/15, samuel <samu60(a)gmail.com>: > > > > First of all, I have to thank you for the time you spent writing > > > > the handbook, it's really really helpfull....I wish all SER > > > > related parts had this docs.. > > > > > > > > I'll try to get familiar with the code of the notifications and > > > > I'll try to find something....which I don't thing so :P. I'll > > > > also merge the two functionalities (proxy + presence) in a > > > > unique config file to see if it works. > > > > I hope I can provide more info these following days. > > > > > > > > About the missing things in the presence handbook, probably the > > > > most important is the new xcap module because in the sample > > > > config files it's missing. > > > > Another thing is that in the XCAP structure description, the > > > > im-rules directory is missing, which might lead to > > > > misunderstandings. I downloaded the structure from the iptel's > > > > ftp and inside the im-rules there were several files > > > > corresponding to presence-rules which should be either removed > > > > or updated with the im-rules namespaces and removing the whitelist. > > > > > > > > Thanks, > > > > > > > > Samuel. > > > > > > > > > > > > > > > > > > > > 2006/5/15, Vaclav Kubart <vaclav.kubart(a)iptel.org>: > > > > > Hi, > > > > > this problem I'm trying to solve with Ilker Aktuna. I try to > > > > > simulate it on my machine and let you know. Or if you solve > > > > > it, please > > let me know. > > > > > :-) > > > > > > > > > > Please, could you tell me, what things you were missing in > > > > > presence handbook? I'm trying to do it as useful as possible > > > > > and whatever ideas are welcome... > > > > > > > > > > Vaclav > > > > > > > > > > On Mon, May 15, 2006 at 01:38:02PM +0200, samuel wrote: > > > > > > Hi all, > > > > > > > > > > > > I recently had a few hours and start installing the presence > > > > > > staff and I have to say that I have it amost workign thanks > > > > > > to the presence handbook, the mailing list and, obviously, a > > > > > > little bit of code review..:P > > > > > > > > > > > > I have two SER instances, the "proxy" and the "presence server" > > > > > > (both with last CVS code) co-located in the same host and I > > > > > > have an issue when the "presence server" tries to send the > > > > > > NOTIFY requests. Below there's an attched log showing the > > > > > > problem (on IP a.b.c.d I've got the two instances): > > > > > > > > > > > > 3(30682) DEBUG notify.c:378: sending winfo notify > > > > > > 3(30682) DEBUG notify.c:383: winfo document created > > > > > > 3(30682) DEBUG notify.c:391: creating headers > > > > > > 3(30682) DEBUG notify.c:398: headers created > > > > > > 3(30682) DEBUG:tm:t_uac: > > > > > > > > next_hop=<sip:a.b.c.d;transport=tcp;ftag=c77b3f33;lr=on> > > > > > > 3(30682) t_uac: no socket found > > > > > > 3(30682) DEBUG notify.c:402: request sent with result -7 > > > > > > 3(30682) ERROR: notify.c:404: Can't send watcherinfo > > > > > > notification (-7) > > > > > > > > > > > > This problem appears in other places, not only in the > > > > > > notifications for winfo so probably there's somthing in the > > > > > > selection of the outgoing socket directing to the local IP. > > > > > > > > > > > > >From the proxy part I just ust t_forward_nonack for the "SIMPLE" > > > > > > messages with record route....maybe adding the port in the > > > > > > record route should help? <http://387555.sigclick.mailinfo.com/sigclick/00090404/000D4808/03034F03/131…> _____________________________________________________________________________________________________________________________________________ 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. _____________________________________________________________________________________________________________________________________________ _____________________________________________________________________________________________________________________________________________ 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

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