sr-users

sr-users@lists.kamailio.org

13 participants
37464 discussions

Re: [Serusers] ser: problems with hearing voice
by Americania .it 27 May '06

27 May '06

>From: Ladislav Andel <ladia6(a)centrum.cz> >To: "Americania .it" <americania(a)hotmail.com> >Subject: Re: [Serusers] ser: problems with hearing voice >Date: Sat, 27 May 2006 01:05:57 +0200 > >Hi, >can you draw your network scenario (just where is SER, SIP phones and NAT >devices in the network) ? It'll be easier to see the problem. >Since you run SER behind NAT (am I right?) nathelper checks for private >addresses {RFC1918) and so the logic of ser.cfg is not then appropriate. >Can you send your ser.cfg? Have you read at onsip.org the getting started >document? > >Next time catch your SIP messages on the server by: >ngrep -d any -W byline -O /tmp/trace.log port 5060 >or >tcpdump -p -s 0 -i any -e port 5060 -w /tmp/trace.log > >Ladislav > >Americania .it wrote: >>I've opened port 8000/8001 on my router .. >> >>I've installed Portrptr to monitor wich ports are used by 3cx Phone (it >>says 5062 5063). >>I've opened 5060 to 5070 udp) too. >>Nothing has changed : no voice. >> >>I've tried XLite : same thing , no voice. >> >>I've tried to make a call from my Lan where Ser is installed to an user >>outside and he can hear me but I can't hear him. >> >>If I enstablish a call from an outside user to another outside user .. no >>voice at all! >> >>I attach X-Lite log for this case: >> >>What can I do now ??? >> >> >> >>SEND TIME: 3474935 >>SEND >> 80.105.2.110:5060 >>INVITE sip:vicky@80.105.2.110 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bK2C92FDF50A36406697C9FDB48723EC39 >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110> >>Contact: <sip:claudio@192.168.0.102:5060> >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 INVITE >>Max-Forwards: 70 >>Content-Type: application/sdp >>User-Agent: X-Lite release 1105x >>Content-Length: 308 >> >>v=0 >>o=claudio 3474591 3474934 IN IP4 192.168.0.102 >>s=X-Lite >>c=IN IP4 192.168.0.102 >>t=0 0 >>m=audio 8000 RTP/AVP 0 8 3 98 97 101 >>a=rtpmap:0 pcmu/8000 >>a=rtpmap:8 pcma/8000 >>a=rtpmap:3 gsm/8000 >>a=rtpmap:98 iLBC/8000 >>a=rtpmap:97 speex/8000 >>a=rtpmap:101 telephone-event/8000 >>a=fmtp:101 0-15 >>a=sendrecv >> >>RECEIVE TIME: 3475635 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 100 trying -- your call is important to us >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport=39267;branch=z9hG4bK2C92FDF50A36406697C9FDB48723EC39;received=62.101.126.230 >> >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110> >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 INVITE >>Server: Sip EXpress router (0.9.4 (i386/linux)) >>Content-Length: 0 >>Warning: 392 10.0.0.133:5060 "Noisy feedback tells: pid=9102 >>req_src_ip=62.101.126.230 req_src_port=39267 in_uri=sip:vicky@80.105.2.110 >>out_uri=sip:vicky@87.1.193.94:5060 via_cnt==1" >> >> >>RECEIVE TIME: 3476404 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 180 Ringing >>Via: SIP/2.0/UDP >>192.168.0.102:5060;received=62.101.126.230;rport=39267;branch=z9hG4bK2C92FDF50A36406697C9FDB48723EC39 >> >>Record-Route: <sip:10.0.0.133;ftag=512156865;lr=on> >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110>;tag=806313b969ebda11a7f5000d613deeec >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 INVITE >>Contact: <sip:vicky@87.1.193.94:5060> >>Max-Forwards: 16 >>Server: SIPPER for 3CX Phone >>Allow: INVITE, ACK, CANCEL, BYE, NOTIFY >>Content-Length: 0 >> >> >>RECEIVE TIME: 3480857 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 200 OK >>Via: SIP/2.0/UDP >>192.168.0.102:5060;received=62.101.126.230;rport=39267;branch=z9hG4bK2C92FDF50A36406697C9FDB48723EC39 >> >>Record-Route: <sip:10.0.0.133;ftag=512156865;lr=on> >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110>;tag=806313b969ebda11a7f5000d613deeec >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 INVITE >>Contact: <sip:vicky@87.1.193.94:5060> >>Max-Forwards: 16 >>Server: SIPPER for 3CX Phone >>Allow: INVITE, ACK, CANCEL, BYE, NOTIFY >>Content-Type: application/sdp >>Content-Length: 261 >> >>v=0 >>o=root 5424921 5424921 IN IP4 192.168.1.2 >>s=call >>c=IN IP4 10.0.0.133 >>t=0 0 >>m=audio 35268 RTP/AVP 0 8 3 97 101 >>a=rtpmap:0 PCMU/8000 >>a=rtpmap:8 PCMA/8000 >>a=rtpmap:3 GSM/8000 >>a=rtpmap:97 iLBC/8000 >>a=rtpmap:101 telephone-event/8000 >>a=nortpproxy:yes >> >>SEND TIME: 3480866 >>SEND >> 10.0.0.133:5060 >>ACK sip:vicky@87.1.193.94:5060 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bK28E629C6EC9342FFA3B89AF152782C9D >>From: claudio <sip:claudio@80.105.2.110>;tag=512156865 >>To: <sip:vicky@80.105.2.110>;tag=806313b969ebda11a7f5000d613deeec >>Contact: <sip:claudio@192.168.0.102:5060> >>Route: <sip:10.0.0.133;ftag=512156865;lr=on> >>Call-ID: 374B53F3-8081-45B1-AD92-4075AF931C00(a)192.168.0.102 >>CSeq: 21421 ACK >>Max-Forwards: 70 >>Content-Length: 0 >> >> >>RECEIVE TIME: 3493387 >>RECEIVE << 80.105.2.110:5060 >> >>SEND TIME: 3500646 >>SEND >> 80.105.2.110:5060 >>REGISTER sip:80.105.2.110 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bKC9C44D63BB0344C4B10F04D9C36AD603 >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio <sip:claudio@80.105.2.110> >>Contact: "claudio" <sip:claudio@192.168.0.102:5060> >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48998 REGISTER >>Expires: 160 >>Max-Forwards: 70 >>User-Agent: X-Lite release 1105x >>Content-Length: 0 >> >> >>SEND TIME: 3502150 >>SEND >> 80.105.2.110:5060 >>REGISTER sip:80.105.2.110 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bKC9C44D63BB0344C4B10F04D9C36AD603 >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio <sip:claudio@80.105.2.110> >>Contact: "claudio" <sip:claudio@192.168.0.102:5060> >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48998 REGISTER >>Expires: 160 >>Max-Forwards: 70 >>User-Agent: X-Lite release 1105x >>Content-Length: 0 >> >> >>RECEIVE TIME: 3502580 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 401 Unauthorized >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport=39267;branch=z9hG4bKC9C44D63BB0344C4B10F04D9C36AD603;received=62.101.126.230 >> >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio >><sip:claudio@80.105.2.110>;tag=2a08c327b8d597781b526eaf86695180.f298 >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48998 REGISTER >>WWW-Authenticate: Digest realm="80.105.2.110", >>nonce="447770198404c4bc9438e9ce6159814a63b777d4" >>Server: Sip EXpress router (0.9.4 (i386/linux)) >>Content-Length: 0 >>Warning: 392 10.0.0.133:5060 "Noisy feedback tells: pid=9102 >>req_src_ip=62.101.126.230 req_src_port=39267 in_uri=sip:80.105.2.110 >>out_uri=sip:80.105.2.110 via_cnt==1" >> >> >>SEND TIME: 3502583 >>SEND >> 80.105.2.110:5060 >>REGISTER sip:80.105.2.110 SIP/2.0 >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport;branch=z9hG4bKC8C6FD549B75482F9BBE53C7AE958465 >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio <sip:claudio@80.105.2.110> >>Contact: "claudio" <sip:claudio@192.168.0.102:5060> >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48999 REGISTER >>Expires: 160 >>Authorization: Digest >>username="claudio",realm="80.105.2.110",nonce="447770198404c4bc9438e9ce6159814a63b777d4",response="24188c3172d488f1296a7c2ad2a048d6",uri="sip:80.105.2.110" >> >>Max-Forwards: 70 >>User-Agent: X-Lite release 1105x >>Content-Length: 0 >> >> >>RECEIVE TIME: 3502841 >>RECEIVE << 80.105.2.110:5060 >>SIP/2.0 200 OK >>Via: SIP/2.0/UDP >>192.168.0.102:5060;rport=39267;branch=z9hG4bKC8C6FD549B75482F9BBE53C7AE958465;received=62.101.126.230 >> >>From: claudio <sip:claudio@80.105.2.110>;tag=425214505 >>To: claudio >><sip:claudio@80.105.2.110>;tag=2a08c327b8d597781b526eaf86695180.24dd >>Call-ID: 63C1074ADB2E448487DECC8994F610F3(a)80.105.2.110 >>CSeq: 48999 REGISTER >>Contact: <sip:claudio@62.101.126.230:39267>;expires=160 >>Server: Sip EXpress router (0.9.4 (i386/linux)) >>Content-Length: 0 >>Warning: 392 10.0.0.133:5060 "Noisy feedback tells: pid=9102 >>req_src_ip=62.101.126.230 req_src_port=39267 in_uri=sip:80.105.2.110 >>out_uri=sip:80.105.2.110 via_cnt==1" >> >>____________________________________________________________________________ >> >>____________________________________________________________________________ >> >> >> >> >>>From: "Andrey Kouprianov" <andrey.kouprianov(a)gmail.com> >>>To: serusers(a)iptel.org >>>Subject: Re: [Serusers] ser: problems with hearing voice >>>Date: Wed, 24 May 2006 00:24:05 +0700 >>> >>>Yes you do. RTP (for voice and video) protocol normally uses ports >>>8000 for media transfer and 8001 for media control. If you are using >>>X-lite, then port 8000 is used definitely. A client like eyeBeam, may >>>choose from range of ports (i dont really know which exactly, but I >>>always see ports in the range of 6000-7000). And Skype, for instance, >>>can use ANY port available. >>> >>>Anyway, you can monitor ports <= 1024 and open the rest. Those are >>>well known and they are the target. There are some ports > 1024 that >>>Windows uses for it's services and you might want to find our what >>>those (because, i dont really know :) are and monitor them as well. >>> >>>Good luck. >>> >>>On 5/23/06, Americania .it <americania(a)hotmail.com> wrote: >>>>Hi, >>>>I can' hear any voice when I call from a pc outside the Lan where ser >>>>is >>>>installed (I've got a router-firewall): I've port 5060 UDP/TCP >>>>forwarded to >>>>my ser server . >>>>Do I have to open other ports ? >>>> >>>>Thanks >>>> >>>> >>>>_______________________________________________ >>>>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 >> >> >

1 0

Re: [Users] Forward SUBSCRIBER
by Bogdan-Andrei Iancu 26 May '06

26 May '06

Javier, you just have to extend the script a little bit: if the RURi is for your server, do routing based on location; if not (uri!=myself), just relay it - it will be sent based on domain name to the right proxy. regards, bogdan Javier Ramirez wrote: > ok, thak you > but, if I use 2 OpenSER, how to do this ? > > A@OSER1 <mailto:A@OSER1> add B@OSER2 <mailto:B@OSER2> > > > Example: > > > User A OSER 1 OSER 2 User B > |---SUBSCRIBER--------->| > | | > | |-----SUBSCRIBER > ---------->| | > | > | |------SUBSCRIBER --->| > | > > > lookup(location) is 0 because B is not registered in A, so > sl_send_reply send 404. > > Best Regards > Javier Ramirez > > > > ----- Original Message ----- > *From:* Bogdan-Andrei Iancu <mailto:bogdan@voice-system.ro> > *To:* Javier Ramirez <mailto:jvr_78@yahoo.com.ar> ; users > openser.org <mailto:users@openser.org> > *Sent:* Friday, May 26, 2006 11:47 AM > *Subject:* Re: [Users] Forward SUBSCRIBER > > Javier, > > with or without the PA, all the messages will go via your OpenSER... > > if you just want to " > when A user add B user, send a SUBSCRIBER to OpenSER, > I need that the OpenSER forward this SUBSCRIBER to B user. > " > you do not need the PA. > > as I told you before, just to: > if (is_method("SUBSCRIBE")) { > if (lookup("location")) { > t_relay(); > } else { > sl_send_reply("404","Not Found"); > } > exit; > } > > regards, > bogdan > > Javier Ramirez wrote: > > > Hi Bogdan, > > I like use PA module for presence, > > the users talk only with the PA, the users use OUTBOUND proxy. > > when A user add B user, send a SUBSCRIBER to OpenSER, > > I need that the OpenSER forward this SUBSCRIBER to B user. > > > > > > when I coment the "break;" the SUBSCRIBER message is forward to > B user. > > if I don´t coment the break, the SUBSCRIBER end in OpenSER. > > if (method=="SUBSCRIBE") { > > if (!t_newtran()) { > > sl_reply_error(); > > }; > > handle_subscription("registrar"); > > # break; > > }; > > best Regards > > Javier Ramirez > > > > __________ NOD32 1.1560 (20060526) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com >

1 0

[Users] SQL query to generate CDR out of ACC logs
by Script Head 26 May '06

26 May '06

Does anyone have a query that'd generate some sort of a CDR out of ACC log table? Supposely it's been posted before but I've looked thru the archives and didn't find it.

4 3

[Serusers] Hello
by rekik refka 26 May '06

26 May '06

Hi, I'm trying to compile SER with silomail module. I have download silomail module but how can I do to insert it to SER. Also, this module depend on libldap.so This library must be installed before running SER with silomail module. How can I install this library. Thanks you in advance.

1 0

Re: [Users] Forward SUBSCRIBER
by Bogdan-Andrei Iancu 26 May '06

26 May '06

Javier, with or without the PA, all the messages will go via your OpenSER... if you just want to " when A user add B user, send a SUBSCRIBER to OpenSER, I need that the OpenSER forward this SUBSCRIBER to B user. " you do not need the PA. as I told you before, just to: if (is_method("SUBSCRIBE")) { if (lookup("location")) { t_relay(); } else { sl_send_reply("404","Not Found"); } exit; } regards, bogdan Javier Ramirez wrote: > Hi Bogdan, > I like use PA module for presence, > the users talk only with the PA, the users use OUTBOUND proxy. > when A user add B user, send a SUBSCRIBER to OpenSER, > I need that the OpenSER forward this SUBSCRIBER to B user. > > > when I coment the "break;" the SUBSCRIBER message is forward to B user. > if I don´t coment the break, the SUBSCRIBER end in OpenSER. > if (method=="SUBSCRIBE") { > if (!t_newtran()) { > sl_reply_error(); > }; > handle_subscription("registrar"); > # break; > }; > best Regards > Javier Ramirez

1 0

[Users] Record Route
by raviprakash sunkara 26 May '06

26 May '06

Hi Users.. Please solve my issue. That I want To write the " Record Route " program in openser.cfg file. Give any clues or where i can find.. or give one sample program.... Bye.... -- Thanks and Regards with cheers Sunkara Ravi Prakash (Voip Developer) Hyperion Technology www.hyperion-tech.com <b>

2 1

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

26 May '06

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/070845 > 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/010A4F03/232…> _____________________________________________________________________________________________________________________________________________ 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] Authorizing IM requests
by İlker Aktuna (Koç.net) 26 May '06

26 May '06

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/07084503/061…> _____________________________________________________________________________________________________________________________________________ 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] Re: Serusers request
by Vaclav Kubart 26 May '06

26 May '06

Interesting. There are some examples and documentation (may be "a bit" out of date) of creating modules. Try to search archives of this mailing list. Vaclav On Fri, May 26, 2006 at 01:43:45PM +0200, rekik refka wrote: > Hi, > I have download silomail 1.0 for SER 0.8.14. > This ser module allows sending a SIP instant message as regular e-mail. Such > a feature may be useful for clients that are incapable of receiving SIP > instant messages. Users with such clients can receive SIP instant messages > using regular e-mail instead. > I'm searching to make some modifications to this. > But how can I insert it with SER 0.814. > I have no idea how to add a new module and compile it. > Can you help me. > thanks in advance!

1 0

[Users] Dispatcher failure route
by Benjamin Lawetz 26 May '06

26 May '06

Hello all, I'm setting up a load balancer using openser. The load balancing works great and I'm now trying to work out the redundancy side of it. In my route I have: if (method=="INVITE") { record_route(); ds_select_dst("1", "0"); t_on_failure("1"); t_relay(); } This works fine in that if the selected server is not up or takes too long to answer, the call is route to failure_route[1] And here's where I'm scratching my head. I would like the INVITE to be tried on another server from the server farm. But how. Is there a way to send it back to ds_select_dst and make sure it doesn't get sent back to the same server? thanks

2 2

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