sr-users February 2004

sr-users@lists.kamailio.org

144 participants
382 discussions

RE: [Serusers] CPL
by Toni Barata 26 Feb '04

26 Feb '04

Hi Bogdan, The version of ser is 0.8.13. (I will update from cvs today) About the timeout issue, ok, the proxy no answer works with the "tm" modparams. My question now is, how to configure a proxy no answer and busy for the same user who will upload the script? Thanks again, Toni -----Original Message----- From: Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de] Sent: quinta-feira, 26 de Fevereiro de 2004 12:02 To: Toni Barata Cc: 'serusers(a)lists.iptel.org' Subject: Re: [Serusers] CPL Hi Tony, First one question: what ser version are you using? The noanswer issue was previous disscused on the mailing list - here is some copy past : Try to do the followings: modparam("tm","noisy_ctimer",1) # this will force timeout modparam("tm","fr_inv_timer",30) # sets the timeout for INVITE to 40 sec (default is 120) Please tell me if this works for you. Toni Barata wrote: > Hi Bogdan, > > Thanks for the recomendation ;-) > But I still have some troubles with the script for "proxy if no answer". > If I upload the following script on the user, e.g. "client1", the > "proxy if no answer" works for the new url (in the first location tag): > > <cpl> > <incoming> > <location url="sip:client2@10.112.128.5"> > <proxy> > <noanswer> > <location url="sip:client3@10.112.128.5"> > <proxy /> > </location> > </noanswer> > </proxy> > </location> > </incoming> > </cpl> > > But if the "new" url is the same of the client who have uploaded the > script (client1), like in the following script, the ser respond with a > "too many hops error": > make sens to do so. If somebody calls user client1, it's script will do proxy to himself (to clinet1) and the request will hit again the proxy, the CPL script will be run again, and so one..... > <cpl> > <incoming> > <location url="sip:client1@10.112.128.5"> > <proxy> > <noanswer> > <location url="sip:client2@10.112.128.5"> > <proxy /> > </location> > </noanswer> > </proxy> > </location> > </incoming> > </cpl> > > So my question is, how can i implement the script to activate the > proxy no answer to the user who will upload the script? > > Many Thanks, > Toni > > -----Original Message----- > From: Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de] > Sent: quarta-feira, 25 de Fevereiro de 2004 17:49 > To: Toni Barata > Cc: 'serusers(a)lists.iptel.org' > Subject: Re: [Serusers] CPL > > > Hi Toni, > > the problem is that your script is wrong. Please read carefully the > cpl-draft from ietf > http://www.ietf.org/internet-drafts/draft-ietf-iptel-cpl-08.txt (there > are also several examples there). > Some hints: when you do proxy, your location set is empty - there is no > location or lookup tag before and for incoming processing the location > set is init as empty. That's the reason for this message: > (17752) DEBUG:run_proxy: location set found empty -> going on > failure/default branch > and as your proxy tag has no failure/default branch, the interpreter > will return to SER script (default behavior). > > About timeout, yes indeed, it is not supported for the moment. This > parameter is totally ignored. > > Regards, > Bogdan > > > Toni Barata wrote: > > > Hi Bogdan, > > > > We are experiencing some problems with the proxy no answer (timeout > > don't work?) and proxy on busy in our scripts. > > > > > > script for proxy if busy on client "cliente1": > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > <!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'> > > > > <cpl> > > <incoming> > > <proxy ordering="sequential"> > > <busy> > > <location url="sip:1234@10.112.128.5" /> > > </busy> > > </proxy> > > </incoming> > > </cpl> > > > > > > > > > > debug for proxy if busy: > > > > 6(17752) DEBUG:cpl-c:get_dest_user: tring to get user from new_uri > > 6(17752) DEBUG:cpl-c:get_dest_user: tring to get user from R_uri > > 6(17752) DEBUG:get_user_script: fetching script for user > > <cliente1(a)10.112.128.5> > > 6(17752) DEBUG:get_user_script: we got the script len=58 > > 6(17752) DEBUG: t_check: msg id=12 global id=12 T start=0x422bb6a8 > > 6(17752) DEBUG: t_check: T alredy found! > > 6(17752) parse_headers: flags=-1 > > 6(17752) check_via_address(10.112.128.55, 10.112.128.55, 0) > > 6(17752) WARNING:vqm_resize: resize(0) called > > 6(17752) DEBUG: reply sent out. buf=0x80c9c98: SIP/2.0 1..., > > shmem=0x422bd0f8: SIP/2.0 1 > > 6(17752) DEBUG: t_reply: finished > > 6(17752) DEBUG:cpl_run_script: processing CPL node > > 6(17752) DEBUG:cpl_run_script: processing proxy node > > 6(17752) DEBUG:run_proxy: location set found empty -> going on > > failure/default branch !!!!!!!!!!!!!!!!????????????? > > 6(17752) DEBUG:cpl_c:cpl_run_script: running default action > > 6(17752) rewrite(): Rewriting Request-URI with > > 'sip:10.112.128.220:14045' > > > > > > > > > > script for proxy if no answer on client "cliente1": > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > <!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'> > > > > <cpl> > > <incoming> > > <proxy ordering="sequential" timeout="5"> > > <noanswer> > > <location url="sip:666@10.112.128.5" /> > > </noanswer> > > </proxy> > > </incoming> > > </cpl> > > > > > > > > > > debug for proxy if no answer: > > > > 5(17963) DEBUG:cpl-c:get_dest_user: tring to get user from new_uri > > 5(17963) DEBUG:cpl-c:get_dest_user: tring to get user from R_uri > > 5(17963) DEBUG:get_user_script: fetching script for user > > <cliente1(a)10.112.128.5> > > 5(17963) DEBUG:get_user_script: we got the script len=62 > > 5(17963) DEBUG: t_check: msg id=680 global id=680 T start=0x42355b88 > > 5(17963) DEBUG: t_check: T alredy found! > > 5(17963) parse_headers: flags=-1 > > 5(17963) check_via_address(10.112.128.55, 10.112.128.55, 0) > > 5(17963) WARNING:vqm_resize: resize(0) called > > 5(17963) DEBUG: reply sent out. buf=0x80cac78: SIP/2.0 1..., > > shmem=0x422e8a58: SIP/2.0 1 > > 5(17963) DEBUG: t_reply: finished > > 5(17963) DEBUG:cpl_run_script: processing CPL node > > 5(17963) DEBUG:cpl_run_script: processing proxy node > > 5(17963) DEBUG:run_proxy: location set found empty -> going on > > failure/default branch (the same problem!!!!!!!!!!!!!!!) > > > > 5(17963) DEBUG:cpl_c:cpl_run_script: running default action > > 5(17963) rewrite(): Rewriting Request-URI with > > 'sip:10.112.128.220:14045' > > > > Can you help us on these issues? > > > > Best regards, > > Toni > > > > > > > > >

2 1

[Serusers] Authentication at a third party gateway
by Sebastian Dehne 26 Feb '04

26 Feb '04

Hi list, Does anyone know how to configure authentication for a third party gateway? I want to redirect SIP messages from our users to a PSTN gateway, which uses authentication. thanks, Sebastian

1 0

[Serusers] Authentication at a third party gateway
by Sebastian Dehne 26 Feb '04

26 Feb '04

Hi list, Does anyone know how to configure authentication for a third party gateway? I want to redirect SIP messages from our users to a PSTN gateway, which uses authentication. thanks, Sebastian

1 0

[Serusers] NAT
by Shirley Toh 26 Feb '04

26 Feb '04

Hi, Can anyone tell me is SER is routing UA directly out and connect two UA directly or is it connect to SER always to do the transmission of data. Please advice? Regards, Shirley

2 1

RE: FW: [Serusers] Rtpproxy
by Shirley Toh 26 Feb '04

26 Feb '04

Hi, thank you for replying.... Yes my UA do support Symmetric. What are the things that I have to take note on the messages that whether the messages is properly written? And how can I check the IP address and port on the RTP traffic? Please help...is really greatly appreciated. Regards, Shirley > -----Original Message----- > From: Klaus Darilion [SMTP:klaus.mailinglists@pernau.at] > Sent: Thursday, February 26, 2004 5:56 PM > To: Shirley Toh > Cc: SER Users (E-mail) > Subject: Re: FW: [Serusers] Rtpproxy > > You have to provide more information. Which clients (do they support > symmetric RTP?). Take a look at SIP messages when they arive at the > proxy and when they are forwarded and vrify that the messages are > properly rewritten by the nathelper module. > > Check if there is any RTP traffic going to the RTPproxy and if it is > forwarded to the proper IP address and port. > > regards, > Klaus > > Shirley Toh wrote: > > > Hi, > > > > I am using the code below. When I am dialing through this scenario ---> > > UA1(Symmetric NAT) ----> SER ---> UA2 (Symmetric NAT) > > . I hear no audio and I haev no error in my route. Please kindly advise > is > > there something missing or I need to have extra components. I am using > CVS > > rel_0.8.12 and latest rtpproxy!!! Help Help!!! > > > > Regards, > > Shirley > > > > > >>-----Original Message----- > >>From: Shirley Toh > >>Sent: Wednesday, February 25, 2004 6:37 PM > >>To: SER Users (E-mail) > >>Subject: FW: [Serusers] Rtpproxy > >> > >>Hi > >> > >>I have problem calling through UA behind Symmetric network? Please > advice > >>any solution to this problem. Thank you!!! > >> > >>UA1(Symmetric NAT) ----> SER ---> UA2 (Symmetric NAT) > >> > >>Regards, > >>Shirley > >>-----Original Message----- > >>From: Shirley Toh > >>Sent: Tuesday, February 24, 2004 9:09 PM > >>To: 'Jan Janak' > >>Subject: RE: [Serusers] Rtpproxy > >> > >>Hi, > >> > >>Thank you for your answer. > >> > >>Can I check the latest module in CVS does it support to call from > >>Symmetric network to Symmetric network?Please help. If can what sgould I > >>take note in the commands? > >> > >>Regards, > >>Shirley > >> > >>-----Original Message----- > >>From: Jan Janak [SMTP:jan@iptel.org] > >>Sent: Tuesday, February 24, 2004 8:35 PM > >>To: Shirley Toh > >>Cc: SER Users (E-mail) > >>Subject: Re: [Serusers] Rtpproxy > >> > >>You are calling force_rtp_proxy or fix_nated_sdp on a message with empty > >>body. Make sure that you call the functions from the script only when > >>the message contains SDP body (usually INVITE and 200 OK). > >> > >> Jan. > >> > >>On 24-02 11:36, Shirley Toh wrote: > >> > >>>Hi, > >>> > >>>Can anyone help me!! I am having this error on my log file when I try > to > >>>make calls. I have attached my ser.cfg. Please help!! Thanks!! > >>> > >>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20404]: ERROR: > >>>send_rtpp_command: can't read reply from a RTP proxy > >>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20413]: ERROR: > >> > >>extract_body: > >> > >>>message body has lenght zero > >>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20413]: ERROR: > >>>force_rtp_proxy: can't extract body from the message > >>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20413]: ERROR: on_reply > >>>processing failed > >>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20417]: ERROR: > >> > >>extract_body: > >> > >>>message body has lenght zero > >>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20417]: ERROR: > >>>force_rtp_proxy: can't extract body from the message > >>>Feb 24 11:29:54 sipserver2 /usr/local/sbin/ser[20417]: ERROR: on_reply > >>>processing failed > >>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20417]: ERROR: > >> > >>extract_body: > >> > >>>message body has lenght zero > >>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20417]: ERROR: > >>>force_rtp_proxy: can't extract body from the message > >>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20417]: ERROR: on_reply > >>>processing failed > >>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR: > >> > >>extract_body: > >> > >>>message body has lenght zero > >>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR: > >> > >>fix_nated_sdp: > >> > >>>cannot extract body from msg! > >>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR: > >> > >>extract_body: > >> > >>>message body has lenght zero > >>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR: > >>>force_rtp_proxy: can't extract body from the message > >>>Feb 24 11:30:24 sipserver2 /usr/local/sbin/ser[20407]: ERROR: on_reply > >>>processing failed > >>> > >>> <<ser.cfg.txt>> > >>> > >>>regards, > >>>shirley > >>> > >> > >>># > >>># $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 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" > >>>mhomed=yes > >>> > >>># ------------------ 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/nathelper.so" > >>>loadmodule "/usr/local/lib/ser/modules/textops.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) > >>> > >>># -- Nathelper -- > >>>modparam("registrar" , "nat_flag", 6) > >>>modparam("nathelper", "natping_interval", 60) > >>>modparam("nathelper", "ping_nated_only", 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 > max_len ) { > >>> sl_send_reply("513", "Message too big"); > >>> break; > >>> }; > >>> > >>> > >>> #!! Nathelper > >>> if (nat_uac_test("3")){ > >>> if (method == "REGISTER"){ > >>> log("LOG:Someone trying to register from > private > >> > >>IP, rewriting\n"); > >> > >>> fix_nated_contact(); # Rewtite contact with > >> > >>source IP of signalling > >> > >>> if(method== "INVITE"){ > >>> fix_nated_sdp("1"); # Add > >> > >>direction-active to SDP > >> > >>> }; > >>> force_rport(); > >>> setflag(6); > >>> }; > >>> }; > >>> > >>> # 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") { > >>> save("location"); > >>> break; > >>> }; > >>> > >>> # native SIP destinations are handled using our USRLOC > >> > >>DB > >> > >>> if (!lookup("location")) { > >>> sl_send_reply("", "Connecting"); > >>> break; > >>> }; > >>> }; > >>> if (isflagset(6)){ > >>> force_rtp_proxy(); > >>> }; > >>> t_on_reply("1"); > >>> > >>> # 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(); > >>> break; > >>> }; > >>> > >>>} > >>> > >>># all incoming replies for t_onrepli-ed transactions enter here > >>>onreply_route[1] { > >>> if (isflagset(6) && status=~"(183)|2[0-9][0-9]") { > >>> fix_nated_contact(); > >>> fix_nated_sdp("1"); > >>> force_rtp_proxy(); > >>> }else if(nat_uac_test("1")){ > >>> fix_nated_contact(); > >>> force_rtp_proxy(); > >>> }; > >>> > >>>} > >> > >>>_______________________________________________ > >>>Serusers mailing list > >>>serusers(a)lists.iptel.org > >>>http://lists.iptel.org/mailman/listinfo/serusers > > > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > >

2 1

RE: [Serusers] CPL
by Toni Barata 26 Feb '04

26 Feb '04

Hi Bogdan, Thanks for the recomendation ;-) But I still have some troubles with the script for "proxy if no answer". If I upload the following script on the user, e.g. "client1", the "proxy if no answer" works for the new url (in the first location tag): <cpl> <incoming> <location url="sip:client2@10.112.128.5"> <proxy> <noanswer> <location url="sip:client3@10.112.128.5"> <proxy /> </location> </noanswer> </proxy> </location> </incoming> </cpl> But if the "new" url is the same of the client who have uploaded the script (client1), like in the following script, the ser respond with a "too many hops error": <cpl> <incoming> <location url="sip:client1@10.112.128.5"> <proxy> <noanswer> <location url="sip:client2@10.112.128.5"> <proxy /> </location> </noanswer> </proxy> </location> </incoming> </cpl> So my question is, how can i implement the script to activate the proxy no answer to the user who will upload the script? Many Thanks, Toni -----Original Message----- From: Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de] Sent: quarta-feira, 25 de Fevereiro de 2004 17:49 To: Toni Barata Cc: 'serusers(a)lists.iptel.org' Subject: Re: [Serusers] CPL Hi Toni, the problem is that your script is wrong. Please read carefully the cpl-draft from ietf http://www.ietf.org/internet-drafts/draft-ietf-iptel-cpl-08.txt (there are also several examples there). Some hints: when you do proxy, your location set is empty - there is no location or lookup tag before and for incoming processing the location set is init as empty. That's the reason for this message: (17752) DEBUG:run_proxy: location set found empty -> going on failure/default branch and as your proxy tag has no failure/default branch, the interpreter will return to SER script (default behavior). About timeout, yes indeed, it is not supported for the moment. This parameter is totally ignored. Regards, Bogdan Toni Barata wrote: > Hi Bogdan, > > We are experiencing some problems with the proxy no answer (timeout > don't work?) and proxy on busy in our scripts. > > > script for proxy if busy on client "cliente1": > > <?xml version="1.0" encoding="UTF-8"?> > > <!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'> > > <cpl> > <incoming> > <proxy ordering="sequential"> > <busy> > <location url="sip:1234@10.112.128.5" /> > </busy> > </proxy> > </incoming> > </cpl> > > > > > debug for proxy if busy: > > 6(17752) DEBUG:cpl-c:get_dest_user: tring to get user from new_uri > 6(17752) DEBUG:cpl-c:get_dest_user: tring to get user from R_uri > 6(17752) DEBUG:get_user_script: fetching script for user > <cliente1(a)10.112.128.5> > 6(17752) DEBUG:get_user_script: we got the script len=58 > 6(17752) DEBUG: t_check: msg id=12 global id=12 T start=0x422bb6a8 > 6(17752) DEBUG: t_check: T alredy found! > 6(17752) parse_headers: flags=-1 > 6(17752) check_via_address(10.112.128.55, 10.112.128.55, 0) > 6(17752) WARNING:vqm_resize: resize(0) called > 6(17752) DEBUG: reply sent out. buf=0x80c9c98: SIP/2.0 1..., > shmem=0x422bd0f8: SIP/2.0 1 > 6(17752) DEBUG: t_reply: finished > 6(17752) DEBUG:cpl_run_script: processing CPL node > 6(17752) DEBUG:cpl_run_script: processing proxy node > 6(17752) DEBUG:run_proxy: location set found empty -> going on > failure/default branch !!!!!!!!!!!!!!!!????????????? > 6(17752) DEBUG:cpl_c:cpl_run_script: running default action > 6(17752) rewrite(): Rewriting Request-URI with > 'sip:10.112.128.220:14045' > > > > > script for proxy if no answer on client "cliente1": > > <?xml version="1.0" encoding="UTF-8"?> > > <!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'> > > <cpl> > <incoming> > <proxy ordering="sequential" timeout="5"> > <noanswer> > <location url="sip:666@10.112.128.5" /> > </noanswer> > </proxy> > </incoming> > </cpl> > > > > > debug for proxy if no answer: > > 5(17963) DEBUG:cpl-c:get_dest_user: tring to get user from new_uri > 5(17963) DEBUG:cpl-c:get_dest_user: tring to get user from R_uri > 5(17963) DEBUG:get_user_script: fetching script for user > <cliente1(a)10.112.128.5> > 5(17963) DEBUG:get_user_script: we got the script len=62 > 5(17963) DEBUG: t_check: msg id=680 global id=680 T start=0x42355b88 > 5(17963) DEBUG: t_check: T alredy found! > 5(17963) parse_headers: flags=-1 > 5(17963) check_via_address(10.112.128.55, 10.112.128.55, 0) > 5(17963) WARNING:vqm_resize: resize(0) called > 5(17963) DEBUG: reply sent out. buf=0x80cac78: SIP/2.0 1..., > shmem=0x422e8a58: SIP/2.0 1 > 5(17963) DEBUG: t_reply: finished > 5(17963) DEBUG:cpl_run_script: processing CPL node > 5(17963) DEBUG:cpl_run_script: processing proxy node > 5(17963) DEBUG:run_proxy: location set found empty -> going on > failure/default branch (the same problem!!!!!!!!!!!!!!!) > > 5(17963) DEBUG:cpl_c:cpl_run_script: running default action > 5(17963) rewrite(): Rewriting Request-URI with > 'sip:10.112.128.220:14045' > > Can you help us on these issues? > > Best regards, > Toni > > > >

2 1

RE: [Serusers] SEMS
by Kapil Dhawan 26 Feb '04

26 Feb '04

hi.... its not only the phone no...it can be like any regret message..or some greeting..also.....i hope i need to work on announcement....basically announcement module plays one file only can i have some way and pass some argument to it..so that it plays ore than one file... >From: "Kapil Dhawan" <sersavvy(a)hotmail.com> >To: serusers(a)lists.iptel.org >Subject: [Serusers] SEMS >Date: Thu, 26 Feb 2004 10:46:51 +0000 > >Hi...How can we use sems to listen our username (phone no) on phone...lets >say user pressed some combination and we want to play his phone no...How >can this be done > >_________________________________________________________________ >Contact brides & grooms FREE! http://www.shaadi.com/ptnr.php?ptnr=hmltag >Only on www.shaadi.com. Register now! > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers _________________________________________________________________ Marriage? Join BharatMatrimony.com. http://www.bharatmatrimony.com/cgi-bin/bmclicks1.cgi?74

1 0

[Serusers] radius - compilation errors
by Dawid Mielnik 26 Feb '04

26 Feb '04

Hi, I'm trying to compile ser with suport for radius accounting. When I uncomment: DEFS+=-DRAD_ACC -I$(LOCALBASE)/include LIBS=-L$(LOCALBASE)/lib -lradiusclient in acc modle Makefile and remove auth_radius, group_radius, uri_radius from exclude modules list in main Makefile I get compilation errors when compiling ser. Am I missing something ? Im using 0.8.12 stable CVS branch on red hat 9. Some of the errors below. Any help apreciated. Dave from make all: make[1]: Entering directory `/root/ser/nathelpercvs/sip_router/modules/uri_radius' ../../Makefile.rules:77: checks.d: No such file or directory ../../Makefile.rules:77: urirad_mod.d: No such file or directory make[1]: Leaving directory `/root/ser/nathelpercvs/sip_router/modules/uri_radius' make[1]: Entering directory `/root/ser/nathelpercvs/sip_router/modules/uri_radius' gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-str ingops -malign-double -falign-loops -mcpu=athlon -DNAME='"ser"' -DVERSI ON='"0.8.12-tcp_nonb"' -DARCH='"i386"' -DOS='"linux"' -DCOMPILER='"gcc 3.2"' -D__CPU_i386 -D__OS_linux -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALL OC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_TCP -DDISABLE_NAGLE -DF_MALLOC -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DHAVE_G ETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHA VE_MSGHDR_MSG_CONTROL -c checks.c -o checks.o checks.c: In function `radius_does_uri_exist': checks.c:77: warning: passing arg 1 of `rc_avpair_add' from incompatible pointer type checks.c:77: warning: passing arg 2 of `rc_avpair_add' makes pointer from integer without a cast checks.c:77: warning: passing arg 3 of `rc_avpair_add' makes integer from pointer without a cast checks.c:77: too few arguments to function `rc_avpair_add' checks.c:85: warning: passing arg 1 of `rc_avpair_add' from incompatible pointer type checks.c:85: warning: passing arg 2 of `rc_avpair_add' makes pointer from integer without a cast checks.c:85: warning: passing arg 3 of `rc_avpair_add' makes integer from pointer without a cast checks.c:85: too few arguments to function `rc_avpair_add' checks.c:92: warning: passing arg 2 of `rc_auth' makes integer from pointer without a cast checks.c:92: warning: passing arg 3 of `rc_auth' from incompatible pointer type checks.c:92: warning: passing arg 4 of `rc_auth' from incompatible pointer type checks.c:92: too few arguments to function `rc_auth' make[1]: *** [checks.o] Error 1 make[1]: Leaving directory `/root/ser/nathelpercvs/sip_router/modules/uri_radius' from make install: ERROR: module modules/acc/acc.so not compiled ERROR: module modules/auth_radius/auth_radius.so not compiled ERROR: module modules/group_radius/group_radius.so not compiled ERROR: module modules/sip_router/sip_router.so not compiled ERROR: module modules/uri_radius/uri_radius.so not compiled touch /usr/local/share/doc/ser//INSTALL install -m 644 INSTALL /usr/local/share/doc/ser/

2 2

[Serusers] Alias and "cross-references" (looping?).
by Johan Larsson 26 Feb '04

26 Feb '04

Hello. I'm trying to set-up a system with a cisco pstn-gw and cisco-ip-phones and Messenger as UA:s. I want every users clients to ring if someone is calling, either if it's by using sip:NUMBER@domain or sip:USERNAME@domain. I.e. User 1: External phone-number 12345 Internal phone-number 2345@domain (cisco-phone registers as this) Messenger joe@domain So, if a call comes in via the pstn-gw i want the Cisco-phone and the Messenger to be INVITED. I have solved this by adding 12345@domain as an alias for joe@domain. Now, the problem, if i from the inside is calling 2345 from another phone (say 2346) i want both the phone and the Messenger to be INVITED. And if i'm inviting joe@domain through another messenger i also want the phone 2345 to be invited. How is this solved best? I have tried to add perm usrloc entries for joe@domain to 2345@domain and for 2345@domain to joe@domain. This almost seems to be working, but if i'm calling from the outside and hang-up before answering, the cisco-phone starts to ring again :/ Like it is getting invited all over again. I hope someone understands the problem, this should be rather normal (if someone is calling i want to be invited on all my devices...). Johan

1 0

[Serusers] SERWEB- Warning: fopen("/tmp/ser_fifo", "w") - Permission denied
by alan chiu 26 Feb '04

26 Feb '04

I haven't had this problem with serweb before but today my serweb>user_interface site is giving me the following error at the top of the page. Can't figure out what's wrong, everything seems to be intact. ser.cfg has fifo="/tmp/ser_fifo". Checked this month's mailing list archive but seems like no one experienced the same problem. Any pointers will be appreciated. *****On user interface site (logged in) *************** Warning: fopen("/tmp/ser_fifo", "w") - Permission denied in /var/www/html/functions.php on line 206 sorry -- cannot open write fifo" name=Author> ************************************************************ *********in serweb's functions.php*********** 206 /* open fifo now */ 207 $fifo_handle=fopen( $config->fifo_server, "w" ); 208 if (!$fifo_handle) { 209 $errors[]="sorry -- cannot open write fifo"; return; ************************************************** *********in serweb's config.php******************************************* $this->fifo_server="/tmp/ser_fifo"; ****************************************************************************** --------------------------------- Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want.

8 11

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users February 2004