sr-users April 2005

sr-users@lists.kamailio.org

250 participants
697 discussions

by Erdem HAKI

Deal all, I am a newbie in SIP I am trying to add Voicemail service on my SER . As according to "SIP Express Router v0.11 --Admin Guide" SEMS is required to provide voicemail capability in SIP server. i have downloaded "sems-0.1.0.tar.gz" and installed in my machine where I have "ser-0.8.11" as a sip server. I have changed my ser.cfg scripts to provide voicemail capabilities and to load vm module available in SER. Now I get stuck How I have to use SEMS module ( I mean to say that "ans_machine" available in sems ) what is the difference & similarity between SEMS Voicemail and SER vm module. On what basis SEMS Voicemail and SER communicate to each other. Is their any configuration file is required inside the SEMS like SER (ex. ser.cfg). what is the proper step to perform a testing of voice mail using these modules.. (the same problem witk koyama) Thanks for your help.... Erdem H. HAKI

19 years, 7 months

RE: [Serusers] Serious Problems with SER - Not responding anythin g.

by Ricardo Martinez

Thanks again. I have heard about sipsak, but nothing about nagios. Is a tool that come with sipsak? How it works?. Is a monitoring tool?. I found the sipsak homepage but i don't see the relation with logging information from SER.... Can someone give more information about this tool? Thanks! Ricardo Martinez.- > -----Mensaje original----- > De: Jiri Kuthan [mailto:jiri@iptel.org] > Enviado el: Miércoles, 20 de Abril de 2005 19:57 > Para: Ricardo Martinez; 'serusers(a)lists.iptel.org' > Asunto: RE: [Serusers] Serious Problems with SER - Not responding > anythin g. > > > One more which came into my mind and has been reported to > block is syslog. > > > At 07:39 PM 4/20/2005, Ricardo Martinez wrote: > >Thanks Jiri. > >I remember have been checked the typical services when the > problem was > >happening. > >My Radius (i'm not use mysql) for example was working > without problems... > > > >How can i log information of SER failures? > > nagios/sipsak is an option. > > -jiri > > > >Regards, > >Ricardo.- > > > > > >> -----Mensaje original----- > >> De: Jiri Kuthan [mailto:jiri@iptel.org] > >> Enviado el: Miércoles, 20 de Abril de 2005 13:12 > >> Para: Ricardo Martinez; 'serusers(a)lists.iptel.org' > >> Asunto: Re: [Serusers] Serious Problems with SER - Not responding > >> anything. > >> > >> > >> a typical reason is SER is blocked waiting for some > external service. > >> It may be possibly unavailable mysql, DNS, or RADIUS... > >> > >> -jiri > >> > >> At 07:09 PM 4/20/2005, Ricardo Martinez wrote: > >> >Hello list. > >> > I'm experiencing problems with my SER. As i > >> mentioned in a past > >> >post > >> (http://lists.iptel.org/pipermail/serusers/2005-April/018324.html), > >> >from time to time (it is getting pretty often) my SER not > >> answering any > >> >request, when a REGISTER reach the server it is not > >> challenged, this happens > >> >too with the INVITE's messages. About two hours ago this > >> happened again. > >> >I asked in my last post how to LOG the internal errors or > >> messages from SER > >> >to see if i can get some idea about what's going on, but i > >> have no answer > >> >about it. > >> >This is the infornmation i was able to capture when this was > >> happening : > >> > > >> >the serctl moni command shows a lot of "failures". > >> > > >> >[cycle #: 11; if constant make sure server lives and fifo is on] > >> >Server: Sip EXpress router (0.8.14-3 (i386/linux)) > >> >Now: Wed Apr 20 12:56:29 2005 > >> >Up Since: Thu Apr 14 21:32:18 2005 > >> >Up time: 487451 [sec] > >> > > >> >Transaction Statistics > >> >Current: 6 (2612 waiting) Total: 38194 (0 local) > >> >Replied localy: 80752 > >> >Completion status 6xx: 4643, 5xx: 768, 4xx: 10664, 3xx: > >> 0,2xx: 22552 > >> > > >> >Stateless Server Statistics > >> >200: 5975004 202: 0 2xx: 0 > >> >300: 0 301: 0 302: 0 3xx: 0 > >> >400: 0 401: 205980 403: 0 404: 0 407: 22918 408: 0 483: 0 > >> 4xx: 19 > >> >500: 0 5xx: 0 > >> >6xx: 0 > >> >xxx: 0 > >> >failures: 24180 > >> > > >> >UsrLoc Stats > >> >Domain Registered Expired > >> >'location' 219 4552 > >> >-------------------------------------------------------------- > >> >[cycle #: 5; if constant make sure server lives and fifo is on] > >> >Server: Sip EXpress router (0.8.14-3 (i386/linux)) > >> >Now: Wed Apr 20 12:56:47 2005 > >> >Up Since: Thu Apr 14 21:32:18 2005 > >> >Up time: 487469 [sec] > >> > > >> >Transaction Statistics > >> >Current: 4 (2619 waiting) Total: 38219 (0 local) > >> >Replied localy: 80762 > >> >Completion status 6xx: 4643, 5xx: 770, 4xx: 10667, 3xx: > >> 0,2xx: 22552 > >> > > >> >Stateless Server Statistics > >> >200: 5975030 202: 0 2xx: 0 > >> >300: 0 301: 0 302: 0 3xx: 0 > >> >400: 0 401: 205995 403: 0 404: 0 407: 22922 408: 0 483: 0 > >> 4xx: 19 > >> >500: 0 5xx: 0 > >> >6xx: 0 > >> >xxx: 0 > >> >failures: 24380 > >> > > >> >UsrLoc Stats > >> >Domain Registered Expired > >> >'location' 220 4552 > >> >----------------------------------------------------------------- > >> >[cycle #: 2; if constant make sure server lives and fifo is on] > >> >Server: Sip EXpress router (0.8.14-3 (i386/linux)) > >> >Now: Wed Apr 20 12:56:52 2005 > >> >Up Since: Thu Apr 14 21:32:18 2005 > >> >Up time: 487474 [sec] > >> > > >> >Transaction Statistics > >> >Current: 4 (2620 waiting) Total: 38224 (0 local) > >> >Replied localy: 80762 > >> >Completion status 6xx: 4643, 5xx: 770, 4xx: 10667, 3xx: > >> 0,2xx: 22552 > >> > > >> >Stateless Server Statistics > >> >200: 5975034 202: 0 2xx: 0 > >> >300: 0 301: 0 302: 0 3xx: 0 > >> >400: 0 401: 206000 403: 0 404: 0 407: 22923 408: 0 483: 0 > >> 4xx: 19 > >> >500: 0 5xx: 0 > >> >6xx: 0 > >> >xxx: 0 > >> >failures: 24445 > >> > > >> >UsrLoc Stats > >> >Domain Registered Expired > >> >'location' 215 4557 > >> > > >> >What is happening to cause the "failures" counter grows > that much?. > >> > > >> >The free command shows this : > >> >[root@root]# free > >> > total used free shared > >> buffers cached > >> >Mem: 1030888 626464 404424 0 > >> 86692 369848 > >> >-/+ buffers/cache: 169924 860964 > >> >Swap: 2040244 4864 2035380 > >> > > >> >The top command shows not much use of CPU. The proccess > >> were running (the > >> >SER and mediaproxy) > >> >Despite of all this, the SER was not answering anything. > >> >Could this be a bug? or maybe a problem with my ser.cfg > file?. I'm > >> >attaching my ser.cfg file too to see if someone can tell me > >> if there is > >> >something wrong about it. > >> >I really hope that someone could help me, this is getting > >> really complicated > >> >every time it happens. > >> > > >> >Thanks > >> >Ricardo Martinez.- > >> > > >> >************************************************** > >> >SER.CFG > >> >************************************************** > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++++++++++++++++++++++++ > >> > > >> > > >> > > >> > > >> ># ----------- global configuration parameters > >> ------------------------ > >> > > >> >debug=0 # debug level (cmd line: -dddddddddd) > >> >fork=yes > >> >log_stderror=yes # (cmd line: -E) > >> > > >> >#Uncomment these lines to enter debugging mode > >> >#fork=no > >> >#log_stderror=yes > >> > > >> >listen=ip.of.my.ser > >> > > >> >alias=sip.mydomain.com > >> >alias=sip2.mydomain.net > >> >alias=ip.of.my.ser > >> > > >> > > >> >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" > >> >fifo_mode=0666 > >> > > >> > > >> ># ------------------ 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/exec.so" > >> > > >> ># ++++++++++ Para trabajar con NAT > >> > > >> >loadmodule "/usr/local//lib/ser/modules/mediaproxy.so" > >> >loadmodule "/usr/local//lib/ser/modules/domain.so" > >> >loadmodule "/usr/local//lib/ser/modules/dbtext.so" > >> >loadmodule "/usr/local//lib/ser/modules/nathelper.so" > >> > > >> ># Uncomment this if you want digest authentication > >> ># mysql.so must be loaded ! > >> >loadmodule "/usr/local/lib/ser/modules/auth.so" > >> > > >> ># ++++++++++ Modulos de Accounting y Autorizacion via Radius > >> > > >> >loadmodule "/usr/local/lib/ser/modules/auth_radius.so" > >> >loadmodule "/usr/local/lib/ser/modules/group_radius.so" > >> >loadmodule "/usr/local/lib/ser/modules/acc.so" > >> > > >> ># ----------------- setting module-specific parameters > >> --------------- > >> ># -- rr params -- > >> ># add value to ;lr param to make some broken UAs happy > >> >modparam("rr", "enable_full_lr", 1) > >> > > >> ># +++++ module authorization > >> >modparam("auth_radius","radius_config","/usr/local/etc/radius > >> client/radiuscl > >> >ient.conf") > >> >modparam("auth_radius","service_type",15) > >> > > >> > > >> ># +++++ module accounting > >> >modparam("acc","radius_config","/usr/local/etc/radiusclient/r > >> adiusclient.con > >> >f") > >> >modparam("acc","log_level",1) > >> >modparam("acc", "service_type", 15) > >> >modparam("acc", "radius_flag", 1) > >> >modparam("acc", "radius_missed_flag", 3) > >> >modparam("acc", "failed_transactions", 1) > >> >modparam("acc", "report_ack", 0) > >> > > >> > > >> ># +++++ group radius > >> >modparam("group_radius","radius_config","/usr/local/etc/radiu > >> sclient/radiusc > >> >lient.conf") > >> >modparam("group_radius", "use_domain", 1) > >> > > >> > > >> ># +++++ module mediaproxy > >> >modparam("mediaproxy", "natping_interval", 60) > >> >modparam("mediaproxy", "mediaproxy_socket", > >> "/var/run/mediaproxy.sock") > >> >#modparam("mediaproxy", "sip_asymmetrics", > >> >"/usr/local/etc/ser/sip-asymmetrics-clients") > >> >#modparam("mediaproxy", "rtp_asymmetrics", > >> >"/usr/local/etc/ser/rtp-asymmetrics-clients") > >> >modparam("registrar", "nat_flag", 5) > >> > > >> ># +++++ module domain > >> >modparam("domain", "db_url", "/usr/local/etc/ser/domaintables") > >> >modparam("domain", "domain_table", "domain") > >> >modparam("domain", "domain_col", "domain") > >> > > >> ># +++++ module tm > >> >modparam("tm", "fr_timer", 15) > >> >modparam("tm", "fr_inv_timer", 22) > >> >modparam("tm", "wt_timer", 5) > >> > > >> ># +++++ module registrar (Con estos parametro haces que el > >> location lookup > >> >priorize solo los mas recientes contacts) > >> >modparam("registrar", "append_branches", 0) > >> >modparam("registrar", "desc_time_order", 1) > >> > > >> > > >> ># ------------------------- request routing logic > >> ------------------- > >> > > >> ># main routing logic > >> > > >> >route { > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> ++++++++++++++ > >> > # Llamada a Rutina Externa "translate" para > cambio de numero > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> ++++++++++++++ > >> > > >> > if (method=="INVITE" || method=="CANCEL") { > >> > exec_dset("/usr/local/etc/ser/translate"); > >> > }; > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> ++++++++++++++ > >> > # 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 > max_len ) { > >> > sl_send_reply("513", "Message too big"); > >> > break; > >> > }; > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> > # Marcamos todos los mensajes para que pasen por > >> nuestro servidor > >> > # a traves del record route. > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> > > >> > record_route(); > >> > > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> > # Permitimos el uso del campo Route en el ruteo > de la llamada > >> > # > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> > > >> > if (method=="BYE" || method=="CANCEL") { > >> > log(1, "NAT: BYE o CANCEL recibido --> > >> terminando la sesion > >> >de media\n"); > >> > end_media_session(); > >> > setflag(1); > >> > }; > >> > > >> > if (loose_route()) { > >> > t_relay(); > >> > break; > >> > }; > >> > > >> > > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+ > >> > # Manejo de los mensajes NOTIFY para Keep Alive de NAT > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+ > >> > > >> > if ((method=="NOTIFY") && search("^Event: keep-alive")) { > >> > sl_send_reply("200", "OK"); > >> > break; > >> > }; > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+ > >> > # Marcamos las llamadas para accounting > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+ > >> > > >> > setflag(1); > >> > > >> > > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+ > >> > # Test para clientes NATeados > >> > # > >> > # 1 : Chequea si el cliente tiene IP privada en el > >> campo Contact. > >> > # 2 : Chequea si el cliente se contacto con una IP > >> distinta a la del > >> >campo VIA. > >> > # 3 : Chequea si el cliente tiene IP privada en el > >> ultimo campo VIA. > >> > # > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+ > >> > > >> > > >> > if (client_nat_test("3")) { > >> > log(1, "NAT: Requerimiento de IP privada --> > >> fixed contact > >> >(en rutina principal)\n"); > >> > setflag(5); > >> > force_rport(); > >> > > >> > if (method=="REGISTER") { > >> > fix_nated_contact(); > >> > } else { > >> > fix_contact(); > >> > }; > >> > append_hf("P-hint: fixed NAT contact for > >> request\r\n"); > >> > }; > >> > > >> > > >> > if (uri==myself) { > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++ > >> > # Chequeo de REGISTRO para equipos del dominio 1 > >> > # Dominio Voiss : sip.mydomain.com > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++ > >> > > >> > if (method=="REGISTER" && > >> uri=~"^sip:.*sip.mydomain.com") { > >> > # Challenge/Response > >> > if ( > >> !radius_www_authorize("sip.mydomain.com")) { > >> > > >> www_challenge("sip.mydomain.com", "1"); > >> > break; > >> > }; > >> > > >> > # Mandamos un mensaje de Log si es > >> que un cliente > >> >NATEADO se registro. > >> > if (isflagset(5)) { > >> > log(1, "NAT: Cliente > >> NAT'eado registrado > >> >(dentro del chequeo de REGISTER)\n"); > >> > }; > >> > > >> > save("location"); > >> > break; > >> > }; # Fin chequeo de Registro para Dominio : > >> sip.mydomain.com > >> > > >> > > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++ > >> > # Chequeo de REGISTRO para equipos del dominio 2 > >> > # Dominio Mayoristas : sip2.mydomain.net > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++ > >> > > >> > if (method=="REGISTER" && > >> uri=~"^sip:.*sip2.mydomain.net") { > >> > # Challenge/Response > >> > if ( > >> !radius_www_authorize("sip2.mydomain.net")) { > >> > > >> www_challenge("sip2.mydomain.net", "1"); > >> > break; > >> > }; > >> > > >> > # Mandamos un mensaje de Log si es > >> que un cliente > >> >NATEADO se registro. > >> > if (isflagset(5)) { > >> > log(1, "NAT: Cliente > >> NAT'eado registrado > >> >(dentro del chequeo de REGISTER)\n"); > >> > }; > >> > > >> > save("location"); > >> > break; > >> > }; # Fin chequeo de Registro para Dominio : > >> >sip2.mydomain.net > >> > > >> > > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++ > >> > # CHEQUEO DEL INVITE PARA TODAS LAS LLAMADAS > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++ > >> > > >> > if (method=="INVITE" && src_ip!=xx.xx.xx.xx) { > >> > if ( !radius_proxy_authorize("")) { > >> > proxy_challenge("", "1"); > >> > log (1, "LOG: Llamada no > >> AUTORIZADA\n"); > >> > break; > >> > }; > >> > }; > >> > > >> > > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++++ > >> > # Llamadas hacia dominio H.323 > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++++ > >> > > >> > if ( (uri=~"^sip:717.*@.*") | > >> (uri=~"^sip:707.*@.*") | > >> >(uri=~"^sip:777.*@.*") | (uri=~"^sip:333.*@.*") | (uri=~"^sip > >> >:0.*@.*") ){ > >> > log(1,"FORWARDING : Llamada hacia > plataforma > >> >H.323\n"); > >> > route(1); > >> > break; > >> > }; > >> > > >> > > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++ > >> > # Llamadas SIP locales > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++ > >> > > >> > if (!lookup("location")) { #Usuarios que > no estan en > >> >"location" database. > >> > route(4); > >> > break; > >> > }; > >> > > >> > > >> > setflag(3); > >> > > >> > > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++ > >> > # Manejo para llamadas NAT'das > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++ > >> > > >> > if (method=="INVITE") { > >> > log(1, "ROUTING: Reply processing > >> (online user) > >> >enabled to handle NAT'd resonses\n"); > >> > t_on_reply("1"); > >> > if ( (isflagset(5)) && > >> (method=="INVITE" || > >> >method=="ACK") ) { > >> > log(1, "NAT: Invite > >> received --> > >> >enabling media proxy (else del lookup 2do if)\n"); > >> > use_media_proxy(); > >> > append_hf("P-hint: > >> request forced to > >> >media proxy\r\n"); > >> > }; > >> > }; > >> > > >> > # Do it ? (Ricardo Martinez) > >> > }; > >> > > >> > append_hf("P-hint: USRLOC\r\n"); > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+++++ > >> > # Efectuamos la llamada > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+++++ > >> > > >> > if (!t_relay()) { > >> > sl_reply_error(); > >> > break; > >> > }; > >> > > >> >} /* end of initial routing logic */ > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++++++++++++ > >> ># COMIENZO DE LA SECCION DE RUTAS > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++++++++++++ > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >++++++++++++++++++ > >> ># Route 1 : Llamadas con destino plataforma > >> >H.323#+++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+++++++++++++++++++++++ > >> >route[1] > >> >{ > >> > # send it out now; use stateful forwarding as it > >> works reliably > >> > # even for UDP2TCP > >> > > >> > # Esta NATEADO? > >> > if (isflagset(5)) { > >> > log(1, "NAT: At least one participant NAT'd > >> --> enable reply > >> >processing (hacia GW)\n"); > >> > t_on_reply("1"); > >> > if (method=="INVITE") { > >> > log(1, "NAT: Invite received --> > >> enabling proxied > >> >media session (hacia GW)\n"); > >> > setflag(1); > >> > use_media_proxy(); > >> > }; > >> > }; > >> > > >> > rewritehostport("mygw.mydomain.com:5060"); > >> > append_hf("P-hint: GATEWAY\r\n"); > >> > > >> > if (!t_relay()) { > >> > sl_reply_error(); > >> > break; > >> > }; > >> > > >> >} > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+++++++++++++++++ > >> ># Route 4 : Llamadas a usuarios Off-line > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+++++++++++++++++ > >> > > >> >route[4] { > >> > > >> > if (!t_newtran()) { > >> > sl_reply_error(); > >> > }; > >> > > >> > if (!t_reply("404", "Not Found IT!")) { > >> > sl_reply_error(); > >> > }; > >> > break; > >> >} > >> > > >> > > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+++++++++++++++++ > >> ># On Reply Route 1 : Equipos NATeados!! > >> >#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> +++++++++++++++ > >> >+++++++++++++++++ > >> > > >> >onreply_route[1] { > >> > if ((isflagset(5) || client_nat_test("3")) && > >> >(status=~"(180)|(183)|2[0-9][0-9]")) { > >> > if (!search("^Content-Length:\ 0")) { > >> > use_media_proxy(); > >> > }; > >> > }; > >> > > >> > if (client_nat_test("1")) { > >> > fix_nated_contact(); > >> > }; > >> > > >> > > >> >} > >> > > >> > > >> > > >> > > >> >Ricardo Martinez.- > >> > > >> >_______________________________________________ > >> >Serusers mailing list > >> >serusers(a)lists.iptel.org > >> >http://lists.iptel.org/mailman/listinfo/serusers > >> > >> -- > >> Jiri Kuthan http://iptel.org/~jiri/ > >> > > > >_______________________________________________ > >Serusers mailing list > >serusers(a)lists.iptel.org > >http://lists.iptel.org/mailman/listinfo/serusers > > -- > Jiri Kuthan http://iptel.org/~jiri/ >

19 years, 7 months

[Serusers] Windows Messenger and SER

by Jffdsaklj dsjk

I'm testing SER with Windows Messenger 4.7 and I have problems with the presence service. Those contacts connected when the user connects, appear as connected (correct). But when another contact connects, it keeps appearing as disconnected, and after a long time (more or less one minute) shows the contact as connected. On the other hand, all the contacts appear as disconnected with Windows Messenger 5.1, independently that the contact is previously connected or connects later. Has someone problems with windows messenger?. I've checked that these contacts are connected in SER with "serctl ul show". So I imagine that it's some type of incompatibility with windows messenger.

19 years, 7 months

[Serusers] ser sizing

by Ahmad Cheikh Moussa

Hi! Can anyone tell me which Hardware requirements I need for a SER server ? Is there anywhere a documentation for this ? Regards, Ahmad -- Ahmad Cheikh-Moussa NetUSE AG Dr.-Hell-Straße, 24107 Kiel, Germany Telefon: +49 431 2390 400 -- Telefax: +49 431 2390 499 Service: Service(a)NetUSE.DE -- http://NetUSE.DE/

19 years, 7 months

[Serusers] RE: [Sipforum-discussion] regarding Authentication...

by Paul van Schagen

-----Oorspronkelijk bericht----- Van: Paul van Schagen [mailto:paul.van.schagen@adaline.net] Verzonden: donderdag 21 april 2005 9:02 Aan: 'Josekutty K.K' Onderwerp: RE: [Sipforum-discussion] regarding Authentication... Methods you really want to authenticate are INVITE ( outgoing calls ) and REGISTER ( incoming calls ). You try the request first and the switch answers requesting authentication. Then the authentication is sent by the UA to the switch. Remember the authentication also verifies the IP address of the sender is correct. By doing a double request you make sure that the original request came from where they say it came from. Lets say somebody fakes an IP address and sents the packet to the switch. The switch then sends back an authentication requests which arrives at another destination. The call never gets authenticated correctly and is rejected. Hopes this helps Can anybody help me with my mediaproxy timeout ? Best regards Paul van Schagen -----Oorspronkelijk bericht----- Van: sipforum-discussion-bounces(a)lists.su.se [mailto:sipforum-discussion-bounces@lists.su.se] Namens Josekutty K.K Verzonden: donderdag 21 april 2005 8:47 Aan: sipforum-discussion(a)lists.su.se Onderwerp: [Sipforum-discussion] regarding Authentication... Hi all, I am a beginner in SIP. Let me explain my doubt. Once a SIP request authenticates itself, (usually a REGISTER request), all further requests MUST include the authorization details .. I mean I MUST send the authorization details to subsequent requests say OPTIONS, INVITE etc . Or Should I try each request without authentication first? Regards Josekutty K K ------ To unsubscribe from the Sipforum-discussion mailing list visit https://mbox.su.se/mailman/listinfo/sipforum-discussion

19 years, 7 months

[Serusers] Commercial SER Support

by Darren Nay

Hey All, Do any of you know of a reliable / knowledgeable source for commercial technical support for SER. If so, we may be interested. We have worked in the past directly with IPTel, and have discussed support options recently with Jiri. He suggested that we ask the fine folks of the SER Users mailing list for their suggestions. Thanks so much, Darren Nay Ionosphere, Inc dnay(a)ionosphere.net (864) 678-3158

19 years, 7 months

[Serusers] how to get call duration in radius accounting stop

by Kamran Ahmad

hi how to get call duration in radius. there should be callduration in accounting stop but here in my case there is no callduration Acct-Status-Type = Stop Service-Type = Sip-Session Sip-Response-Code = 200 Sip-Method = 8 User-Name = "4000@ser" Calling-Station-Id = "sip:4000@ser" Called-Station-Id = "sip:3000@ser" Sip-Translated-Request-URI = "sip:3000@ser" Acct-Session-Id = "CB13EC9C-9DB4-420F-BEF4-786E6398D714@UA" Sip-To-Tag = "as23df87de" Sip-From-Tag = "290015013442" Sip-Cseq = "2" NAS-IP-Address = 127.0.0.1 NAS-Port = 5060 Acct-Delay-Time = 0 Client-IP-Address = 127.0.0.1 Acct-Unique-Session-Id = "ca12eca5fce40009" Timestamp = 1112912023 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

19 years, 7 months

Re: [Serusers] Ser 0.9.0 and Cisco Voice Gateway

by Ahmad Cheikh-Moussa

Hi Steve! Now it works properly. Like you wrote the port command was missed in the dial peer. dial-peer voice 1 pots description Default-Dial-peer fuer ausgehende Anrufe preference 3 service session max-conn 25 destination-pattern 0T progress_ind alert enable 8 direct-inward-dial port 0/0/1:15 Now I have activated the www_authorize section. # Uncomment this if you want to use digest authentication if (!www_authorize("netuse.de", "subscriber")) { www_challenge("netuse.de", "1"); break; }; On my cisco I see following when I enable the ccsip debugging: Apr 21 09:24:52.933 MEST: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpSocketReads: Msg enqueued for SPI with IP addr: 192.168.254.30:5060 Apr 21 09:24:52.933 MEST: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x00000000 Apr 21 09:24:52.933 MEST: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: Received: SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.254.203:5060;branch=z9hG4bK2924EA From: "0*" <sip:0*@192.168.254.30>;tag=E7AF75C-13AE To: "0*" <sip:0*@192.168.254.30>;tag=b27e1a1d33761e85846fc98f5f3a7e58.2283 Call-ID: E1A23104-B0DA11D9-81B582BA-75F29624 CSeq: 42 REGISTER WWW-Authenticate: Digest realm="netuse.de", nonce="426756705993d4a9785e2e828158f76faa5234d4", qop="auth" Server: Sip EXpress router (0.9.0 (sparc64/solaris)) Content-Length: 0 Warning: 392 192.168.254.30:5060 "Noisy feedback tells: pid=16087 req_src_ip=192.168.254.203 req_src_port=52773 in_uri=sip:192.168.254.30:5060 out_uri=sip:192.168.254.30:5060 via_cnt==1" Apr 21 09:24:52.933 MEST: //-1/000000000000/SIP/Error/sipSPIHandleAuthChallenge: Error getting credentials Apr 21 09:24:52.933 MEST: //-1/000000000000/SIP/Info/sipSPIUdeleteCcbFromUACTable: ****Deleting from UAC table. Apr 21 09:24:52.933 MEST: //-1/000000000000/SIP/Info/sipSPIUdeleteCcbFromTable: Deleting from table. ccb=0x45D7009C key=E1A23104-B0DA11D9-81B582BA-75F29624 Apr 21 09:24:52.933 MEST: //-1/000000000000/SIP/Info/sipSPIFlushEventBufferQueue: There are 0 events on the internal queue that are going to be free'd Apr 21 09:24:52.933 MEST: //-1/000000000000/SIP/Info/sipSPIUfreeOneCCB: Freeing ccb 45D7009C It looks like the cisco tries to registering to the server, but the server decline this. How can I enable the registering of my gateway in ser, without to disable the www_authorize ? Regards, Ahmad On Apr 20, 05, Steve Blair wrote: > > > Ahmad Cheikh Moussa wrote: > > >Hi! > > > >> > >>>Can I ask you some questions? > >>>How do I know, that my ser server only act as registrar and > >>>redirect Server ? With redirect I mean, any other calls, which > >>>starts with 0, redirect to the gateway. > >> > >> > >> > >>I'm not sure I understand. Are you concerned about people outside > >>of your user community routing calls through your proxy and out to the > >>PSTN? If so then you need to use check_from and check_to to > >>determine if the caller is authenticated to your proxy. > > > >I have following line in ser.cfg > >t_relay_to_udp("192.168.254.203", "5060"); > >when I understand you right, then I have to change this paramater to > >sl_relay_to_udp("192.168.254.203", "5060"); > > > No, the t_relay is fine. > > >This would mean stateless forwarding to this gateway ? > >correct ? > > > >Regars, > > Ahmad > > > > -- > > ISC Network Engineering > The University of Pennsylvania > 3401 Walnut Street, Suite 221A > Philadelphia, PA 19104 > > > voice: 215-573-8396 > > 215-746-8001 > > fax: 215-898-9348 > > sip:blairs@upenn.edu > -- Ahmad Cheikh-Moussa NetUSE AG Dr.-Hell-Straße, 24107 Kiel, Germany Telefon: +49 431 2390 400 -- Telefax: +49 431 2390 499 Service: Service(a)NetUSE.DE -- http://NetUSE.DE/

19 years, 7 months

[Serusers] HELP Needed! SER Crashes.

by Aleksandr N/A

Hi! I have some problems with SER 0.8.14. When I'm trying AUTH modules, it crashes. (it says: --------------------------------------------------------------------------------------------------- Starting SER : cat: /var/run/ser.pid: No such file or directory started pid() --------------------------------------------------------------------------------------------------- My config is the following: # # $Id: ser.cfg,v 1.21.2.1 2003/07/30 16:46:18 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 debug=7 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" # 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 (len_gt( max_len )) { 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 record_route(); # loose-route processing if (loose_route()) { t_relay(); 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("ignosya.dyndns.org", "subscriber")) { www_challenge("ignosya.dyndns.org", "0"); break; }; save("location"); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; # forward to current uri now; use stateful forwarding; that # works reliably even if we forward from TCP to UDP if (!t_relay()) { sl_reply_error(); }; }

19 years, 7 months

[Serusers] (no subject)

by Clay Bryan

Hi, I loaded serweb on my gentoo box and when I open the my_account.php I get a error highlighted in red sorry - fifo reading error. Has anyone else encountered this problem and if so how can I fix it. Wercs Communications Clay Bryan Network Administrator Wercs Communications 400 East First Casper, WY 82601 <http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=400+East+First&csz=Caspe r%2C+WY++82601&country=us> CBryan(a)wercs.com <mailto:CBryan@wercs.com> tel: fax: mobile: 307-233-8359 307-233-8701 307-258-7371 Add me to your address book... <https://www.plaxo.com/add_me?u=21475170292&v0=646557&k0=282754785> Want a signature like this? <http://www.plaxo.com/signature>

19 years, 7 months

← Newer
1
...
21
22
23
24
25
26
27
...
70
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 April 2005