sr-users December 2005

sr-users@lists.kamailio.org

158 participants
312 discussions

by Yong, Chee Yeew

Hello, First of all, I hope this is the correct forum to post this; if not, please correct me. :) Secondly, I am having problems make-ing the CVS version downloaded from the pserver (sip_router). I have posted the errors below. If anyone can help, please advise. Thanks. Chee ======================== The errors that I am experiencing: /usr/bin/ld: cannot find -lxcap collect2: ld returned 1 exit status make[1]: *** [pa.so] Error 1 avpops.c:138: warning: initialization from incompatible pointer type avpops.c:139: warning: initialization from incompatible pointer type avpops.c:140: warning: initialization from incompatible pointer type avpops.c:141: warning: initialization from incompatible pointer type avpops.c:144: warning: initialization from incompatible pointer type avpops.c: In function `fixup_db_avp': avpops.c:277: error: incompatible types in assignment avpops.c:278: error: invalid operands to binary == avpops.c:282: error: invalid type argument of `->' avpops.c:282: error: cannot convert to a pointer type avpops.c:283: error: invalid type argument of `->' avpops.c:284: error: invalid type argument of `->' avpops.c: In function `fixup_write_avp': avpops.c:429: error: incompatible types in assignment avpops.c:430: error: invalid operands to binary == avpops.c:436: error: invalid type argument of `->' avpops.c:436: error: cannot convert to a pointer type avpops.c:437: error: invalid type argument of `->' avpops.c:438: error: invalid type argument of `->' avpops.c:439: error: invalid type argument of `->' avpops.c:440: error: invalid type argument of `->' avpops.c:440: error: invalid type argument of `->' avpops.c:440: error: invalid type argument of `->' avpops.c:440: error: invalid type argument of `->' avpops.c:440: error: invalid type argument of `->' avpops.c:440: error: invalid type argument of `->' avpops.c:440: error: invalid type argument of `->' avpops.c:440: error: invalid type argument of `->' avpops.c: In function `fixup_pushto_avp': avpops.c:583: error: incompatible types in assignment avpops.c:584: error: invalid operands to binary == avpops.c:589: error: invalid type argument of `->' avpops.c:589: error: cannot convert to a pointer type avpops.c:590: error: invalid type argument of `->' avpops.c:591: error: invalid type argument of `->' avpops.c: In function `fixup_check_avp': avpops.c:679: error: invalid type argument of `->' avpops.c:679: error: invalid type argument of `->' avpops.c:679: error: invalid type argument of `->' avpops.c:679: error: invalid type argument of `->' avpops.c:679: error: invalid type argument of `->' avpops.c:679: error: invalid type argument of `->' avpops.c:679: error: invalid type argument of `->' avpops.c:679: error: invalid type argument of `->' avpops.c:681: error: invalid type argument of `->' avpops.c:684: error: invalid type argument of `->' avpops.c:684: error: invalid type argument of `->' avpops.c:684: error: invalid type argument of `->' avpops.c:684: error: invalid type argument of `->' avpops.c:684: error: invalid type argument of `->' avpops.c:684: error: invalid type argument of `->' avpops.c:684: error: invalid type argument of `->' avpops.c:684: error: invalid type argument of `->' avpops.c:689: error: incompatible type for argument 2 of `qm_free' avpops.c:690: error: incompatible types in assignment make[1]: *** [avpops.o] Error 1 make[1]: *** No targets specified and no makefile found. Stop. make[1]: *** No targets specified and no makefile found. Stop. make[1]: *** No targets specified and no makefile found. Stop. ================================ ******************************************************************************* This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may not be divulged to any third party without the express permission of the originator. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thales Research & Technology (UK) Limited. *******************************************************************************

18 years, 11 months

[Users] AVPops question

by Joachim Fabini

Hi, Is there a way or workaround to generate AVPs with header values as AVP name? It seems to me that the current AVP concept defines the AVPs at OpenSER startup, so header-value-based names are not feasible. What I need is the following: Store/retrieve a (key,value) pair where the key is the current message's call-id and the value some combination of header values and pseudo- variables. e.g. use the ops avp_printf("$hdr(call-id)", "$hdr(call-id)-$Ts"); avp_pushto("$Myheader","$hdr(call-id)"); in order to append the following header to the SIP message: Myheader: 23459(a)10.0.0.1-4235627623 Any idea how to do this in OpenSER? thanks in advance --Joachim

18 years, 11 months

RE: [Users] mysql cluster and openser

by Maria Yndefors

Yes I have testing/unstable on both machines, one which run SER and one which I have installed Openser. Regards /Maria > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: den 14 december 2005 20:59 > To: Maria Yndefors > Cc: users(a)openser.org > Subject: Re: [Users] mysql cluster and openser > > > Hi Maria, > > what debian version package are you using? unstable or...? > > regards, > bogdan > > Maria Yndefors wrote: > > >Hallo, > >I run openser on a debian used the deb package to install it. > >I have a ndb-cluster setup that I have used successfully > with SER 0.9.4, now I have tested to install openser and I > >can't manage to get the openser mysql module to find the > correct libmysql. > > > >I have: > > > >/usr/lib/libmysqlclient.so.12 > >/usr/lib/libmysqlclient.so.15 > > > >I have tried with a softlink from libmysql.so.10 but I don't manage. > >What is the difference from standard SER and openser mysql module? > > > >Regards > >/Maria > > > > > > > >Maria Yndefors > >_______________________________________________________________ > >System Management & Development > >BREDBANDSBOLAGET / B2 Bredband AB > >Direct: +46 (0)8 50 69 83 80 > >Mobile: +46 (0)7 33 81 92 51 > >Fax: +46 (0)8 54 90 46 08 > >http://www.bredband.com > >_______________________________________________________________ > > > > > >_______________________________________________ > >Users mailing list > >Users(a)openser.org > >http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > > >

18 years, 11 months

Re: [Serusers] need help with ser-0.9.4 and SUBSCRIBE requests

by Vaclav Kubart

Hi, I recommend the CVS version or - may be better - latest version from "presence snapshot" (ftp://ftp.iptel.org/pub/ser/presence/). Vaclav On Thu, 15 Dec 2005, Ekaterina Ivannikova wrote: > Hello, > > I just tried Windows Messenger 5.1 (tcpdump follows), but ser produces the > same error as for 4.7. Could the list members please advise which version > of ser should I use to make SUBSCRIBE requests of WM work ? > > Regards, > > Ekaterina > > ~~~~~~~~~~~~~~~~~~ > REGISTER sip:gutatelecom.ru SIP/2.0 > Via: SIP/2.0/UDP 10.123.0.190:12479 > Max-Forwards: 70 > From: <sip:kate@gutatelecom.ru>;tag=3f7630c4da1b459ea8785c10c6c29676;epid=6ffbeddc9d > To: <sip:kate@gutatelecom.ru> > Call-ID: 9d356b245a924154bb96a2a43144add1 > CSeq: 1 REGISTER > Contact: <sip:10.123.0.190:12479>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER, BENOTIFY" > User-Agent: RTC/1.3.5470 (Messenger 5.1.0701) > Event: registration > Allow-Events: presence > Content-Length: 0 > C6 > SIP/2.0 200 OK > Via: SIP/2.0/UDP 10.123.0.190:12479 > From: <sip:kate@gutatelecom.ru>;tag=3f7630c4da1b459ea8785c10c6c29676;epid=6ffbeddc9d > To: <sip:kate@gutatelecom.ru>;tag=9bf9a4f66ee3c16d13ef4422214649c2.f220 > Call-ID: 9d356b245a924154bb96a2a43144add1 > CSeq: 1 REGISTER > Contact: <sip:10.123.0.190:7808>;expires=3288, <sip:10.123.0.190:12479>;expires=3600 > Server: Sip EXpress router (0.9.4 (i386/solaris)) > Content-Length: 0 > Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=25299 req_src_ip=10.123.0.190 req_src_port=1041 in_uri=sip:gutatelecom.ru out_uri=sip:gutatelecom.ru via_cnt==1" > C$# > 2 ?SUBSCRIBE sip:ura@gutatelecom.ru SIP/2.0 > Via: SIP/2.0/UDP 10.123.0.190:12479 > Max-Forwards: 70 > From: "kate(a)gutatelecom.ru" <sip:kate@gutatelecom.ru>;tag=1fe50fffda3b490192c4a4e5badd2008;epid=6ffbeddc9d > To: <sip:ura@gutatelecom.ru> > Call-ID: 4ab889c390a14810aea197bb705e2e9d > CSeq: 1 SUBSCRIBE > Contact: <sip:10.123.0.190:12479> > User-Agent: RTC/1.3 > Event: presence > Accept: application/xpidf+xml, text/xml+msrtc.pidf, application/pidf+xml > Supported: com.microsoft.autoextend > Supported: ms-benotify > Proxy-Require: ms-benotify > Content-Length: 0 > C~# > 2":SUBSCRIBE sip:admin@gutagroup.ru SIP/2.0 > Via: SIP/2.0/UDP 10.123.0.190:12479 > Max-Forwards: 70 > From: "kate(a)gutatelecom.ru" <sip:kate@gutatelecom.ru>;tag=40649ffd5fb04089a23bdb25fba6ed3f;epid=6ffbeddc9d > To: <sip:admin@gutagroup.ru> > Call-ID: 9f52e3dd37ad46e79b0517f06e878b67 > CSeq: 1 SUBSCRIBE > Contact: <sip:10.123.0.190:12479> > User-Agent: RTC/1.3 > Event: presence > Accept: application/xpidf+xml, text/xml+msrtc.pidf, application/pidf+xml > Supported: com.microsoft.autoextend > Supported: ms-benotify > Proxy-Require: ms-benotify > Content-Length: 0 > vSIP/2.0 400 Bad Request > Via: SIP/2.0/UDP 10.123.0.190:12479 > From: "kate(a)gutatelecom.ru" <sip:kate@gutatelecom.ru>;tag=1fe50fffda3b490192c4a4e5badd2008;epid=6ffbeddc9d > To: <sip:ura@gutatelecom.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-f220 > Call-ID: 4ab889c390a14810aea197bb705e2e9d > CSeq: 1 SUBSCRIBE > Error while parsing headersServer: Sip EXpress router (0.9.4 (i386/solaris)) > Content-Length: 0 > Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=25299 req_src_ip=10.123.0.190 req_src_port=1041 in_uri=sip:ura@gutatelecom.ru out_uri=sip:ura@gutatelecom.ru via_cnt==1" > C~+ > oSIP/2.0 400 Bad Request > Via: SIP/2.0/UDP 10.123.0.190:12479 > From: "kate(a)gutatelecom.ru" <sip:kate@gutatelecom.ru>;tag=40649ffd5fb04089a23bdb25fba6ed3f;epid=6ffbeddc9d > To: <sip:admin@gutagroup.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-f220 > Call-ID: 9f52e3dd37ad46e79b0517f06e878b67 > CSeq: 1 SUBSCRIBE > Error while parsing headersServer: Sip EXpress router (0.9.4 (i386/solaris)) > Content-Length: 0 > Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=25299 req_src_ip=10.123.0.190 req_src_port=1041 in_uri=sip:admin@gutagroup.ru out_uri=sip:admin@gutagroup.ru via_cnt==1" > > On Thu, Dec 15, 2005 at 09:33:18AM +0100, Vaclav Kubart wrote: >> Hello, >> I'm quite sure, that SER was able to work with Windows Messenger 4.7 (it >> is able to work with version 5.1), but I'm not sure about the version >> 0.9.4. May be that it wasn't in that version. >> >> Vaclav >> >> On Thu, 15 Dec 2005, Ekaterina Ivannikova wrote: >> >>> Hello list, >>> >>> I installed a binary package of ser-0.9.4 on Solaris 10 (Intel) from >>> ftp.berlios.de and am trying to use Windows Messenger 4.7 as a client. >>> However SUBSCRIBE requests fail with an obscure message "Error while >>> parsing >>> headers". Googling found several similar complaints, but I still can't >>> figure >>> out how to resolve the issue. Any help is very much appreciated. My config, >>> syslog messages and tcpdump follow. >>> >>> Regards, >>> >>> Ekaterina >>> >>> # ----------- 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 >>> >>> listen=10.123.0.250 >>> user=ser >>> group=ser >>> >>> 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" >>> loadmodule "/usr/local/lib/ser/modules/pa.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) >>> >>> modparam("usrloc|registrar", "use_domain", 1) >>> modparam("pa", "use_db", 1) >>> modparam("pa", "db_url", "mysql://ser:heslo@localhost/ser") >>> modparam("pa", "pa_domain", "gutatelecom.ru") >>> >>> >>> # ------------------------- request routing logic ------------------- >>> >>> # main routing logic >>> >>> alias="z1.all.yans.ru" >>> alias="gutatelecom.ru" >>> alias="gutagroup.ru" >>> alias="10.123.0.250" >>> >>> 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("iptel.org", "subscriber")) { >>> # www_challenge("iptel.org", "0"); >>> # break; >>> # }; >>> >>> save("location"); >>> break; >>> }; >>> >>> if (method=="SUBSCRIBE") { >>> if (!t_newtran()) { >>> log(1, "newtran error\n"); >>> sl_reply_error(); >>> }; >>> handle_subscription("registrar"); >>> break; >>> }; >>> >>> if (method=="PUBLISH") { >>> if (!t_newtran()) { >>> log(1, "newtran error\n"); >>> sl_reply_error(); >>> }; >>> handle_publish("registrar"); >>> 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(); >>> }; >>> } >>> >>> >>> Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] >>> setting signal 2 to 8063eb0 >>> Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] >>> setting signal 13 to 8063eb0 >>> Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] >>> setting signal 16 to 8063eb0 >>> Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] >>> setting signal 18 to 8063eb0 >>> Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] >>> setting signal 15 to 8063eb0 >>> Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] >>> setting signal 1 to 8063eb0 >>> Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] >>> setting signal 17 to 8063eb0 >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 212014 daemon.warning] >>> Warning: uac does not spread across the whole hash table >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 499528 daemon.notice] >>> Maxfwd module- initializing >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 520766 daemon.crit] >>> db_url=8228c90 >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 520769 daemon.crit] >>> db_url=mysql://ser:heslo@localhost/ser >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 472096 daemon.crit] >>> db_url.len=31 >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 351855 daemon.crit] >>> pa_domain=gutatelecom.ru >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 624776 daemon.crit] >>> pa_mod: use_db=1 db_url.s=mysql://ser:heslo@localhost/ser >>> pa_domain=gutatelecom.ru >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 101486 daemon.crit] >>> pa_mod_init done >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 187949 daemon.error] >>> subscribe_fixup: pdomain name is registrar >>> Dec 13 17:16:15 z1 last message repeated 1 time >>> Dec 13 17:16:15 z1 /usr/local/sbin/ser[24587]: [ID 827449 daemon.warning] >>> WARNING: no fifo_db_url given - fifo DB commands disabled! >>> Dec 13 17:17:25 z1 /usr/local/sbin/ser[24588]: [ID 219598 daemon.error] >>> handle_subscription() entered >>> Dec 13 17:17:25 z1 /usr/local/sbin/ser[24588]: [ID 717776 daemon.error] >>> parse_hfs(): Error while parsing headers >>> Dec 13 17:17:25 z1 /usr/local/sbin/ser[24588]: [ID 828236 daemon.error] >>> handle_subscription(): Error while parsing message header >>> Dec 13 17:17:25 z1 /usr/local/sbin/ser[24588]: [ID 405054 daemon.error] >>> handle_subscription about to send_reply and return -2 >>> Dec 13 17:17:25 z1 /usr/local/sbin/ser[24590]: [ID 219598 daemon.error] >>> handle_subscription() entered >>> Dec 13 17:17:25 z1 /usr/local/sbin/ser[24590]: [ID 717776 daemon.error] >>> parse_hfs(): Error while parsing headers >>> Dec 13 17:17:25 z1 /usr/local/sbin/ser[24590]: [ID 828236 daemon.error] >>> handle_subscription(): Error while parsing message header >>> Dec 13 17:17:25 z1 /usr/local/sbin/ser[24590]: [ID 405054 daemon.error] >>> handle_subscription about to send_reply and return -2 >>> Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 219598 daemon.error] >>> handle_subscription() entered >>> Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 717776 daemon.error] >>> parse_hfs(): Error while parsing headers >>> Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 828236 daemon.error] >>> handle_subscription(): Error while parsing message header >>> Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 405054 daemon.error] >>> handle_subscription about to send_reply and return -2 >>> Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 219598 daemon.error] >>> handle_subscription() entered >>> Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 717776 daemon.error] >>> parse_hfs(): Error while parsing headers >>> Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 828236 daemon.error] >>> handle_subscription(): Error while parsing message header >>> Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 405054 daemon.error] >>> handle_subscription about to send_reply and return -2 >>> >>> ~~~~~~~~~~~~~~~~~~ >>> REGISTER sip:gutatelecom.ru SIP/2.0 >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> Max-Forwards: 70 >>> From: >>> <sip:kate@gutatelecom.ru>;tag=f3dda05188a9449abba6930f6dc9ba57;epid=d631b39a7b >>> To: <sip:kate@gutatelecom.ru> >>> Call-ID: fc49c5f7ddbd4bf78718b0b11986caf4(a)10.123.0.190 >>> CSeq: 1 REGISTER >>> Contact: <sip:10.123.0.190:10707>;methods="INVITE, MESSAGE, INFO, >>> SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER" >>> User-Agent: RTC/1.2.4949 >>> Event: registration >>> Allow-Events: presence >>> Content-Length: 0 >>> K)^SIP/2.0 200 OK >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> From: >>> <sip:kate@gutatelecom.ru>;tag=f3dda05188a9449abba6930f6dc9ba57;epid=d631b39a7b >>> To: <sip:kate@gutatelecom.ru>;tag=9bf9a4f66ee3c16d13ef4422214649c2.b407 >>> Call-ID: fc49c5f7ddbd4bf78718b0b11986caf4(a)10.123.0.190 >>> CSeq: 1 REGISTER >>> Contact: <sip:10.123.0.190:10707>;expires=3600 >>> Server: Sip EXpress router (0.9.4 (i386/solaris)) >>> Content-Length: 0 >>> Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24588 >>> req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:gutatelecom.ru >>> out_uri=sip:gutatelecom.ru via_cnt==1" >>> SUBSCRIBE sip:ura@gutatelecom.ru SIP/2.0 >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> Max-Forwards: 70 >>> From: "kate" >>> <sip:kate@gutatelecom.ru>;tag=88b65cf1039140ba8f3fb3a0177ad1f0;epid=d631b39a7b >>> To: <sip:ura@gutatelecom.ru> >>> Call-ID: bf50c9641de74282a1f950e114e446de(a)10.123.0.190 >>> CSeq: 1 SUBSCRIBE >>> Contact: <sip:10.123.0.190:10707> >>> User-Agent: RTC/1.2 >>> Event: presence >>> Accept: application/xpidf+xml, text/xml+msrtc.pidf >>> Supported: com.microsoft.autoextend >>> Content-Length: 0 >>> SUBSCRIBE sip:admin@gutagroup.ru SIP/2.0 >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> Max-Forwards: 70 >>> From: "kate" >>> <sip:kate@gutatelecom.ru>;tag=28b82b1b69e34ffda395eafa53bff1fa;epid=d631b39a7b >>> To: <sip:admin@gutagroup.ru> >>> Call-ID: 0c95f18aac8a45578e90b1f61e5ad634(a)10.123.0.190 >>> CSeq: 1 SUBSCRIBE >>> Contact: <sip:10.123.0.190:10707> >>> User-Agent: RTC/1.2 >>> Event: presence >>> Accept: application/xpidf+xml, text/xml+msrtc.pidf >>> Supported: com.microsoft.autoextend >>> Content-Length: 0 >>> SIP/2.0 400 Bad Request >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> From: "kate" >>> <sip:kate@gutatelecom.ru>;tag=28b82b1b69e34ffda395eafa53bff1fa;epid=d631b39a7b >>> To: <sip:admin@gutagroup.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-b407 >>> Call-ID: 0c95f18aac8a45578e90b1f61e5ad634(a)10.123.0.190 >>> CSeq: 1 SUBSCRIBE >>> Error while parsing headersServer: Sip EXpress router (0.9.4 >>> (i386/solaris)) >>> Content-Length: 0 >>> Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24588 >>> req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:admin@gutagroup.ru >>> out_uri=sip:admin@gutagroup.ru via_cnt==1" >>> SIP/2.0 400 Bad Request >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> From: "kate" >>> <sip:kate@gutatelecom.ru>;tag=88b65cf1039140ba8f3fb3a0177ad1f0;epid=d631b39a7b >>> To: <sip:ura@gutatelecom.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-b407 >>> Call-ID: bf50c9641de74282a1f950e114e446de(a)10.123.0.190 >>> CSeq: 1 SUBSCRIBE >>> Error while parsing headersServer: Sip EXpress router (0.9.4 >>> (i386/solaris)) >>> Content-Length: 0 >>> Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24590 >>> req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:ura@gutatelecom.ru >>> out_uri=sip:ura@gutatelecom.ru via_cnt==1" >>> SUBSCRIBE sip:ura@gutatelecom.ru SIP/2.0 >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> Max-Forwards: 70 >>> From: "kate" >>> <sip:kate@gutatelecom.ru>;tag=88b65cf1039140ba8f3fb3a0177ad1f0;epid=d631b39a7b >>> To: <sip:ura@gutatelecom.ru> >>> Call-ID: bf50c9641de74282a1f950e114e446de(a)10.123.0.190 >>> CSeq: 1 SUBSCRIBE >>> Contact: <sip:10.123.0.190:10707> >>> User-Agent: RTC/1.2 >>> Event: presence >>> Accept: application/xpidf+xml, text/xml+msrtc.pidf >>> Supported: com.microsoft.autoextend >>> Content-Length: 0 >>> SUBSCRIBE sip:admin@gutagroup.ru SIP/2.0 >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> Max-Forwards: 70 >>> From: "kate" >>> <sip:kate@gutatelecom.ru>;tag=28b82b1b69e34ffda395eafa53bff1fa;epid=d631b39a7b >>> To: <sip:admin@gutagroup.ru> >>> Call-ID: 0c95f18aac8a45578e90b1f61e5ad634(a)10.123.0.190 >>> CSeq: 1 SUBSCRIBE >>> Contact: <sip:10.123.0.190:10707> >>> User-Agent: RTC/1.2 >>> Event: presence >>> Accept: application/xpidf+xml, text/xml+msrtc.pidf >>> Supported: com.microsoft.autoextend >>> Content-Length: 0 >>> SIP/2.0 400 Bad Request >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> From: "kate" >>> <sip:kate@gutatelecom.ru>;tag=88b65cf1039140ba8f3fb3a0177ad1f0;epid=d631b39a7b >>> To: <sip:ura@gutatelecom.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-b407 >>> Call-ID: bf50c9641de74282a1f950e114e446de(a)10.123.0.190 >>> CSeq: 1 SUBSCRIBE >>> Error while parsing headersServer: Sip EXpress router (0.9.4 >>> (i386/solaris)) >>> Content-Length: 0 >>> Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24590 >>> req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:ura@gutatelecom.ru >>> out_uri=sip:ura@gutatelecom.ru via_cnt==1" >>> SIP/2.0 400 Bad Request >>> Via: SIP/2.0/UDP 10.123.0.190:10707 >>> From: "kate" >>> <sip:kate@gutatelecom.ru>;tag=28b82b1b69e34ffda395eafa53bff1fa;epid=d631b39a7b >>> To: <sip:admin@gutagroup.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-b407 >>> Call-ID: 0c95f18aac8a45578e90b1f61e5ad634(a)10.123.0.190 >>> CSeq: 1 SUBSCRIBE >>> Error while parsing headersServer: Sip EXpress router (0.9.4 >>> (i386/solaris)) >>> Content-Length: 0 >>> Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24588 >>> req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:admin@gutagroup.ru >>> out_uri=sip:admin@gutagroup.ru via_cnt==1" >>> >>> _______________________________________________ >>> Serusers mailing list >>> serusers(a)lists.iptel.org >>> http://lists.iptel.org/mailman/listinfo/serusers >>> >

18 years, 11 months

[Serusers] need help with ser-0.9.4 and SUBSCRIBE requests

by Ekaterina Ivannikova

Hello list, I installed a binary package of ser-0.9.4 on Solaris 10 (Intel) from ftp.berlios.de and am trying to use Windows Messenger 4.7 as a client. However SUBSCRIBE requests fail with an obscure message "Error while parsing headers". Googling found several similar complaints, but I still can't figure out how to resolve the issue. Any help is very much appreciated. My config, syslog messages and tcpdump follow. Regards, Ekaterina # ----------- 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 listen=10.123.0.250 user=ser group=ser 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" loadmodule "/usr/local/lib/ser/modules/pa.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) modparam("usrloc|registrar", "use_domain", 1) modparam("pa", "use_db", 1) modparam("pa", "db_url", "mysql://ser:heslo@localhost/ser") modparam("pa", "pa_domain", "gutatelecom.ru") # ------------------------- request routing logic ------------------- # main routing logic alias="z1.all.yans.ru" alias="gutatelecom.ru" alias="gutagroup.ru" alias="10.123.0.250" 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("iptel.org", "subscriber")) { # www_challenge("iptel.org", "0"); # break; # }; save("location"); break; }; if (method=="SUBSCRIBE") { if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); }; handle_subscription("registrar"); break; }; if (method=="PUBLISH") { if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); }; handle_publish("registrar"); 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(); }; } Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] setting signal 2 to 8063eb0 Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] setting signal 13 to 8063eb0 Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] setting signal 16 to 8063eb0 Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] setting signal 18 to 8063eb0 Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] setting signal 15 to 8063eb0 Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] setting signal 1 to 8063eb0 Dec 13 17:16:14 z1 /usr/local/sbin/ser[24585]: [ID 326729 daemon.crit] setting signal 17 to 8063eb0 Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 212014 daemon.warning] Warning: uac does not spread across the whole hash table Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 499528 daemon.notice] Maxfwd module- initializing Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 520766 daemon.crit] db_url=8228c90 Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 520769 daemon.crit] db_url=mysql://ser:heslo@localhost/ser Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 472096 daemon.crit] db_url.len=31 Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 351855 daemon.crit] pa_domain=gutatelecom.ru Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 624776 daemon.crit] pa_mod: use_db=1 db_url.s=mysql://ser:heslo@localhost/ser pa_domain=gutatelecom.ru Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 101486 daemon.crit] pa_mod_init done Dec 13 17:16:15 z1 /usr/local/sbin/ser[24585]: [ID 187949 daemon.error] subscribe_fixup: pdomain name is registrar Dec 13 17:16:15 z1 last message repeated 1 time Dec 13 17:16:15 z1 /usr/local/sbin/ser[24587]: [ID 827449 daemon.warning] WARNING: no fifo_db_url given - fifo DB commands disabled! Dec 13 17:17:25 z1 /usr/local/sbin/ser[24588]: [ID 219598 daemon.error] handle_subscription() entered Dec 13 17:17:25 z1 /usr/local/sbin/ser[24588]: [ID 717776 daemon.error] parse_hfs(): Error while parsing headers Dec 13 17:17:25 z1 /usr/local/sbin/ser[24588]: [ID 828236 daemon.error] handle_subscription(): Error while parsing message header Dec 13 17:17:25 z1 /usr/local/sbin/ser[24588]: [ID 405054 daemon.error] handle_subscription about to send_reply and return -2 Dec 13 17:17:25 z1 /usr/local/sbin/ser[24590]: [ID 219598 daemon.error] handle_subscription() entered Dec 13 17:17:25 z1 /usr/local/sbin/ser[24590]: [ID 717776 daemon.error] parse_hfs(): Error while parsing headers Dec 13 17:17:25 z1 /usr/local/sbin/ser[24590]: [ID 828236 daemon.error] handle_subscription(): Error while parsing message header Dec 13 17:17:25 z1 /usr/local/sbin/ser[24590]: [ID 405054 daemon.error] handle_subscription about to send_reply and return -2 Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 219598 daemon.error] handle_subscription() entered Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 717776 daemon.error] parse_hfs(): Error while parsing headers Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 828236 daemon.error] handle_subscription(): Error while parsing message header Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 405054 daemon.error] handle_subscription about to send_reply and return -2 Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 219598 daemon.error] handle_subscription() entered Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 717776 daemon.error] parse_hfs(): Error while parsing headers Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 828236 daemon.error] handle_subscription(): Error while parsing message header Dec 13 17:17:32 z1 /usr/local/sbin/ser[24593]: [ID 405054 daemon.error] handle_subscription about to send_reply and return -2 ~~~~~~~~~~~~~~~~~~ REGISTER sip:gutatelecom.ru SIP/2.0 Via: SIP/2.0/UDP 10.123.0.190:10707 Max-Forwards: 70 From: <sip:kate@gutatelecom.ru>;tag=f3dda05188a9449abba6930f6dc9ba57;epid=d631b39a7b To: <sip:kate@gutatelecom.ru> Call-ID: fc49c5f7ddbd4bf78718b0b11986caf4(a)10.123.0.190 CSeq: 1 REGISTER Contact: <sip:10.123.0.190:10707>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER" User-Agent: RTC/1.2.4949 Event: registration Allow-Events: presence Content-Length: 0 K)^SIP/2.0 200 OK Via: SIP/2.0/UDP 10.123.0.190:10707 From: <sip:kate@gutatelecom.ru>;tag=f3dda05188a9449abba6930f6dc9ba57;epid=d631b39a7b To: <sip:kate@gutatelecom.ru>;tag=9bf9a4f66ee3c16d13ef4422214649c2.b407 Call-ID: fc49c5f7ddbd4bf78718b0b11986caf4(a)10.123.0.190 CSeq: 1 REGISTER Contact: <sip:10.123.0.190:10707>;expires=3600 Server: Sip EXpress router (0.9.4 (i386/solaris)) Content-Length: 0 Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24588 req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:gutatelecom.ru out_uri=sip:gutatelecom.ru via_cnt==1" SUBSCRIBE sip:ura@gutatelecom.ru SIP/2.0 Via: SIP/2.0/UDP 10.123.0.190:10707 Max-Forwards: 70 From: "kate" <sip:kate@gutatelecom.ru>;tag=88b65cf1039140ba8f3fb3a0177ad1f0;epid=d631b39a7b To: <sip:ura@gutatelecom.ru> Call-ID: bf50c9641de74282a1f950e114e446de(a)10.123.0.190 CSeq: 1 SUBSCRIBE Contact: <sip:10.123.0.190:10707> User-Agent: RTC/1.2 Event: presence Accept: application/xpidf+xml, text/xml+msrtc.pidf Supported: com.microsoft.autoextend Content-Length: 0 SUBSCRIBE sip:admin@gutagroup.ru SIP/2.0 Via: SIP/2.0/UDP 10.123.0.190:10707 Max-Forwards: 70 From: "kate" <sip:kate@gutatelecom.ru>;tag=28b82b1b69e34ffda395eafa53bff1fa;epid=d631b39a7b To: <sip:admin@gutagroup.ru> Call-ID: 0c95f18aac8a45578e90b1f61e5ad634(a)10.123.0.190 CSeq: 1 SUBSCRIBE Contact: <sip:10.123.0.190:10707> User-Agent: RTC/1.2 Event: presence Accept: application/xpidf+xml, text/xml+msrtc.pidf Supported: com.microsoft.autoextend Content-Length: 0 SIP/2.0 400 Bad Request Via: SIP/2.0/UDP 10.123.0.190:10707 From: "kate" <sip:kate@gutatelecom.ru>;tag=28b82b1b69e34ffda395eafa53bff1fa;epid=d631b39a7b To: <sip:admin@gutagroup.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-b407 Call-ID: 0c95f18aac8a45578e90b1f61e5ad634(a)10.123.0.190 CSeq: 1 SUBSCRIBE Error while parsing headersServer: Sip EXpress router (0.9.4 (i386/solaris)) Content-Length: 0 Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24588 req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:admin@gutagroup.ru out_uri=sip:admin@gutagroup.ru via_cnt==1" SIP/2.0 400 Bad Request Via: SIP/2.0/UDP 10.123.0.190:10707 From: "kate" <sip:kate@gutatelecom.ru>;tag=88b65cf1039140ba8f3fb3a0177ad1f0;epid=d631b39a7b To: <sip:ura@gutatelecom.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-b407 Call-ID: bf50c9641de74282a1f950e114e446de(a)10.123.0.190 CSeq: 1 SUBSCRIBE Error while parsing headersServer: Sip EXpress router (0.9.4 (i386/solaris)) Content-Length: 0 Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24590 req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:ura@gutatelecom.ru out_uri=sip:ura@gutatelecom.ru via_cnt==1" SUBSCRIBE sip:ura@gutatelecom.ru SIP/2.0 Via: SIP/2.0/UDP 10.123.0.190:10707 Max-Forwards: 70 From: "kate" <sip:kate@gutatelecom.ru>;tag=88b65cf1039140ba8f3fb3a0177ad1f0;epid=d631b39a7b To: <sip:ura@gutatelecom.ru> Call-ID: bf50c9641de74282a1f950e114e446de(a)10.123.0.190 CSeq: 1 SUBSCRIBE Contact: <sip:10.123.0.190:10707> User-Agent: RTC/1.2 Event: presence Accept: application/xpidf+xml, text/xml+msrtc.pidf Supported: com.microsoft.autoextend Content-Length: 0 SUBSCRIBE sip:admin@gutagroup.ru SIP/2.0 Via: SIP/2.0/UDP 10.123.0.190:10707 Max-Forwards: 70 From: "kate" <sip:kate@gutatelecom.ru>;tag=28b82b1b69e34ffda395eafa53bff1fa;epid=d631b39a7b To: <sip:admin@gutagroup.ru> Call-ID: 0c95f18aac8a45578e90b1f61e5ad634(a)10.123.0.190 CSeq: 1 SUBSCRIBE Contact: <sip:10.123.0.190:10707> User-Agent: RTC/1.2 Event: presence Accept: application/xpidf+xml, text/xml+msrtc.pidf Supported: com.microsoft.autoextend Content-Length: 0 SIP/2.0 400 Bad Request Via: SIP/2.0/UDP 10.123.0.190:10707 From: "kate" <sip:kate@gutatelecom.ru>;tag=88b65cf1039140ba8f3fb3a0177ad1f0;epid=d631b39a7b To: <sip:ura@gutatelecom.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-b407 Call-ID: bf50c9641de74282a1f950e114e446de(a)10.123.0.190 CSeq: 1 SUBSCRIBE Error while parsing headersServer: Sip EXpress router (0.9.4 (i386/solaris)) Content-Length: 0 Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24590 req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:ura@gutatelecom.ru out_uri=sip:ura@gutatelecom.ru via_cnt==1" SIP/2.0 400 Bad Request Via: SIP/2.0/UDP 10.123.0.190:10707 From: "kate" <sip:kate@gutatelecom.ru>;tag=28b82b1b69e34ffda395eafa53bff1fa;epid=d631b39a7b To: <sip:admin@gutagroup.ru>;tag=4847b256b8606eb0a98fbd0f755585cd-b407 Call-ID: 0c95f18aac8a45578e90b1f61e5ad634(a)10.123.0.190 CSeq: 1 SUBSCRIBE Error while parsing headersServer: Sip EXpress router (0.9.4 (i386/solaris)) Content-Length: 0 Warning: 392 10.123.0.250:5060 "Noisy feedback tells: pid=24588 req_src_ip=10.123.0.190 req_src_port=1271 in_uri=sip:admin@gutagroup.ru out_uri=sip:admin@gutagroup.ru via_cnt==1"

18 years, 11 months

[Users] login problem

by unplug

I am using mysql.so for the user login. User can login without problem. After a few hours, user issues still issue a register request as below but can't login to the system (there is no record in the db). Why user failed to login suddently? I am sure the username and password are correct. From the log, I can see the register request as below. However, user login failed. Dec 14 17:19:32 os01 /usr/local/sbin/openser[14889]: SIP Request: method [REGISTER] from [210.202.7.17] [1833] to [203.193.146.6] [5060]

18 years, 11 months

[Serusers] SER-0.9.4 and Mysql 5.0.15

by han yibing

Hello All: I am using SER-0.9.4 with mysql 5.0.15,when i create database and tables with following error: [root@localhost sbin]# ./ser_mysql.sh create MySql password for root: creating database ser ... ERROR 1049 (42000) at line 2: Unknown database 'ser;' please help me !!! thanks __________________________________________________ 赶快注册雅虎超大容量免费邮箱? http://cn.mail.yahoo.com

18 years, 11 months

[Serusers] problems with ser + radius

by Guido

Hello, I'm using fedora core 4 and radiusclient-0.4.3. installing SER 0.9.4 with support for radius I can't install radius modules and when run my SER I view this mesasge error 0(441) ERROR: load_module: could not open module </usr/local/lib/ser/modules/auth_radius.so>: /usr/local/lib/ser/modules/auth_radius.so: cannot open shared object file: No such file or directory 0(441) parse error (41,13-14): failed to load module 0(441) set_mod_param_regex: No module matching auth_radius found | 0(441) parse error (71,20-21): Can't set module parameter 0(441) set_mod_param_regex: No module matching auth_radius found | 0(441) parse error (72,20-21): Can't set module parameter 0(441) parse error (326,34-35): unknown command, missing loadmodule? Anybody can help me ? Thanks Guido

18 years, 11 months

[Users] Variables

by Douglas Garstang

All, I can't find any documentation of OpenSER use of variables. I'm sending a lot of info to syslog with xlog(), and with multiple threads (processes?) and multiple calls running, all the output is out of sequence. As a result, I'd like to prefix the debug output with the call-id. The call-id however is very long and I'd like to cut it down and only display a portion of it. How can I extract a string from a SIP message, cut it up, extract the portion I want, and print that portion? OpenSER doesn't seem to have any concept of assigning variables by: variable = value Thanks, Doug.

18 years, 11 months

[Users] How to send SIP REFER?

by James H Thompson

Whats the best way to send out a SIP REFER in reply to a received INVITE? Thanks.

18 years, 11 months

← Newer
1
...
6
7
8
9
10
11
12
...
32
Older →

Jump to page:

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