sr-users February 2004

sr-users@lists.kamailio.org

144 participants
382 discussions

RE: FW: [Serusers] Rtpproxy & UDP
by Shirley Toh 27 Feb '04

27 Feb '04

Hi, Thank you for the reply. 1. Can I checked on the SIP messages Status == 200 OK, there is a <Contact: <sip:joo@ip:port>> field. May I know on the onreply_route what is the command that is control this field on the IP and Port is have the reply_route like below when my UA is behind the fire-wall: onreply_route[1] { if (isflagset(6) && status=~"2[0-9][0-9]") { fix_nated_contact(); fix_nated_sdp("1"); force_rtp_proxy(); }else{ fix_nated_contact(); fix_nated_sdp("3"); force_rtp_proxy(); } 2. What is function in ser.cfg is sending the UDP to the Ethereal? As when I have UA1 calling to UA2, I cannot see any UDP messages on the Ethereal. Please advice what is the command that is doing the RTP or UDP, is it force_rtp_proxy() or t_on_reply("1") or etc. Thanks alot......:) p/s: kindly cc to j2xue(a)singnet.com.sg Regards, Shirley > -----Original Message----- > From: Klaus Darilion [SMTP:klaus.mailinglists@pernau.at] > Sent: Thursday, February 26, 2004 10:35 PM > To: Shirley Toh; Serusers > Subject: Re: FW: [Serusers] Rtpproxy > > Search the mailing list archive for configuration samples! > > regards, > klaus > > PS: cc to the mailing list! > > Shirley Toh wrote: > > > Hi , > > > > How about the force_rtp_proxy? Where should I appropriate apply this > > command? The current Nat module have no problem going through from > Symmetric > > Newtwork to Symmetric Network right? Thank you for your answer it really > > helps!!! :) > > > > Regards, > > Shirley > > > > > >>-----Original Message----- > >>From: Klaus Darilion [SMTP:klaus.mailinglists@pernau.at] > >>Sent: Thursday, February 26, 2004 8:18 PM > >>To: Shirley Toh > >>Cc: SER Users (E-mail) > >>Subject: Re: FW: [Serusers] Rtpproxy > >> > >>start ethereal on the machine with the SIP&RTP proxy. as filter use: UDP > >>Then take a look at the SIP messages. The nathelper module has to > >>rewrite the IP-address and the port in the SDP of the INVITE and the 200 > > >>OK message. > >> > >>klaus > >> > >>Shirley Toh wrote: > >> > >>>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

[Serusers] SerWEB PROBLEM 2
by Sergio Gerardo Festa 27 Feb '04

27 Feb '04

Hi I have problems in order that Serweb. works correctly do not manage to accede not user commonly, not admin. I have modified the lines - short_open_tag = on and - register_globals = on of php.ini Always it he gives me the same mistake " Bad username or password " I work on a linux with: RH9 Php-4.2.2-17 Httpd-2.0.40-21 Mysql-3.23.54a-11 Someone can help me? Thank you Saludos! Sergio Gerardo Festa

3 3

[Serusers] Failure route and time out.
by Laurent BURGY 27 Feb '04

27 Feb '04

Hi, I want to know if i can see in the ser.cfg why the execution goes in a failure route ( to differentiate a negative reply and a timer hits) in order to perform reply processing... I didn't see ( or understand ) how to do this....I don't think that you can parse the reply to see the return code... The only way i see right now is to build a module and register to the TMCB_ON_FAILURE event to see if there is a FAKED_REPLY ( but i don't know if this callback can pass this value) but maybe there is an easier way... I need some help thx Laurent

2 3

[Serusers] upgrading from 0.8.11 to 0.8.12 db upgrade error.
by Jev 27 Feb '04

27 Feb '04

When I attempt to 'upgrade' my database using the ser_mysql.sh reinstall command I get the following error: robusto# ser_mysql.sh reinstall MySql password for root: creating backup database dumping table content (ser) dropping table (ser) creating new structures creating database ser ... restoring table content ERROR 1054 at line 21: Unknown column 'usernamename' in 'field list' reinstall: restoring table failed robusto# I'm running mysql-4.0.17 on a FreeBSD 5.2.1-RELEASE machine. Thanks, -Jev

1 0

[Serusers] proxy + nat in the same box
by Eduard San Anselmo Mateu 27 Feb '04

27 Feb '04

Hello everyone. I have read lots of posts to this list and whitepapers about NAT traversal with SIP, but all of them refer to the same problem: the endpoint is behind a nat box and SER is after that box. My question is regarding the situation in which SER resides at the same box than NAT. Here's a diagram (sorry for that awful ascii-art, never been a good artist): _____ ______ ______ _____ | | | | | | | | | A |------| FW |----- INTERNET ----| |-------| B | |_____| | NAT | | NAT | |_____| | SER | | | 192.168.0.90 |______| IPpA IPpB |______| 10.0.0.70 IPpA and IPpB are the public IP addresses of A and B, respectively. SER is listening on its private IP. Of course, the SER box also has an RTP proxy. I think there's no problem with RTP, because nathelper's exported functions can deal with the problem of changing SDP's fields. My problem has to deal with SIP, specially when B invites A into a conversation, and A has to give an answer. In that case, when SER has to repeat that answer to B, what will it write in the Record-Route header field? It should write IPpA so that B can get to SER in the future, but if SER's listening on its private IP, I'm afraid it will write that public IP in Record-Route. Can anybody please point me in the right direction, or at least address me to a place where all this may be explained (not the RFC, please!)?. Thanks in advance. Eduard San Anselmo

2 1

[Serusers] replication and rtpproxy
by Arnd Vehling 27 Feb '04

27 Feb '04

Hello, ive got a couple of question of the t_replicate feature of the tm module. First, ive found the follwing note in modules/tm/README (8.0.12 CVS stable): ---- * t_replicate should be done more cleanly--Vias, Routes, etc. should be removed from a message prior to replicating it (well, does not matter any longer so much as there is a new replication module). ---- Can someone comment on what may be the consequences of using t_replicate which is "not done so cleanly" and where i may get a copy of this "new replication" module? If its under open source licence, that is. Next question :) Is there any way that a failover server pickups the neccessary port bindings for portaones rtpproxy or do will all "rtpproxied" sessions fail when a failover server will take over a primary server? best regards, Arnd

5 24

Fw: [Serusers] replication and rtpproxy
by Andres 27 Feb '04

27 Feb '04

No...our SIP server DNS entries time out at 5 minutes. It does not matter where the entry is cached. Unless it is cached by someone who ignores our TTL...but that has not been the case so far. ----- Original Message ----- From: "Klaus Darilion" <klaus.mailinglists(a)pernau.at> To: "Andres" <andres(a)telesip.net> Cc: "Nils Ohlmeier" <nils(a)iptel.org>; <serusers(a)lists.iptel.org> Sent: Thursday, February 26, 2004 12:54 PM Subject: Re: [Serusers] replication and rtpproxy > But this will work only if the client uses your DNS servers, because the > DNS entries are cached by the other nameservers - or do you have a very > short TTL configured? > > I think also softclients will have problems as Windows XP by default > caches the DNS lookups. > > regards, > klaus > > Andres wrote: > > Hi Klaus, > > > > We use DNS updates. We have special scripts based on sipsak (Thanks Nils!), > > that check all SIP servers every minute. If something is wrong, then we > > update our DNS dynamically to point to another SIP Server. If the UAs are > > unable to register then they redo their DNS query and find the new IP. > > Works quite well in combination with replication since the backup server has > > the exact duplicate location table. > > > > Regards, > > Andres > > > > ----- Original Message ----- > > From: "Klaus Darilion" <klaus.mailinglists(a)pernau.at> > > To: "Nils Ohlmeier" <nils(a)iptel.org> > > Cc: <serusers(a)lists.iptel.org> > > Sent: Thursday, February 26, 2004 9:59 AM > > Subject: Re: [Serusers] replication and rtpproxy > > > > > > > >> > >>Nils Ohlmeier wrote: > >> > >>>On Thursday 26 February 2004 03:28, Arnd Vehling wrote: > >>> > >>>>Next question :) Is there any way that a failover server pickups the > >>>>neccessary port bindings for portaones rtpproxy or do will all > >>>>"rtpproxied" sessions fail when a failover server will take over > >>>>a primary server? > >>> > >>> > >>>As currently the rtp-proxy has to run on the same host as SER it does > > > > not make > > > >>>much sence IMHO to think about taking over rtp-proxy sessions. Then you > > > > would > > > >>>need some kind of rtp-proxy session replication, which should be easy > > > > when > > > >>>the nathelper module and the rtp proxy ever uses IP protocol for > >>>communication. But all this will only work if the backup server takes > > > > over > > > >>>the IP of the failed server, and you are not using SRV backup servers > > > > for > > > >>>example (except that a SRV backup can obviously also can takeover the > > > > IP). > > > >>Is it yet possible to build redundancy on top of SRV? I tested some > >>clients (Xlite, Budgetone-100, Windows Messenger 4.7) wether they use > >>SRV records to locate the proxy and Messenger is the only one who uses it. > >> > >>So, if I use these clients, is there any other failover solution than IP > >>takeover? > >> > >>regards, > >>klaus > >> > >>_______________________________________________ > >>Serusers mailing list > >>serusers(a)lists.iptel.org > >>http://lists.iptel.org/mailman/listinfo/serusers > >> > > > > > > > > >

1 0

[Serusers] question about ser and vocal
by listas iPfone 26 Feb '04

26 Feb '04

Hi All, I need to set up a system to people register free sip adresses. The question is: Why do you use ser and not vocal? What are the diferences and vantages about vocal and ser? regards Miklos

4 3

[Serusers] Hi
by Firoze Pasha 26 Feb '04

26 Feb '04

Hi I am trying to run SER on Linux box. I am not able to send register request from ATA. I have default ser.cfg, no authentication and no database as of now. Can any one help me please. Thanks

1 0

[Serusers] Need help with cryptic error messages
by Mike Dehn 26 Feb '04

26 Feb '04

I posted a request for help yesterday, but perhaps my subject line was too cryptic. At any rate, we are stumped with the SER errors from the syslog shown below. Installation is from the CVS unstable branch. Can anyone suggest what we might be doing wrong? Thanks - Mike Feb 26 14:18:50 dhcp-3258-41 ser: Listening on Feb 26 14:18:50 dhcp-3258-41 ser: udp: 127.0.0.1 [127.0.0.1]:5060 Feb 26 14:18:50 dhcp-3258-41 ser: udp: 220.15.47.139 [220.15.47.139]:5060 Feb 26 14:18:50 dhcp-3258-41 ser: tcp: 127.0.0.1 [127.0.0.1]:5060 Feb 26 14:18:50 dhcp-3258-41 ser: tcp: 220.15.47.139 [220.15.47.139]:5060 Feb 26 14:18:50 dhcp-3258-41 ser: Aliases: Feb 26 14:18:50 dhcp-3258-41 ser: tcp: 220-15-47-139.c3-0.129-ubr4.lnh-129.md.cable.rcn.com:5060 Feb 26 14:18:50 dhcp-3258-41 ser: tcp: localhost:5060 Feb 26 14:18:50 dhcp-3258-41 ser: tcp: localhost.localdomain:5060 Feb 26 14:18:50 dhcp-3258-41 ser: udp: 220-15-47-139.c3-0.129-ubr4.lnh-129.md.cable.rcn.com:5060 Feb 26 14:18:50 dhcp-3258-41 ser: udp: localhost:5060 Feb 26 14:18:50 dhcp-3258-41 ser: udp: localhost.localdomain:5060 Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4808]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4820]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4810]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 ser: *: sip-dc.mistcreek.com:* Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4811]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4812]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4813]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4814]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4815]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4816]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4817]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4818]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4821]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4822]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4809]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4819]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4823]: NOTICE:init_avp_child: no avp_db_url specified -> feature disabled Feb 26 14:18:50 dhcp-3258-41 /usr/local/sbin/ser[4824]: WARNING: no fifo_db_url given - fifo DB commands disabled! Feb 26 14:18:50 dhcp-3258-41 ser: *: anywhere:* Feb 26 14:18:50 dhcp-3258-41 ser: Feb 26 14:18:50 dhcp-3258-41 ser: ser startup succeeded

2 1

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