sr-users

sr-users@lists.kamailio.org

13 participants
37464 discussions

[Serusers] how to use presence module?
by Henry Jacob 26 May '06

26 May '06

Please forgive my ignorance because I'm new to SER. I want to know if I need to have a external presence server if PA module is compiled into SER. I need to use Presence, but I want to put Presence server/Presence agent into one Linux box. thanks, Henry

2 3

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

26 May '06

Great :) That's good nes for me, because I couldn't make you believe that there was a serious problem :) Now how shall we proceed ? Btw, you'll also have the following error in latest CVS, can you check ? May 25 16:44:57 sesapp /root/ser/sbin/ser[3173]: register_udomain(): Invalid table version (use ser_mysql.sh reinstall) May 25 16:44:57 sesapp /root/ser/sbin/ser[3173]: register_udomain(): Invalid table version (use ser_mysql.sh reinstall) Regards, ilker -----Original Message----- From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] Sent: Thursday, May 25, 2006 4:26 PM To: İlker Aktuna (Koç.net) Cc: serusers(a)iptel.org; samuel Subject: Re: PA error sending notifies I updated to latest CVS sources and I have the same problem now! [Can't send watcherinfo notification (-7)] Vaclav On Wed, May 24, 2006 at 10:45:42AM +0300, ?lker Aktuna (Koç.net) wrote: > Hi Vaclav, > > I want to install and run Ser on an identical linux setup with you to > overcome the notification sending issue (thus presence) That's why I need the library versions that you use. > Also I need to know which version of Debian Sarge you are using. > And your ser snapshot version. > > Can you supply me these information please ? > > Thanks, > ilker > > > ________________________________ > > From: ?lker Aktuna (Koç.net) > Sent: Tuesday, May 23, 2006 5:44 PM > To: 'samuel' > Cc: Vaclav Kubart; serusers(a)iptel.org > Subject: RE: PA error sending notifies > > > > So you are not able to use presence but other traffic (IM, voice etc.) is fine ? > Do you know the xml parser library that your system has installed ? > Vaclav, which library version do you use ? > > Thanks, > ilker > > -----Original Message----- > From: samuel [mailto:samu60@gmail.com] > Sent: Tuesday, May 23, 2006 5:05 PM > To: ?lker Aktuna (Koç.net) > Cc: Vaclav Kubart; serusers(a)iptel.org > Subject: Re: PA error sending notifies > > Unfortunately I had no more time to look into it, so I have no more progress..I just saw that the contact header was not properly parsed and there were problems when selecting the local socket where to send the notifies from...I hope in the following weeks I find some more time to spend on it. > > Samuel. > > > 2006/5/23, ?lker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > > > > > > Hi Samuel, > > > > Did you solve the issue where sending notifies would fail with error > > code -7 ? > > > > "Can't send watcherinfo notification (-7)" > > > > If you solved it can you tell me how ? > > > > I believe the problem is occuring while creating the headers. > > Because in "notify.c" I see that -7 is returned only while creating headers. > > > > Regards, > > ilker > > <http://387555.sigclick.mailinfo.com/sigclick/010C0605/07044406/0B044D02/124…> _____________________________________________________________________________________________________________________________________________ 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

Re: [Serusers] upload script in presence snapshot
by Vaclav Kubart 26 May '06

26 May '06

Look into presence handbook. You have to set LD_LIBRARY_PATH to the path, where are lib_ser_cds.so and others. Vaclav On Thu, May 25, 2006 at 12:08:31PM -0300, Gustavo Moreira wrote: > Ok, that work fine. Thank you. > But now when I'm trying to run ser, I've got a parse problem, do I have to > add an extra package or lib? (I've checked that modules are in > /usr/local/lib/ser/modules/) > Here you have the log: > > > > norris:/# ser > 0(1705) ERROR: load_module: could not open module > </usr/local/lib/ser/modules/dialog.so>: lib_ser_cds.so: cannot open shared > object file: No such file or directory > 0(1705) parse error (36,13-14): failed to load module > 0(1705) ERROR: load_module: could not open module > </usr/local/lib/ser/modules/rls.so>: lib_ser_xcap.so: cannot open shared > object file: No such file or directory > 0(1705) parse error (37,13-14): failed to load module > 0(1705) ERROR: load_module: could not open module > </usr/local/lib/ser/modules/pa.so>: lib_ser_xcap.so: cannot open shared > object file: No such file or directory > 0(1705) parse error (38,13-14): failed to load module > 0(1705) ERROR: load_module: could not open module > </usr/local/lib/ser/modules/presence_b2b.so>: lib_ser_xcap.so: cannot open > shared object file: No such file or directory > 0(1705) parse error (39,13-14): failed to load module > 0(1705) set_mod_param_regex: No module matching <rls> found > 0(1705) parse error (76,21-22): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <rls> found > 0(1705) parse error (77,21-22): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <rls> found > 0(1705) parse error (78,21-22): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <rls> found > 0(1705) parse error (79,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <rls> found > 0(1705) parse error (80,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <rls> found > 0(1705) parse error (81,19-20): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <rls> found > 0(1705) parse error (82,19-20): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <rls> found > 0(1705) parse error (83,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (85,19-20): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (87,19-20): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (89,21-22): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (91,21-22): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (92,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (94,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (95,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (97,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (99,19-20): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (101,19-20): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (103,21-22): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (105,21-22): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <pa> found > 0(1705) parse error (107,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <presence_b2b> found > 0(1705) parse error (110,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <presence_b2b> found > 0(1705) parse error (112,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <presence_b2b> found > 0(1705) parse error (114,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <presence_b2b> found > 0(1705) parse error (116,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <presence_b2b> found > 0(1705) parse error (118,20-21): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <presence_b2b> found > 0(1705) parse error (120,22-23): Can't set module parameter > 0(1705) set_mod_param_regex: No module matching <presence_b2b> found > 0(1705) parse error (122,19-20): Can't set module parameter > 0(1705) parse error (190,32-33): unknown command, missing loadmodule? > > 0(1705) parse error (195,32-33): unknown command, missing loadmodule? > > 0(1705) parse error (201,30-31): unknown command, missing loadmodule? > > 0(1705) parse error (204,24-25): unknown command, missing loadmodule? > > 0(1705) parse error (218,35-36): unknown command, missing loadmodule? > > 0(1705) parse error (222,36-37): unknown command, missing loadmodule? > > 0(1705) parse error (230,26-27): unknown command, missing loadmodule? > > 0(1705) parse error (233,31-32): unknown command, missing loadmodule? > > 0(1705) parse error (246,32-33): unknown command, missing loadmodule? > > 0(1705) parse error (260,36-37): unknown command, missing loadmodule? > > 0(1705) parse error (261,28-29): unknown command, missing loadmodule? > > 0(1705) parse error (282,21-22): unknown command, missing loadmodule? > > 0(1705) parse error (286,24-25): unknown command, missing loadmodule? > > 0(1705) parse error (304,24-25): unknown command, missing loadmodule? > > 0(1705) parse error (312,28-29): unknown command, missing loadmodule? > > ERROR: bad config file (47 errors) > > > > -----Mensaje original----- > De: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > Enviado el: jueves, 25 de mayo de 2006 2:48 > Para: Gustavo Moreira > CC: serusers(a)iptel.org > Asunto: Re: [Serusers] upload script in presence snapshot > > Run "make" in the directory src/upload or you can call a C compiler > (like gcc) directly to the source file. > Vaclav > > On Wed, May 24, 2006 at 11:19:39PM -0300, Gustavo Moreira wrote: > > In the README document included with the presence snapshot (xcap/README) > > says that a script must be created from C source in src/upload. I've got > the > > source but I don't know how to create the script :-P > > > > Could someone help me? > > > > Thanks, > > > > Gustavo. > > > > > _______________________________________________ > > Serusers mailing list > > Serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers

1 0

[Serusers] SER + Asterisk
by Edgar Barbosa 25 May '06

25 May '06

Hi all, I'm trying to deploy a scenario where I have an openser as a sip proxy (taking care of registrations) in front of an asterisk (to handle pstn call routing/billing/etc). Both openser and asterisk authenticate users on the same database, and I'm able to register a UA on both. The problem is when I try to relay calls from openser to asterisk. I always get the following error: SIP/2.0 407 Proxy Authentication Required What am I missing here? My openser.cfg is the following: debug=3 # debug level (cmd line: -dddddddddd) fork=yes #log_stderror=no # (cmd line: -E) # Uncomment these lines to enter debugging mode #fork=no log_stderror=yes listen=192.168.64.102 sip_warning=no #advertised_address=192.168.1.102 reply_to_via=no check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=4 fifo="/tmp/ser_fifo" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database loadmodule "/usr/lib/openser/modules/mysql.so" loadmodule "/usr/lib/openser/modules/sl.so" loadmodule "/usr/lib/openser/modules/tm.so" loadmodule "/usr/lib/openser/modules/rr.so" loadmodule "/usr/lib/openser/modules/maxfwd.so" loadmodule "/usr/lib/openser/modules/usrloc.so" loadmodule "/usr/lib/openser/modules/registrar.so" loadmodule "/usr/lib/openser/modules/nathelper.so" loadmodule "/usr/lib/openser/modules/textops.so" loadmodule "/usr/lib/openser/modules/xlog.so" loadmodule "/usr/lib/openser/modules/auth.so" loadmodule "/usr/lib/openser/modules/auth_db.so" # -- usrloc params -- # Flush every 60 sec modparam("usrloc", "db_mode", 0) # -- auth params -- modparam("auth_db", "db_url", "XXX") modparam("auth_db", "user_column", "accountcode") #modparam("auth_db", "domain_column", "accountcode") modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "secret") # -- replication auth param -- modparam("auth", "secret", "mysecret") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); return; }; if ( msg:len > max_len ) { sl_send_reply("513", "Message too big"); return; }; force_rport(); fix_nated_contact(); if(uri == myself) { if(method == "REGISTER") { # Make sure they are a valid user on our proxy if(!www_authorize("", "astaccount")) { xlog("L_INFO", "Req Auth For %ct, URI = %ru\n"); www_challenge("", "1"); return; }; xlog("L_INFO", "Registered Contact %ct, URI = %ru\n"); save("location"); return; }; }; record_route(); # ------------------------------------------------------------------ # loose-route processing if(loose_route()) { xlog("L_INFO", "loose_route(): Looking up %rm URI %ru from %is\n"); lookup("location"); xlog("L_INFO", "loose_route(): t_relay() %rm to URI %ru\n"); t_relay(); return; }; if(method == "INVITE") { # Assume it came from one of our VoIP phones, all routing is done by Asterisk xlog("L_INFO", "%rm came from a VoIP phone (%is), attempting to authorize %fu\n"); # Make sure they are a valid user on our proxy if (!www_authorize("", "astaccount")) { www_challenge("", "0"); xlog("L_INFO", "Failed to authorize %fu (%is)\n"); return; }; # Found a match, this is going to a VoIP phone xlog("L_INFO", "Auth OK, sending URI %ru to Asterisk for routing\n"); rewritehostport("192.168.64.103:5060"); xlog("L_INFO", "INVITE New URI = %ru, t_relay()ing now\n"); t_relay(); # forward(uri:host, uri:port); return; }; # ------------------------------------------------------------------ # forward to current uri now; use stateful forwarding; that # works reliably even if we forward from TCP to UDP lookup("location"); xlog("L_INFO", "Default t_relay() (method = %rm, URI = %ru, >From = %is)\n"); if(!t_relay()) { xlog("L_INFO", "Failed sending requesting %rm URI (%ru)\n"); sl_reply_error(); }; } Thanks for your help

2 1

[Serusers] Buffer overflow?
by sip 25 May '06

25 May '06

I recently started seeing this in the logs right after a registration attempt from a user who's a on our system, but is somehow storing contact info for a different username on a different service: May 25 12:03:52 death ser[22235]: ERROR: warning_builder: buffer size exceeded May 25 12:03:52 death ser[22235]: WARNING: warning skipped -- too big The register packet that caused it was: REGISTER sip:proxy.ideasip.com:5060;g_id=17476253781;g_dom=proxy01.sipphone.com SIP/2.0. Record-Route: <sip:198.65.XXX.XXX;ftag=31839881;lr>. Via: SIP/2.0/UDP 198.65.XXX.XXX;branch=z9hG4bK1033.75ea1c43.0. Via: SIP/2.0/UDP 192.168.1.18:36560;received=69.91.XXX.XXX;branch=z9hG4bK-d87543-5e7fc69802da2376-1--d87543-;rport=33028. Max-Forwards: 69. Contact: <sip:1747625XXXX@proxy01.sipphone.com:5060>. To: <sip:1101201XXXX@proxy.ideasip.com:5060;g_id=1747625XXXX;g_dom=proxy01.sipphone.com>. From: <sip:1101201XXXX@proxy.ideasip.com:5060;g_id=1747625XXXX;g_dom=proxy01.sipphone.com>;tag=31839881. Call-ID: 7dffe5df6f2a521a@YW50ZXJvb21lbWFjLmxvY2Fs. CSeq: 40 REGISTER. Expires: 1800. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, INFO, NOTIFY, MESSAGE. Supported: ICE. User-Agent: MacGizmo (Gizmo-s2n1)/1.5. Authorization: Digest username="1101201XXXX",realm="proxy.ideasip.com",nonce="4475d66395235de62215f7d44f9dbafc068050f7",uri="sip:proxy.ideasip.com:5060;g_id=1747625XXXX;g_dom=proxy01.sipphone.com",response="2a56661c46fdac2129de3100014e5753",cnonce="aab804aa999687b7",nc=00000003,qop=auth,algorithm=MD5. Content-Length: 0. P-hint: outbound. Any idea what's throwing the error and what causes it? N.

3 4

[Users] 404 not found and 408 request time out.
by raviprakash sunkara 25 May '06

25 May '06

Hi... please help me...... what i need to do This is log log message occurred in softphone END TIME: 5733597 SEND >> 24.98.157.209:5060 REGISTER sip:24.98.157.209 SIP/2.0 v: SIP/2.0/UDP 192.168.2.10:5060 ;rport;branch=z9hG4bK1F1709A8059643318C41CAEA3A92556F f: test <sip:test1@24.98.157.209>;tag=2726274778 t: test <sip:test1@24.98.157.209> m: "test" <sip:test1@192.168.2.10:5060> i: CD5177EE93424854AC1EFCBB8377C934(a)24.98.157.209 CSeq: 33483 REGISTER Expires: 1800 Authorization: Digest username="test1",realm="24.98.157.209 ",nonce="447537969c8cd77b390784061802d25fb1172536",response="494295ffe8019017d090458fe5bd4355",uri="sip: 24.98.157.209" Max-Forwards: 70 User-Agent: X-Lite release 1105x l: 0 RECEIVE TIME: 5734005 RECEIVE << 24.98.157.209:5060 SIP/2.0 200 OK v: SIP/2.0/UDP 192.168.2.10:5060 ;rport=5060;branch=z9hG4bK1F1709A8059643318C41CAEA3A92556F;received= 61.17.248.68 f: test <sip:test1@24.98.157.209>;tag=2726274778 t: test <sip:test1@24.98.157.209>;tag=390c3671353535dcaf504ab6b64ba770.4a87 i: CD5177EE93424854AC1EFCBB8377C934(a)24.98.157.209 CSeq: 33483 REGISTER Contact: <sip:test1@192.168.2.10:5060>;expires=1800 Server: OpenSer (1.0.1-notls (i386/linux)) Content-Length: 0 Warning: 392 192.168.2.101:5060 "Noisy feedback tells: pid=8426 req_src_ip= 61.17.248.68 req_src_port=5060 in_uri=sip:24.98.157.209 out_uri=sip: 24.98.157.209 via_cnt==1" SEND TIME: 5744995 SEND >> 24.98.157.209:5060 INVITE sip:test2@24.98.157.209 SIP/2.0 v: SIP/2.0/UDP 192.168.2.10:5060 ;rport;branch=z9hG4bK94B0A7B9F494421C98C5F0AE70FF77B5 f: test <sip:test1@24.98.157.209>;tag=3426314233 t: <sip:test2@24.98.157.209> m: <sip:test1@192.168.2.10:5060> i: 06861D8C-44D7-44E3-862B-2804B53FF5A0(a)192.168.2.10 CSeq: 40000 INVITE Max-Forwards: 70 c: application/sdp User-Agent: X-Lite release 1105x l: 304 v=0 o=test1 5744982 5744995 IN IP4 192.168.2.10 s=X-Lite c=IN IP4 192.168.2.10 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: 5745404 RECEIVE << 24.98.157.209:5060 SIP/2.0 100 trying -- your call is important to us v: SIP/2.0/UDP 192.168.2.10:5060 ;rport=5060;branch=z9hG4bK94B0A7B9F494421C98C5F0AE70FF77B5;received= 61.17.248.68 f: test <sip:test1@24.98.157.209>;tag=3426314233 t: <sip:test2@24.98.157.209> i: 06861D8C-44D7-44E3-862B-2804B53FF5A0(a)192.168.2.10 CSeq: 40000 INVITE Server: OpenSer (1.0.1-notls (i386/linux)) Content-Length: 0 Warning: 392 192.168.2.101:5060 "Noisy feedback tells: pid=8426 req_src_ip= 61.17.248.68 req_src_port=5060 in_uri=sip:test2@24.98.157.209 out_uri= sip:test2@192.168.2.8:5060 via_cnt==1" RECEIVE TIME: 5745421 RECEIVE << 24.98.157.209:5060 SIP/2.0 404 Not Found v: SIP/2.0/UDP 192.168.2.10:5060;received=61.17.248.68 ;rport=5060;branch=z9hG4bK94B0A7B9F494421C98C5F0AE70FF77B5 f: test <sip:test1@24.98.157.209>;tag=3426314233 t: <sip:test2@24.98.157.209>;tag=3318687206 i: 06861D8C-44D7-44E3-862B-2804B53FF5A0(a)192.168.2.10 CSeq: 40000 INVITE Server: Cisco ATA 188 v3.2.1 atasip (050616A) Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Content-Length: 0 SEND TIME: 5745423 SEND >> 24.98.157.209:5060 ACK sip:test2@24.98.157.209 SIP/2.0 v: SIP/2.0/UDP 192.168.2.10:5060 ;rport;branch=z9hG4bK94B0A7B9F494421C98C5F0AE70FF77B5 f: test <sip:test1@24.98.157.209>;tag=3426314233 t: <sip:test2@24.98.157.209>;tag=3318687206 m: <sip:test1@192.168.2.10:5060> i: 06861D8C-44D7-44E3-862B-2804B53FF5A0(a)192.168.2.10 CSeq: 40000 ACK Max-Forwards: 70 l: 0 -- Thanks and Regards with cheers Sunkara Ravi Prakash (Voip Developer) Hyperion Technology www.hyperion-tech.com <b>

2 1

[Users] 408 and 404 messages
by raviprakash sunkara 25 May '06

25 May '06

Hi Everybody... I'm using openser 1.0.1 and Xlite softphone.. It finely registered and initialized the nathelper moudule just giving the nat_interval and ping_nated_flag parameters. When i tried to makes call I found ..." 404 not found" and 408 Request timeout " messages arrived to me.. I think so problem in NAT only... help me in this please , its very important to me.... Bye -- Thanks and Regards with cheers Sunkara Ravi Prakash (Voip Developer) Hyperion Technology www.hyperion-tech.com <b>

1 0

[Serusers] hello
by rekik refka 25 May '06

25 May '06

hello, I must make some change to ser code and recompile it. So, I'm searching to make some changes to pa module. i'm trying then to send an email to one client to be notified of presence of some contacts. I'm trying with ser_08.12.tar.gz can I think in other persistant changes or continue with my idea. In bith case what can I do that. I'm debutant on Ser. Can you help me. thanks in advance. Refka On 5/25/06, serusers-request(a)lists.iptel.org <serusers-request(a)lists.iptel.org> wrote: > Send Serusers mailing list submissions to > serusers(a)lists.iptel.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.iptel.org/mailman/listinfo/serusers > or, via email, send a message with subject or body 'help' to > serusers-request(a)lists.iptel.org > > You can reach the person managing the list at > serusers-owner(a)lists.iptel.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Serusers digest..." > > > Today's Topics: > > 1. Re: Mediaproxy gets confused (rusl) > 2. Re: Hell Sir please help in SER (Andrey Kouprianov) > 3. How to enable Authentication (Aniruddha Vaidya) > 4. Re: How to enable Authentication (Andrey Kouprianov) > 5. Re: How to enable Authentication (Andrey Kouprianov) > 6. Re: How to enable Authentication (Andrey Kouprianov) > 7. Re: How to enable Authentication (Andrey Kouprianov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 25 May 2006 08:14:41 +0000 > From: rusl <rusl(a)jpfortune.org> > Subject: Re: [Serusers] Mediaproxy gets confused > To: serusers(a)lists.iptel.org > Message-ID: <200605250814.41731.rusl(a)jpfortune.org> > Content-Type: text/plain; charset="iso-8859-1" > > > Hi, just to let everyone know, I found the problem.. In mediaproxy 1.4.2, > they > added a new "feature" which allows the called user to change his media > stream > with a 183, 200 status w/ SDP. But the thing is that usually it's the caller > that initiates a mediachange, so when the caller sent a 200 or 183 for media > change, mediaproxy thought it was the called that had a media change, and > basically connected the caller to itself by saying that the caller was the > called. > > I fixed it by "reversing" the functionality in mediaproxy. > > On Wednesday 24. May 2006 22:04, rusl wrote: > > Hi, I was wondering whether anyone has seen this strange error before. It > > happens intermittently, where mediaproxy gets confused as to who the > > "called" IP is, it thinks the caller is the called and switches back and > > forth. > > > > Any ideas? > > > > rusl.. > > > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 193.xxx.33.xxx:20820 (RTP) (will return to 193.xxx.33.xxx:20820) > > May 24 21:58:08 voice mediaproxy[15520]: session > > 7A99B4CF-725E-0952-8C5A-7C17443072C7(a)192.168.15.3: called signed in from > > 10.2.1.3:6622 (RTP) (will return to 10.2.1.3:6622) > > _______________________________________________ > > Serusers mailing list > > Serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > ------------------------------ > > Message: 2 > Date: Thu, 25 May 2006 16:22:01 +0700 > From: "Andrey Kouprianov" <andrey.kouprianov(a)gmail.com> > Subject: [Serusers] Re: Hell Sir please help in SER > To: serusers(a)iptel.org > Message-ID: > <ab5f5bda0605250222wc43a773ifb9103de26a1b6d5(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, > > proxyIP takes only one IP address. You cannot say > > proxyIP = 81.21.33.35,127.0.0.1 > > Instead try > > proxyIP = 81.21.33.35 > > Then mail me if you have problem. Your ser.cfg seems like the one from > getting started document. It should work just fine. > > > ------------------------------ > > Message: 3 > Date: Thu, 25 May 2006 16:03:33 +0530 > From: "Aniruddha Vaidya" <anir123(a)gmail.com> > Subject: [Serusers] How to enable Authentication > To: Serusers(a)lists.iptel.org > Message-ID: > <7759a74d0605250333x5ae6196ekc780dc3d8d7ff064(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hello All, > I'm trying to enable the authentication feature in SER. But its not accepted > by the server. > This is my ser.cfg file. > > Can you tell me whats wrong ? > > # > # $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 andrei Exp $ > # > # simple quick-start config script > # > > # ----------- global configuration parameters ------------------------ > > #debug=3 # debug level (cmd line: -dddddddddd) > #fork=yes > #log_stderror=no # (cmd line: -E) > > # Uncomment these lines to enter debugging mode > #fork=no > #log_stderror=yes > # > > check_via=no # (cmd. line: -v) > dns=no # (cmd. line: -r) > rev_dns=no # (cmd. line: -R) > port=5060 > children=4 > fifo="/tmp/ser_fifo" > > # ------------------ module loading ---------------------------------- > > # Uncomment this if you want to use SQL database > loadmodule "/usr/local/lib/ser/modules/mysql.so" > > loadmodule "/usr/local/lib/ser/modules/sl.so" > loadmodule "/usr/local/lib/ser/modules/tm.so" > loadmodule "/usr/local/lib/ser/modules/rr.so" > loadmodule "/usr/local/lib/ser/modules/maxfwd.so" > loadmodule "/usr/local/lib/ser/modules/usrloc.so" > loadmodule "/usr/local/lib/ser/modules/registrar.so" > loadmodule "/usr/local/lib/ser/modules/textops.so" > > # Uncomment this if you want digest authentication > # mysql.so must be loaded ! > #loadmodule "/usr/local/lib/ser/modules/auth.so" > #loadmodule "/usr/local/lib/ser/modules/auth_db.so" > > # ----------------- setting module-specific parameters --------------- > > # -- usrloc params -- > > #modparam("usrloc", "db_mode", 0) > > # Uncomment this if you want to use SQL database > # for persistent storage and comment the previous line > modparam("usrloc", "db_mode", 2) > > # -- auth params -- > # Uncomment if you are using auth module > # > modparam("auth_db", "calculate_ha1", yes) > # > # If you set "calculate_ha1" parameter to yes (which true in this config), > # uncomment also the following parameter) > # > modparam("auth_db", "password_column", "password") > > # -- rr params -- > # add value to ;lr param to make some broken UAs happy > modparam("rr", "enable_full_lr", 1) > > # ------------------------- request routing logic ------------------- > > # main routing logic > > route{ > > # initial sanity checks -- messages with > # max_forwards==0, or excessively long requests > if (!mf_process_maxfwd_header("10")) { > sl_send_reply("483","Too Many Hops"); > break; > }; > if (msg:len >= 2048 ) { > sl_send_reply("513", "Message too big"); > break; > }; > > > # we record-route all messages -- to make sure that > # subsequent messages will go through our proxy; that's > # particularly good if upstream and downstream entities > # use different transport protocol > if (!method=="REGISTER") record_route(); > > # subsequent messages withing a dialog should take the > # path determined by record-routing > if (loose_route()) { > # mark routing logic in request > append_hf("P-hint: rr-enforced\r\n"); > route(1); > break; > }; > > if (!uri==myself) { > # mark routing logic in request > append_hf("P-hint: outbound\r\n"); > route(1); > break; > }; > > # if the request is for other domain use UsrLoc > # (in case, it does not work, use the following command > # with proper names and addresses in it) > if (uri==myself) { > > if (method=="REGISTER") { > > # Uncomment this if you want to use digest authentication > if (!www_authorize("<InternalSER>", "subscriber")) { > www_challenge("<InternalSER>", "0"); > break; > }; > > save("location"); > break; > }; > > lookup("aliases"); > if (!uri==myself) { > append_hf("P-hint: outbound alias\r\n"); > route(1); > break; > }; > > # native SIP destinations are handled using our USRLOC DB > if (!lookup("location")) { > sl_send_reply("404", "Not Found"); > break; > }; > }; > append_hf("P-hint: usrloc applied\r\n"); > route(1); > } > > route[1] > { > # send it out now; use stateful forwarding as it works reliably > # even for UDP2TCP > if (!t_relay()) { > sl_reply_error(); > }; > } > > > Thanks, > Aniruddha >

1 0

[Serusers] hello
by rekik refka 25 May '06

25 May '06

Hello, I must make some change to ser code and recompile it. So, I'm searching to make some changes to pa module. i'm trying then to send an email to one client to be notified of presence of some contacts. I'm trying with ser_08.12.tar.gz can I think in other persistant changes or continue with my idea. In bith case what can I do that. I'm debutant on Ser. Can you help me. thanks in advance. Refka

1 0

[Serusers] Re: Hell Sir please help in SER
by Andrey Kouprianov 25 May '06

25 May '06

Hi, Please, just call me Andrey. So, you are using X-lite. Try setting Send Internal IP to "Always". Your contact header fields must contain the NATed IP addressed (that's what that setting will do), but now they are your proxy's. I think, I had this kind of problem before... On 5/25/06, ravi reddy <mravikreddy(a)gmail.com> wrote: > Hello Mr.Andrey Kouprianov > > I made some changes in my mediaproxy and it starts with no errors > in that even i saw in log messages it is perfetly say mediaproxy server is > on and socked is /var/run/mediaproxy.sock > > > and i registerd three users and even now when iam calling there is no > sound in both ways at first i get succsess for only one call and i saw in > sessions.py every thing is o.k but after one hour again i tried but i dont > know what is happening here > > here are some messages i found in ngrep port 5060 > > > 213.149.178.204:5060 -> 81.21.33.35:5060 > SIP/2.0 200 Ok..Via: SIP/2.0/UDP > 81.21.33.35;branch=z9hG4bK471b.a07c0605.0..Via: SIP/2.0/UDP > 81.21.34.34:5060;rport=5060 > ;branch=z9hG4bKC2A7F34D7D1D49139D47222CE36B2163..From: > 32331000 <sip:32331000@81.21.33.35>;tag=630051386..To: <sip:32331 > 002(a)81.21.33.35>;tag=1982025997..Contact: > <sip:32331002@213.149.178.204:5060>..Call-ID: > 9602F577-35D2-4596-BB54-5A28F865 > 6802@192.168.0.77..CSeq: 24309 BYE..Server: X-Lite release > 1105x..Content-Length: 0.... > # > U 81.21.33.35:5060 -> 81.21.34.34:5060 > SIP/2.0 200 Ok..Via: SIP/2.0/UDP > 81.21.34.34:5060;rport=5060;branch=z9hG4bKC2A7F34D7D1D49139D47222CE36B2163..From: > 32331 > 000 <sip:32331000@81.21.33.35>;tag=630051386..To: > <sip:32331002@81.21.33.35>;tag=1982025997..Contact: <sip:32331002@213. > 149.178.204:5060>..Call-ID: > 9602F577-35D2-4596-BB54-5A28F8656802@192.168.0.77..CSeq: > 24309 BYE..Server: X-Lite release 1 > 105x..Content-Length: 0.... > # > U 81.21.34.34:5060 -> 81.21.33.35:5060 > > the phone is connecting fine and when connects i dont hear any sounds > > > Sir, i need your help and iam very desperate to make this sucessfull global > calls i hope you will solve my problem thanks > > kindly regards > Ravi. > > > >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users