sr-users May 2006

sr-users@lists.kamailio.org

195 participants
502 discussions

Re: [Serusers] Two PSTN gateway providers needs different prefix
by Ryan Pagquil 31 May '06

31 May '06

Hi Andrey, I want SER the one to append the prefix on the Request URI. I think this fits when the user appends a prefix... Any suggestion? Thanks, Ryan At 05:22 PM 5/26/2006, Andrey Kouprianov wrote: >how about this... dont use # key. just append 3333 or 4444 to the number, i.e. > >GW1 ---> 3333<phone number> >GW2 ---> 4444<phone number> > > >if(uri=~"^sip:3333.*") { > strip(4); #if you need to get rid of first 4 >digits (i.e. "3333") > t_relay_to_udp("gw1.ip.address", "gw1-port") ; >} >else if(uri=~"^sip:4444.*") { > strip(4); #if you need to get rid of first 4 >digits (i.e. "4444") > t_relay_to_udp("GW2.ip.address", "GW2-port"); >}; > > >Hope that works out for you. > > >On 5/26/06, Ryan Pagquil <rpagquil(a)philonline.com> wrote: >>Hi, >> Anyone has any idea on how to do this? >> >>Please help.... >> >>Thanks, >>Ryan >> >> >> >>At 11:15 AM 5/25/2006, Ryan Pagquil wrote: >> >Hi SER users, >> > >> > I have a problem. We have two PSTN gateway providers and >> > both of them needs different prefixes when sending request to >> their gateway. >> > >> > For example: >> > GW1 ---> 3333#<phone number> >> > GW2 ---> 4444#<phone number> >> > >> >Now I'll be using these two provider with LCR, but I don't know how >> >will I accomplish their requirements on their prefixes. Could you >> >give me any idea about this scenario? Also how can I make LCR to >> >failover with these gateways? >> > >> >Please help.... >> > >> >Thanks in advance, >> >Ryan Pagquil >> > >> > >> > >> >_______________________________________________ >> >Serusers mailing list >> >Serusers(a)lists.iptel.org >> >http://lists.iptel.org/mailman/listinfo/serusers >> >> >>_______________________________________________ >>Serusers mailing list >>Serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers

2 4

[Users] new MediaProxy release 1.7.2
by Adrian Georgescu 31 May '06

31 May '06

Hello, There is a new MediaProxy release available. The change log is available at http://mediaproxy.ag-projects.com/Changelog. Beside bug fixes a new accounting features has been introduced. To upgrade go to http://mediaproxy.ag-projects.com/ or download the software directly from: http://mediaproxy.ag-projects.com/mediaproxy-1.7.2.tar.gz Kind regards, Adrian Georgescu

3 3

[Serusers] i can register now
by ravi reddy 31 May '06

31 May '06

Thank you very much now i can register soft phones immediately after changing the listening ports of phones Thank you Regards Ravi

1 0

[Serusers] Re: Authorizing IM requests
by Vaclav Kubart 31 May '06

31 May '06

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 > > > > > > > > > > > >-----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? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >_______________________________________________________________ > > > > > >__ > > > > > >__ > > > > > >_______________________________________________________________ > > > > > >__ __ _______ 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/05090E04/0C024D08/0708 > > > 45 > > > 03/06191971.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/000A0404/02044D0A/010A4F > > 03/23231711.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/07090307/00054909/02014800/141…> > _____________________________________________________________________________________________________________________________________________ > 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. > _____________________________________________________________________________________________________________________________________________

1 0

[Serusers] (no subject)
by S.A.S. Lorensuhewa 31 May '06

31 May '06

Dear all, After starting Mysql and Ser OI got following error message in the /var/log/messages. Can somebody comment on this? Aruna ay 31 10:23:20 orange kernel: audit(1149049400.859:330): avc: granted { execmem } for pid=2621 comm="ser" scontext=root:system_r:unconfined_t:s0-s0:c0.c255 tcontext=root:system_r:unconfined_t:s0-s0:c0.c255 tclass=process May 31 10:23:20 orange ser[2623]: connect_db(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111) May 31 10:23:20 orange ser[2623]: db_init(): Error while trying to connect database May 31 10:23:20 orange ser[2623]: mod_init(): Error while connecting database May 31 10:23:20 orange ser[2623]: init_mod(): Error while initializing module usrloc May 31 10:23:55 orange kernel: audit(1149049435.081:331): avc: granted { execstack } for pid=2752 comm="ser" scontext=root:system_r:initrc_t:s0 tcontext=root:system_r:initrc_t:s0 tclass=process May 31 10:23:55 orange kernel: audit(1149049435.081:332): avc: granted { execmem } for pid=2752 comm="ser" scontext=root:system_r:initrc_t:s0 tcontext=root:system_r:initrc_t:s0 tclass=process ---------------------------------------------------------- S. A. S. Lorensuhewa Head, Department of Computer Science University of Ruhuna, Matara, Sri Lanka Telephone: 0094 (0)41 2227019 Fax: 0094 (0)41 2222683 Email: lorensuhewa(a)cc.ruh.ac.lk, aruna(a)cc.ruh.ac.lk

2 1

[Serusers] Problem : Forwarding Routine to a NAT'd endpoint.
by Ricardo Martinez 31 May '06

31 May '06

Hello List I have a problem forwarding a number for a NAT'd endpoint. The problem presents as follow. For incoming calls to my SER users i load via avp_load_radius("callee") the "forward options" for my users. For example if a user has set the Call Forward ON and the set the forwarded number, these options are loaded via avp_radius. So for a incoming call to a user with Call Forward ON, the call is then redirected to a Asterisk Box to handle the call. I have no problem with this if the user is not NAT'd, even if is NAT'd but the user is not registered i can forward the call to my Asterisk Box via a special route (route[8]) without any problem. But if the NAT'd endpoint is REGISTERED in my ser BOX like this : aor : '5507515800' ~~~Contact(0x404cb198)~~~ domain : 'location' aor : '5507515800' Contact : 'sip:5507515800@192.168.1.100:5061' Expires : 595 q : Call-ID : '17b73476-132fa250(a)192.168.1.100' CSeq : 2 User-Agent: 'Linksys/PAP2-3.1.3(LS)' received : 'sip:111.76.148.248:46139' State : CS_NEW Flags : 1 next : (nil) prev : (nil) I'm even using rewritehostport (as indicated in my ser.cfg snipet) route[8] { xlog("L_INFO", "[%Tf] : Ruta [8] Enviando llamada a asterisk\n"); rewritehostport("111.76.154.101:5060"); route(4); route(1); } the call is re-routed to the "received" parameter indicated in the register RECORD. Please check the next debug taken in my ser box. 111.76.148.237 : Caller Endpoint 111.76.148.246 : SER Box 111.76.148.101 : Asterisk Box 111.76.148.248 : Called Enpoint (NAT'd) U 111.76.148.237:5060 -> 111.76.148.246:5060 INVITE sip:5507515800@sipvoiss.desa.redvoiss.net:5060 SIP/2.0. Via: SIP/2.0/UDP 111.76.148.237:5060;branch=z9hG4bKf50b1f9ca. Max-Forwards: 70. Content-Length: 304. To: sip:5507515800@sipvoiss.desa.redvoiss.net:5060. From: sip:2408100@111.76.148.237:5060;tag=acee04f44a858c7. Call-ID: 12524b29b2c08e262bc8daef67f6dcf0(a)111.76.148.237. CSeq: 1032746828 INVITE. Supported: timer. Content-Type: application/sdp. Contact: sip:2408100@111.76.148.237:5060. Supported: replaces. . v=0. o=MxSIP 0 26 IN IP4 111.76.148.237. s=SIP Call. c=IN IP4 111.76.148.237. t=0 0. m=audio 4978 RTP/AVP 18 4 4 101. a=rtpmap:18 G729/8000. a=rtpmap:4 G723/8000. a=rtpmap:4 G723/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:18 annexb=no. a=fmtp:101 0-15. a=sendrecv. m=image 4980 udptl t38. a=sendrecv. U 111.76.148.246:5060 -> 111.76.148.237:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 111.76.148.237:5060;branch=z9hG4bKf50b1f9ca. To: sip:5507515800@sipvoiss.desa.redvoiss.net:5060. From: sip:2408100@111.76.148.237:5060;tag=acee04f44a858c7. Call-ID: 12524b29b2c08e262bc8daef67f6dcf0(a)111.76.148.237. CSeq: 1032746828 INVITE. Server: Sip EXpress router (0.9.3 (i386/linux)). Content-Length: 0. Warning: 392 111.76.148.246:5060 "Noisy feedback tells: pid=22321 req_src_ip=111.76.148.237 req_src_port=5060 in_uri=sip:5507515800@sipvoiss.desa.redvoiss.net:5060 out_uri=sip:75755507515800@111.76.154.101:5060 via_cnt==1". . U 111.76.148.246:5060 -> 111.76.148.248:46139 INVITE sip:75755507515800@111.76.154.101:5060 SIP/2.0. Record-Route: <sip:111.76.148.246;ftag=acee04f44a858c7;lr=on>. Via: SIP/2.0/UDP 111.76.148.246;branch=z9hG4bK38bc.f157bcd5.0. Via: SIP/2.0/UDP 111.76.148.237:5060;branch=z9hG4bKf50b1f9ca. Max-Forwards: 16. Content-Length: 306. To: sip:5507515800@sipvoiss.desa.redvoiss.net:5060. From: sip:2408100@111.76.148.237:5060;tag=acee04f44a858c7. Call-ID: 12524b29b2c08e262bc8daef67f6dcf0(a)111.76.148.237. CSeq: 1032746828 INVITE. Supported: timer. Content-Type: application/sdp. Contact: sip:2408100@111.76.148.237:5060. Supported: replaces. . v=0. o=MxSIP 0 26 IN IP4 111.76.148.237. s=SIP Call. c=IN IP4 111.76.148.246. t=0 0. m=audio 35068 RTP/AVP 18 4 4 101. a=rtpmap:18 G729/8000. a=rtpmap:4 G723/8000. a=rtpmap:4 G723/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:18 annexb=no. a=fmtp:101 0-15. a=sendrecv. m=image 35070 udptl t38. a=sendrecv. Why SER is routing the call to the "received" ip address insted of the ip address indicated in my route[8] by the rewritehostport("111.76.154.101:5060"); ??? Hope that someone can help me here Is there a way to avoid this ? Thanks ! Ricardo Martinez

2 1

[Serusers] Radius accounting howto
by İlker Aktuna (Koç.net) 30 May '06

30 May '06

Hi everyone, I am trying to use acc_radius module with presence CVS sources. I compiled the radiusclient library and compiled ser with acc_radius module. Then I added following lines to the config: loadmodule "/root/ser/lib/ser/modules/acc_radius.so" modparam("acc_radius", "radius_config", "/usr/local/etc/radiusclient-ng/radiusclient.conf") modparam("acc_radius", "service_type", 15) modparam("acc_radius", "radius_flag", 1) modparam("acc_radius", "radius_missed_flag", 3) modparam("acc_radius", "report_ack", 0) But when I try to start ser, it doesn't accept 2 parameters: modparam("acc_radius", "radius_flag", 1) modparam("acc_radius", "radius_missed_flag", 3) What should be the correct syntax for these parameters ? are they required ? And what else should I add to the configuration to send radius-start and radius-stop messages to the radius server ? Thanks, ilker <http://387555.sigclick.mailinfo.com/sigclick/010D0404/07044A01/04044F03/925…> _____________________________________________________________________________________________________________________________________________ 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] mediaproxy 1.7.2 start problems
by Andrey Kouprianov 30 May '06

30 May '06

Hi, I have tried to install mediaproxy 1.7.2. So, i did. Configuration was about the same as 1.4.2, however, "mediaproxy start", just started mediaproxy.py, but not proxydispatcher.py. Version 1.4.2 started them both w/o any problem. Trying to start proxydispatcher.py independently did not give any results. /var/run/proxydispatcher.sock is simply not there anymore. There are no logs or whatsoever, that I could show you, because I did not find any. Anyway, here's the config (NOTE: mediaproxy's running on the same machine as SER): [Dispatcher] start = yes socket = /var/run/proxydispatcher.sock listen = <my IP address> group = wheel defaultProxy = /var/run/mediaproxy.sock [MediaProxy] start = yes socket = /var/run/mediaproxy.sock group = wheel listen = <my IP address> allow = <my IP address>, 127.0.0.1 proxyIP = <my IP address> portRange = 60000:65000 TOS = 0xb8 idleTimeout = 60 holdTimeout = 3600 forceClose = 10800 [Accounting] dbaccounting = off //<my IP address> is IP of SER/mediaproxy machine // the rest is irrelevant Please, also note that I dont have a DNS SRV entry for media proxy. Could that cause the problem? One way or another, I had to downgrade back to 1.4.2. Any suggestions? Thanx in advance. Andrey.

1 0

[Users] How to Work on Accounting in Openser + radius
by raviprakash sunkara 30 May '06

30 May '06

Hi Everybody, I need help from you users, That How can we perform the accouting in Openser and Radius, That I want database should in radius + mysql with openser . In openser if I add " save("acc") its give error as " reinstall ser_mysql.sh " how can we do that... And I follow this "http://openser.org/docs/openser-radius-1.0.x.html " for integrating openser + radius But I wnat really how cam we integrate the " opensaer + radius + mysql " with hints or sample file -- Thanks and Regards with cheers Sunkara Ravi Prakash (Voip Developer) Hyperion Technology www.hyperion-tech.com <b>

1 0

RE: [Serusers] mysql configuration issue
by Benjamin.George＠t-systems.com 30 May '06

30 May '06

Hi, I put the debug on now and started getting debug messages. The error which I am getting now is pasted below: root@ubuntu:/usr/local/etc/ser # ser start Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 10.25.119.97 [10.25.119.97]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 10.25.119.97 [10.25.119.97]:5060 Aliases: tcp: ubuntu:5060 tcp: localhost:5060 tcp: localhost.localdomain:5060 udp: ubuntu:5060 udp: localhost:5060 udp: localhost.localdomain:5060 stateless - initializing 0(0) Maxfwd module- initializing textops - initializing 0(0) new_connection(): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 0(0) db_init(): Could not create a connection 0(0) ERROR: auth_db_ver: unable to open database connection 0(0) auth_db:str_fixup(): Error while querying table version 0(0) ERROR: fix_expr : fix_actions error ERROR: error -1 while trying to fix configuration What might be the possible reason for this error? Can anyone help me out to solve this issue or it will be great if someone throw some light on why this error happens while starting SER with MySql. Thanks, Benjamin. -----Original Message----- From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Andrey Kouprianov Sent: Monday, May 29, 2006 7:36 PM To: serusers(a)iptel.org Subject: Re: [Serusers] mysql configuration issue what does /var/log/messages say? On 5/29/06, Benjamin.George(a)t-systems.com <Benjamin.George(a)t-systems.com> wrote: > Hi, > Thanks for the reply! > > My installed SER version is >0.9.x. Anyway, my issue is not with presence server for the time being. Before experimenting with presence server, I have to complete the mysql configuration with SER. I ran the script to create the Ser DB and tables. It went successfully and all the tables got created. After this, I modified the ser.cfg file to configure mysql with SER (.cfg file is attached). After these modifications, ser -c command was executed and I got an error related to libmysqlclient.so.12. Then I created a soft link to libmysqlclient.so.10. After this, ser -c command was through but when I tried to start the server, it is not getting started. I could not understand the real issue why the SER server is not getting started. I have to configure the mysql to continue my experiments with presence server. It will be great if somebody can get me some pointers on configuring mysql with SER. Some links or tutorials are also well being appreciated. > Thanks, > Benjamin > > -----Original Message----- > From: Andrey Kouprianov [mailto:andrey.kouprianov@gmail.com] > Sent: Monday, May 29, 2006 12:39 PM > To: serusers(a)iptel.org > Subject: Re: [Serusers] mysql configuration issue > > you have installed version <= 0.9.x. This version doesnt have any > presence support, except simply forwarding presence/IM messages back > and forth. What you need is to install ser with presence. it's still > unstable, but try it anyway. > > ftp.iptel.org/pub/ser/presence/ > > > On 5/29/06, Benjamin.George(a)t-systems.com <Benjamin.George(a)t-systems.com> wrote: > > > > > > > > Hi , > > > > > > > > I am a new user of SER and last week only I started installing and > > configuring SER to deploy some presence based applications on top of SER. I > > am finiding some configuration issues with mysql and SER. I installed SER > > and registerd users (X-Lite) successfully. After that I installed mysql to > > store all registration and other information to database instead of in RAM. > > After mysql installation, I ran the script to create the Ser database and > > tables for SER, every thing got craeted successfully. Then the lines > > mentioned to uncomment to use mysql also has been uncommented in ser.cfg > > file. But when I registerd the users again, I could not see any users in the > > table subsriber. It will be great if somebody can throw some light in to > > this issue so that I could complete my mysql configuration with Ser. What > > extra configuration has to be done in ser.cfg file to use mysql? > > > > > > > > Thanks in advance, > > > > Benjmain. > > > > > > _______________________________________________ > > Serusers mailing list > > Serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > _______________________________________________ > Serusers mailing list > Serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > > > > _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

2 1

← Newer
1
2
3
4
5
6
7
8
...
51
Older →

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