sr-users November 2003

sr-users@lists.kamailio.org

116 participants
267 discussions

[Serusers] CANCEL and ACK in 0.8.12 problems (noise)
by Greg Fausak 25 Nov '03

25 Nov '03

I just loaded the 0.8.12 server on my lab linux 9.x box. Running postgres/2 current registrations, 123456(a)named.com and 9723937976(a)named.com. My configuration allows calls between these two no problem. I can hangup from either end with no problem. I am seeing a problem with a CANCEL message. If one end calls the other, and than CANCELs the communication before the other end ACKs, I get several messages CANCEL ACK CANCEL ACK ... I read the serusers list and see that Maxim and Andrea reported the same problem. I don't see the problem in my production configuration on 0.8.11. What can I do to make the CANCEL work? Here is my configuration: UA1 XTEN XPRO UA2 Cisco 7960 SER 0.8.12 configuration: -------------start--------------- 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; }; # 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"); xlog("L_WARN", "LOOSE: %Ts call-id:%ci cseq:%ci contact:%ct from:%fu fromtag:%ft to:%tu totag:%tt method:%rm ruri:%ru messageid:%mi\n"); setflag(1); setflag(2); 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") { if (!www_authorize("named.com", "subscriber")) { www_challenge("named.com", "0"); break; }; save("location"); break; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; if (method=="INVITE") { if (!www_authorize("named.com", "subscriber")) { www_challenge("named.com", "0"); break; }; xlog("L_WARN", "INVITE: %Ts call-id:%ci cseq:%ci contact:%ct from:%fu fromtag:%ft to:%tu totag:%tt method:%rm ruri:%ru messageid:%mi\n"); # if (lookup("location")) { route(1); break; }; if(uri=~"sip:[0-9]{10}@.*") { xlog("L_WARN", "10DIGIT: %Ts call-id:%ci cseq:%ci contact:%ct from:%fu fromtag:%ft to:%tu totag:%tt method:%rm ruri:%ru messageid:%mi\n"); route(2); break; } xlog("L_WARN", "UNKNOWN: %Ts call-id:%ci cseq:%ci contact:%ct from:%fu fromtag:%ft to:%tu totag:%tt method:%rm ruri:%ru messageid:%mi\n"); sl_send_reply("580", "Sorry"); break; }; if (method=="CANCEL") { xlog("L_WARN", "CANCEL: %Ts call-id:%ci cseq:%ci contact:%ct from:%fu fromtag:%ft to:%tu totag:%tt method:%rm ruri:%ru messageid:%mi\n"); route(2); break; }; if (method=="BYE") { xlog("L_WARN", "BYE: %Ts call-id:%ci cseq:%ci contact:%ct from:%fu fromtag:%ft to:%tu totag:%tt method:%rm ruri:%ru messageid:%mi\n"); route(2); break; }; if (method=="ACK") { xlog("L_WARN", "ACK: %Ts call-id:%ci cseq:%ci contact:%ct from:%fu fromtag:%ft to:%tu totag:%tt method:%rm ruri:%ru messageid:%mi\n"); break; }; sl_send_reply("404", "Not Found"); break; }; xlog("L_WARN", "FAILATBOTTOM: %Ts call-id:%ci cseq:%ci contact:%ct from:%fu fromtag:%ft to:%tu totag:%tt method:%rm ruri:%ru messageid:%mi\n"); break; } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; } route[2] { consume_credentials(); rewritehostport("1.2.3.4:5060"); if(!t_relay()) { sl_reply_error(); break; }; } -------------------- here are the ngrep packets, from invite to duplicate CANCEL packets... # U 2003/11/22 13:10:32.356665 66.228.44.254:5060 -> 66.228.53.218:5060 INVITE sip:9723937976@66.228.53.218:5060 SIP/2.0. Max-Forwards: 10. Record-Route: <sip:9723937976@66.228.44.254;ftag=320951244;lr>. Via: SIP/2.0/UDP 66.228.44.254;branch=z9hG4bKe198.142630c1.0. Via: SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>. Contact: <sip:123456@66.228.53.216:5060>. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 INVITE. Authorization: Digest username="123456",realm="named.com",nonce="3fbfb5d42576afa9e9384c4f0f16427e46909d1d",response="7bf9fe190978d98811d56ddb60dded2f",uri="sip:9723937976@named.com". Content-Type: application/sdp. User-Agent: X-PRO build 1050. Content-Length: 322. . v=0. o=123456 485850365 485850365 IN IP4 66.228.53.216. s=X-PRO. c=IN IP4 66.228.53.216. t=0 0. m=audio 8000 RTP/AVP 0 8 3 4 98 97 101. a=rtpmap:0 pcmu/8000. a=rtpmap:8 pcma/8000. a=rtpmap:3 gsm/8000. a=rtpmap:4 G723/8000. a=rtpmap:98 iLBC/8000. a=rtpmap:97 speex/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. # U 2003/11/22 13:10:32.619424 66.228.53.218:50560 -> 66.228.44.254:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP 66.228.44.254;branch=z9hG4bKe198.142630c1.0,SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 INVITE. Server: CSCO/5. Contact: <sip:9723937976@66.228.53.218:5060>. Record-Route: <sip:9723937976@66.228.44.254;ftag=320951244;lr>. Content-Length: 0. . # U 2003/11/22 13:10:32.728062 66.228.53.218:50561 -> 66.228.44.254:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 66.228.44.254;branch=z9hG4bKe198.142630c1.0,SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>;tag=000b5faab82400151dddd662-025452b6. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 INVITE. Server: CSCO/5. Contact: <sip:9723937976@66.228.53.218:5060>. Record-Route: <sip:9723937976@66.228.44.254;ftag=320951244;lr>. Content-Length: 0. . # U 2003/11/22 13:10:32.728480 66.228.44.254:5060 -> 66.228.53.216:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>;tag=000b5faab82400151dddd662-025452b6. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 INVITE. Server: CSCO/5. Contact: <sip:9723937976@66.228.53.218:5060>. Record-Route: <sip:9723937976@66.228.44.254;ftag=320951244;lr>. Content-Length: 0. . # U 2003/11/22 13:10:34.846506 66.228.53.216:5060 -> 66.228.44.254:5060 CANCEL sip:9723937976@named.com SIP/2.0. Via: SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>. Contact: <sip:123456@66.228.53.216:5060>. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 CANCEL. User-Agent: X-PRO build 1050. Content-Length: 0. . # U 2003/11/22 13:10:34.847662 66.228.44.254:5060 -> 66.228.53.218:5060 CANCEL sip:9723937976@66.228.53.218:5060 SIP/2.0. Max-Forwards: 10. Record-Route: <sip:9723937976@66.228.44.254;ftag=320951244;lr>. Via: SIP/2.0/UDP 66.228.44.254;branch=z9hG4bKe198.142630c1.0. Via: SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>. Contact: <sip:123456@66.228.53.216:5060>. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 CANCEL. User-Agent: X-PRO build 1050. Content-Length: 0. . # U 2003/11/22 13:10:34.847761 66.228.44.254:5060 -> 66.228.53.216:5060 SIP/2.0 200 cancelling. Via: SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-6763. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 CANCEL. Server: Sip EXpress router (0.8.12 (i386/linux)). Content-Length: 0. Warning: 392 66.228.44.254:5060 "Noisy feedback tells: pid=10695 req_src_ip=66.228.53.216 req_src_port=5060 in_uri=sip:9723937976@named.com out_uri=sip:9723937976@65.77.154.243:5060 via_cnt==1". . # U 2003/11/22 13:10:34.847806 66.228.44.254:5060 -> 66.228.53.216:5060 SIP/2.0 487 Request cancelled. Via: SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-6763. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 INVITE. Server: Sip EXpress router (0.8.12 (i386/linux)). Content-Length: 0. Warning: 392 66.228.44.254:5060 "Noisy feedback tells: pid=10695 req_src_ip=66.228.53.216 req_src_port=5060 in_uri=sip:9723937976@named.com out_uri=sip:9723937976@66.228.53.218:5060 via_cnt==1". . # U 2003/11/22 13:10:34.875833 66.228.53.216:5060 -> 66.228.44.254:5060 ACK sip:9723937976@named.com SIP/2.0. Via: SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-6763. Contact: <sip:123456@66.228.53.216:5060>. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 ACK. Max-Forwards: 70. Content-Length: 0. . # U 2003/11/22 13:10:34.906960 66.228.53.218:50562 -> 66.228.44.254:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 66.228.44.254;branch=z9hG4bKe198.142630c1.0,SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>;tag=000b5faab82400151dddd662-025452b6. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 CANCEL. Server: CSCO/5. Content-Length: 0. . # U 2003/11/22 13:10:34.942865 66.228.53.218:50563 -> 66.228.44.254:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 66.228.44.254;branch=z9hG4bKe198.142630c1.0,SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>;tag=000b5faab82400151dddd662-025452b6. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 INVITE. Server: CSCO/5. Contact: <sip:9723937976@66.228.53.218:5060>. Record-Route: <sip:9723937976@66.228.44.254;ftag=320951244;lr>. Content-Length: 0. . # U 2003/11/22 13:10:34.943103 66.228.44.254:5060 -> 66.228.53.218:5060 ACK sip:9723937976@66.228.53.218:5060 SIP/2.0. Via: SIP/2.0/UDP 66.228.44.254;branch=z9hG4bKe198.142630c1.0. From: 123456 <sip:123456@named.com>;tag=320951244. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. To: <sip:9723937976@named.com>;tag=000b5faab82400151dddd662-025452b6. CSeq: 19721 ACK. User-Agent: Sip EXpress router(0.8.12 (i386/linux)). Content-Length: 0. . # U 2003/11/22 13:10:35.649964 66.228.44.254:5060 -> 66.228.53.216:5060 SIP/2.0 487 Request cancelled. Via: SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-6763. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 INVITE. Server: Sip EXpress router (0.8.12 (i386/linux)). Content-Length: 0. Warning: 392 66.228.44.254:5060 "Noisy feedback tells: pid=10695 req_src_ip=66.228.53.216 req_src_port=5060 in_uri=sip:9723937976@named.com out_uri=sip:9723937976@66.228.53.218:5060 via_cnt==1". . # U 2003/11/22 13:10:35.671936 66.228.53.216:5060 -> 66.228.44.254:5060 ACK sip:9723937976@named.com SIP/2.0. Via: SIP/2.0/UDP 66.228.53.216:5060. From: 123456 <sip:123456@named.com>;tag=320951244. To: <sip:9723937976@named.com>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-6763. Contact: <sip:123456@66.228.53.216:5060>. Call-ID: A7A5E0C3-865F-41A1-9CAD-EE1B104D7244(a)66.228.53.216. CSeq: 19721 ACK. Max-Forwards: 70. Content-Length: 0. . The 487CANCEL/ACK/CANCEL/ACK/CANCEL/ACK goes on and on until something eventually times out. Anybody have any ideas? The CANCEL works, but the excess chatter isn't wanted. Thanks, ---greg

2 2

Re: [Serusers] Warning: 392 137.252.37.5:5060 "Noisy feedback tells
by Jiri Kuthan 25 Nov '03

25 Nov '03

read the manual. http://www.iptel.org/ser/doc/seruser/seruser.html#AEN709 If you are uncomfortable with the option, it will tell you how to turn it off too. -jiri At 12:55 AM 11/25/2003, Vo, Tony wrote: >content-class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C3B2E6.66169657" > >Hi, >I'm getting this "Warning:" header from responses from methods received by SER; > >Warning: 392 137.252.37.5:5060 "Noisy feedback tells > >Anyone knows what this means? 392 is not in the RFC was a warning code. It's miscellaneous warning code. > > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Serusers] Warning: 392 137.252.37.5:5060 "Noisy feedback tells
by Vo, Tony 24 Nov '03

24 Nov '03

Hi, I'm getting this "Warning:" header from responses from methods received by SER; Warning: 392 137.252.37.5:5060 "Noisy feedback tells Anyone knows what this means? 392 is not in the RFC was a warning code. It's miscellaneous warning code.

1 0

[Serusers] test
by Jiri Kuthan 24 Nov '03

24 Nov '03

ignore -- Jiri Kuthan http://iptel.org/~jiri/

1 0

RE: [Serusers] Fw: Serweb problems - 0.8.12
by Jiri Kuthan 24 Nov '03

24 Nov '03

I may be wrong but my guess is that SER was not running. serweb tries to introduce an alias, which means that SER needs to be running and be configured to use aliases. -jiri At 09:44 PM 11/24/2003, Klaus Darilion wrote: >content-class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C3B2CB.C77D563C" > >Hi! > >Please CC to the list! > >Looks like serweb copies the new user from 'pending' to 'subscriber' table, but failes to delete the new user from the 'pending' table. > >I think these activities of serweb are unrelated to ser - serweb interacts directly with the DB. Maybe the table/colum names have changed slightly. > >Klaus >-----Original Message----- >From: Jon Ole Nome [mailto:jonome@avitrans.no] >Sent: Monday, November 24, 2003 9:39 PM >To: Klaus Darilion >Subject: Re: [Serusers] Fw: Serweb problems - 0.8.12 > >Thanks for the quick reply! Looking in the database I see that the new user is both in the pending and subscriber tables. Does that tell you anything? > >Jon Ole >----- Original Message ----- >From: <mailto:darilion@ict.tuwien.ac.at>Klaus Darilion >To: <mailto:jonome@avitrans.no>Jon Ole Nome ; <mailto:serusers@lists.iptel.org>serusers(a)lists.iptel.org >Sent: Monday, November 24, 2003 9:33 PM >Subject: RE: [Serusers] Fw: Serweb problems - 0.8.12 > >The aliases table is unrelated to this! > >Serweb adds the user to the "pending" table and when you confirm the registration by clicking the link, serweb moves the user from "pending" to "subscriber". > >Klaus >-----Original Message----- >From: Jon Ole Nome [mailto:jonome@avitrans.no] >Sent: Monday, November 24, 2003 9:29 PM >To: <mailto:serusers@lists.iptel.org>serusers(a)lists.iptel.org >Subject: [Serusers] Fw: Serweb problems - 0.8.12 > >I am running ser 0.8.12 with MySQL support on a RH9 server. Downloaded the latest serweb tarball from the cvs. I can log in with existing userids, both on the admin and user_interface web pages. If I try to register a new user in serweb the registration process runs ok and I get a mail asking for confirmation, but when I click the link to confirm I get this error: > >ringsip.com User Management >error in SQL query, line: 43 >We regret but your ringsip.com confirmation attempt failed. >Please contact <mailto:info@ringsip.com>info(a)ringsip.com for further assistance. >I have verified that the new user is added to the database, and I can log in to user_interface with the new userid. But there is nothing in the "aliases" table in the database. Any ideas? Grateful for any help! > >Jon Ole > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

2 2

RE: [Serusers] Fw: Serweb problems - 0.8.12
by Klaus Darilion 24 Nov '03

24 Nov '03

Hi! Please CC to the list! Looks like serweb copies the new user from 'pending' to 'subscriber' table, but failes to delete the new user from the 'pending' table. I think these activities of serweb are unrelated to ser - serweb interacts directly with the DB. Maybe the table/colum names have changed slightly. Klaus -----Original Message----- From: Jon Ole Nome [mailto:jonome@avitrans.no] Sent: Monday, November 24, 2003 9:39 PM To: Klaus Darilion Subject: Re: [Serusers] Fw: Serweb problems - 0.8.12 Thanks for the quick reply! Looking in the database I see that the new user is both in the pending and subscriber tables. Does that tell you anything? Jon Ole ----- Original Message ----- From: Klaus Darilion <mailto:darilion@ict.tuwien.ac.at> To: Jon Ole Nome <mailto:jonome@avitrans.no> ; serusers(a)lists.iptel.org Sent: Monday, November 24, 2003 9:33 PM Subject: RE: [Serusers] Fw: Serweb problems - 0.8.12 The aliases table is unrelated to this! Serweb adds the user to the "pending" table and when you confirm the registration by clicking the link, serweb moves the user from "pending" to "subscriber". Klaus -----Original Message----- From: Jon Ole Nome [mailto:jonome@avitrans.no] Sent: Monday, November 24, 2003 9:29 PM To: serusers(a)lists.iptel.org Subject: [Serusers] Fw: Serweb problems - 0.8.12 I am running ser 0.8.12 with MySQL support on a RH9 server. Downloaded the latest serweb tarball from the cvs. I can log in with existing userids, both on the admin and user_interface web pages. If I try to register a new user in serweb the registration process runs ok and I get a mail asking for confirmation, but when I click the link to confirm I get this error: ringsip.com User Management error in SQL query, line: 43 We regret but your ringsip.com confirmation attempt failed. Please contact info(a)ringsip.com for further assistance. I have verified that the new user is added to the database, and I can log in to user_interface with the new userid. But there is nothing in the "aliases" table in the database. Any ideas? Grateful for any help! Jon Ole

3 2

RE: [Serusers]VoiceMail
by Klaus Darilion 24 Nov '03

24 Nov '03

No, you don't need two instances of mysql, only two instances of ser. Make two config files for ser, for example: ser.cfg for the main proxy ser-vm.cfg for the voicemail proxy. (dont forget to change the listening port as 5060 is already used by the main proxy) start the main proxy as usual - manually or unsing the startup-script /etc/init.d/ser start the voicemail proxy using the second cfg file, e.g. ser -f /usr/local/etc/ser/ser-vm.cfg or copy the init.d/ser script to init.d/ser-vm and make the changes in the startup script. regards, Klaus > -----Original Message----- > From: Sesha B [mailto:sesha@iic.com] > Sent: Monday, November 24, 2003 10:49 PM > To: Klaus Darilion; serusers(a)lists.iptel.org > Subject: RE: [Serusers]VoiceMail > > > How do I run two instances of SER on the same machine? AS far as I > understood, I have to run two instances of mysql and two > instances of SER! > Please help. Thank you. > >

1 0

RE: [Serusers] Fw: Serweb problems - 0.8.12
by Klaus Darilion 24 Nov '03

24 Nov '03

So, aliases should be fine. Which MySQL version do you use? I had problems with the latest serweb using mysql 3.x because the introduced new SQL queries which requries mysql 4.x klaus -----Original Message----- From: Jon Ole Nome [mailto:jonome@avitrans.no] Sent: Monday, November 24, 2003 10:32 PM To: Klaus Darilion Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Fw: Serweb problems - 0.8.12 The lookup("aliases") is in the ser.cfg, in the routing section, just after save location. Is that the right place? Sorry for all the dumb questions. ----- Original Message ----- From: Klaus Darilion <mailto:darilion@ict.tuwien.ac.at> To: Jon Ole Nome <mailto:jonome@avitrans.no> Cc: serusers(a)lists.iptel.org Sent: Monday, November 24, 2003 10:25 PM Subject: RE: [Serusers] Fw: Serweb problems - 0.8.12 Yes, you're right. serweb adds an alias for every user - but you carn turn this off. maybe the problem accours when adding the alias. hint: there are often problems if the 'lookup("aliases")' statement is missing in the ser.cfg. klaus -----Original Message----- From: Jon Ole Nome [mailto:jonome@avitrans.no] Sent: Monday, November 24, 2003 9:56 PM To: Klaus Darilion Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Fw: Serweb problems - 0.8.12 Hello again, do you know where I can find line 43 in the SQL query? Maybe I can figure out what is wrong if I know what it's trying to do. Doesn't serweb add an alias for the user? That was the next thing I wanted to look into. I don't want users to select their own usernames, I want to assign a number when they register. Not sure how to set that up, though :) Jon Ole ----- Original Message ----- From: Klaus Darilion <mailto:darilion@ict.tuwien.ac.at> To: Jon Ole Nome <mailto:jonome@avitrans.no> Cc: serusers(a)lists.iptel.org Sent: Monday, November 24, 2003 9:44 PM Subject: RE: [Serusers] Fw: Serweb problems - 0.8.12 Hi! Please CC to the list! Looks like serweb copies the new user from 'pending' to 'subscriber' table, but failes to delete the new user from the 'pending' table. I think these activities of serweb are unrelated to ser - serweb interacts directly with the DB. Maybe the table/colum names have changed slightly. Klaus -----Original Message----- From: Jon Ole Nome [mailto:jonome@avitrans.no] Sent: Monday, November 24, 2003 9:39 PM To: Klaus Darilion Subject: Re: [Serusers] Fw: Serweb problems - 0.8.12 Thanks for the quick reply! Looking in the database I see that the new user is both in the pending and subscriber tables. Does that tell you anything? Jon Ole ----- Original Message ----- From: Klaus Darilion <mailto:darilion@ict.tuwien.ac.at> To: Jon Ole Nome <mailto:jonome@avitrans.no> ; serusers(a)lists.iptel.org Sent: Monday, November 24, 2003 9:33 PM Subject: RE: [Serusers] Fw: Serweb problems - 0.8.12 The aliases table is unrelated to this! Serweb adds the user to the "pending" table and when you confirm the registration by clicking the link, serweb moves the user from "pending" to "subscriber". Klaus -----Original Message----- From: Jon Ole Nome [mailto:jonome@avitrans.no] Sent: Monday, November 24, 2003 9:29 PM To: serusers(a)lists.iptel.org Subject: [Serusers] Fw: Serweb problems - 0.8.12 I am running ser 0.8.12 with MySQL support on a RH9 server. Downloaded the latest serweb tarball from the cvs. I can log in with existing userids, both on the admin and user_interface web pages. If I try to register a new user in serweb the registration process runs ok and I get a mail asking for confirmation, but when I click the link to confirm I get this error: ringsip.com User Management error in SQL query, line: 43 We regret but your ringsip.com confirmation attempt failed. Please contact info(a)ringsip.com for further assistance. I have verified that the new user is added to the database, and I can log in to user_interface with the new userid. But there is nothing in the "aliases" table in the database. Any ideas? Grateful for any help! Jon Ole

2 1

RE: [Serusers] Forwarding to more than one destination --
by Klaus Darilion 24 Nov '03

24 Nov '03

try "append_branch" http://www.iptel.org/ser/doc/seruser/seruser.html#AEN1597 klaus > -----Original Message----- > From: Kannaiyan Natesan [mailto:nkans@lycos.co.uk] > Sent: Friday, November 21, 2003 11:28 AM > To: serusers(a)lists.iptel.org > Subject: [Serusers] Forwarding to more than one destination -- > > > I want to forward it to more than one SIP address, I used the > following rule > but not working. > > if( uri=~"^sip:12345@mydomain.com") { > rewritehost("iptel.org"); > forward(iptel.org,5060); > rewritehost("fwd.pulver.com"); > forward(fwd.pulver.com,5060); > break; > } > > I want to ring in multiple destinations when a single call arrives, > whichever is first picked up, the other calls were cancelled. > > Am I missing anything here ? > > Kannaiyan > > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > >

2 1

RE: [Serusers] Fw: Serweb problems - 0.8.12
by Klaus Darilion 24 Nov '03

24 Nov '03

Yes, you're right. serweb adds an alias for every user - but you carn turn this off. maybe the problem accours when adding the alias. hint: there are often problems if the 'lookup("aliases")' statement is missing in the ser.cfg. klaus -----Original Message----- From: Jon Ole Nome [mailto:jonome@avitrans.no] Sent: Monday, November 24, 2003 9:56 PM To: Klaus Darilion Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Fw: Serweb problems - 0.8.12 Hello again, do you know where I can find line 43 in the SQL query? Maybe I can figure out what is wrong if I know what it's trying to do. Doesn't serweb add an alias for the user? That was the next thing I wanted to look into. I don't want users to select their own usernames, I want to assign a number when they register. Not sure how to set that up, though :) Jon Ole ----- Original Message ----- From: Klaus Darilion <mailto:darilion@ict.tuwien.ac.at> To: Jon Ole Nome <mailto:jonome@avitrans.no> Cc: serusers(a)lists.iptel.org Sent: Monday, November 24, 2003 9:44 PM Subject: RE: [Serusers] Fw: Serweb problems - 0.8.12 Hi! Please CC to the list! Looks like serweb copies the new user from 'pending' to 'subscriber' table, but failes to delete the new user from the 'pending' table. I think these activities of serweb are unrelated to ser - serweb interacts directly with the DB. Maybe the table/colum names have changed slightly. Klaus -----Original Message----- From: Jon Ole Nome [mailto:jonome@avitrans.no] Sent: Monday, November 24, 2003 9:39 PM To: Klaus Darilion Subject: Re: [Serusers] Fw: Serweb problems - 0.8.12 Thanks for the quick reply! Looking in the database I see that the new user is both in the pending and subscriber tables. Does that tell you anything? Jon Ole ----- Original Message ----- From: Klaus Darilion <mailto:darilion@ict.tuwien.ac.at> To: Jon Ole Nome <mailto:jonome@avitrans.no> ; serusers(a)lists.iptel.org Sent: Monday, November 24, 2003 9:33 PM Subject: RE: [Serusers] Fw: Serweb problems - 0.8.12 The aliases table is unrelated to this! Serweb adds the user to the "pending" table and when you confirm the registration by clicking the link, serweb moves the user from "pending" to "subscriber". Klaus -----Original Message----- From: Jon Ole Nome [mailto:jonome@avitrans.no] Sent: Monday, November 24, 2003 9:29 PM To: serusers(a)lists.iptel.org Subject: [Serusers] Fw: Serweb problems - 0.8.12 I am running ser 0.8.12 with MySQL support on a RH9 server. Downloaded the latest serweb tarball from the cvs. I can log in with existing userids, both on the admin and user_interface web pages. If I try to register a new user in serweb the registration process runs ok and I get a mail asking for confirmation, but when I click the link to confirm I get this error: ringsip.com User Management error in SQL query, line: 43 We regret but your ringsip.com confirmation attempt failed. Please contact info(a)ringsip.com for further assistance. I have verified that the new user is added to the database, and I can log in to user_interface with the new userid. But there is nothing in the "aliases" table in the database. Any ideas? Grateful for any help! Jon Ole

2 1

← Newer
1
...
6
7
8
9
10
11
12
...
27
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 November 2003