- sr-users - kamailio.org

by Yang Xiang

Hi, and in file digest.c of the module radius_auth: warning: digest.c: In function `radius_authorize': digest.c:79: `PW_SIP_NONCE' undeclared (first use in this function) digest.c:79: (Each undeclared identifier is reported only once digest.c:79: for each function it appears in.) digest.c:83: `PW_SIP_NONCE_COUNT' undeclared (first use in this function) Changed from PW_SIP_NONCE to PW_SIP_USER_NONCE and from PW_SIP_NONCE_COUNT to PW_SIP_USER_NONCE_COUNT which are defined in your new header file "radiusclient.h". Hope this is ok. Regards Yang

21 years, 4 months

2
1
0 0

[Serusers] Error in acc.c ?

by Yang Xiang

Hi, While trying to compile the module radius_acc I get some warnings as follows: acc.c: In function `radius_log_reply': acc.c:142: warning: passing arg 1 of `parse_from_header' from incompatible pointer type acc.c: In function `radius_log_ack': acc.c:426: warning: passing arg 1 of `parse_from_header' from incompatible pointer type acc.c: In function `rad_acc_request': acc.c:708: warning: passing arg 1 of `parse_from_header' from incompatible pointer type So I looked into the file acc.c and found such statements like if ( parse_from_header( msg )==-1 ) Because the function parse_from_header needs a parameter of type hdr_field, I changed the statements above to if ( parse_from_header( msg->headers )==-1 ) after this the warnings don't appear any longer. Is this change ok? Best Regards Yang

21 years, 4 months

2
1
0 0

Re: [Serusers] SIP/H.323 Gateway

by Giorgos Tsiouris

No it is not very stable and it produces a huge executable but it is the only open source that I am aware off. I also think that the development of sip2h323gw has stop since the programer that did the development has left long ago from Vovida. You can also complile this with the new h323 libraries available from www.h323.org or so I think. Giorgos Tsiouris ----- Original Message ----- From: "Vlasis Hatzistavrou" <vhatz(a)auth.gr> To: "Giorgos Tsiouris" <gtsiouris(a)telecom.ntua.gr> Sent: Wednesday, February 12, 2003 5:11 PM Subject: Re: [Serusers] SIP/H.323 Gateway > Hello Giorgo, > > Have you worked with the Vovida sip2h323gw? Is it stable or compatible with > other major vendor H323 GW's like Cisco for example? > > Best regards, > Vlasis. > > Giorgos Tsiouris wrote: > > > There is one SIP to H323 gateway from www.vovida.org . You can download > > vocal and you can compile only the gateway. I also think that there is one > > from siemens (I do not remeber their site) but this is not open source. > > > > Giorgos Tsiouris > > > > ----- Original Message ----- > > From: "Ng, Soo Sim" <SooSim.Ng(a)hp.com> > > To: <serusers(a)lists.iptel.org> > > Sent: Wednesday, February 12, 2003 1:09 PM > > Subject: [Serusers] SIP/H.323 Gateway > > > > > Is there testing being done SIP end-point to H.323 end-point call and > > vice-versa. What's the SIP/H.323 gateway being tested? > > > > > > Thanks > > > > > > SS > > > _______________________________________________ > > > 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 >

21 years, 4 months

1
0
0 0

[Serusers] SIP/H.323 Gateway

by Ng, Soo Sim

Is there testing being done SIP end-point to H.323 end-point call and vice-versa. What's the SIP/H.323 gateway being tested? Thanks SS

21 years, 4 months

2
1
0 0

[Serusers] Problem compiling module radius_auth

by Bjoern Zuelch

Hi, we try to compile ser 0.8.10 with radius support under Solaris 8. First we have a problem with the radius_acc module. We found s solution in the mailinglist archive. Now we have a problem with the radius_auth module. If we compile it we get the following error message: digest.c -o digest.o digest.c: In function `radius_authorize': digest.c:79: `PW_SIP_NONCE' undeclared (first use in this function) digest.c:79: (Each undeclared identifier is reported only once digest.c:79: for each function it appears in.) digest.c:83: `PW_SIP_NONCE_COUNT' undeclared (first use in this function) digest.c: In function `radius_authorize_freeradius': digest.c:160: `PW_DIGEST_USER_NAME' undeclared (first use in this function) digest.c:164: `PW_DIGEST_REALM' undeclared (first use in this function) digest.c:168: `PW_DIGEST_NONCE' undeclared (first use in this function) digest.c:172: `PW_DIGEST_URI' undeclared (first use in this function) digest.c:176: `PW_DIGEST_METHOD' undeclared (first use in this function) digest.c:184: `PW_DIGEST_QOP' undeclared (first use in this function) digest.c:192: `PW_DIGEST_CNONCE' undeclared (first use in this function) digest.c:201: `PW_DIGEST_NONCE_COUNT' undeclared (first use in this function) digest.c:211: `PW_DIGEST_BODY_DIGEST' undeclared (first use in this function) digest.c:241: `PW_DIGEST_ALGORITHM' undeclared (first use in this function) digest.c:252: `PW_DIGEST_ATTRIBUTES' undeclared (first use in this function) digest.c:258: `PW_DIGEST_RESPONSE' undeclared (first use in this function) gmake: *** [digest.o] Error 1 we think that there some definitions not defined in an header-file. we included the dict.h file from the radius_acc module(CVS version), so most of the definitions PW_SIP_* are present. Is there a possibility to get the missing definitions? greetings bjoern

21 years, 4 months

2
1
0 0

Re: [Serusers] New Setup of SER

by chid＠eglobalcall.com

Hi, Can I just cut and paste the script directly into the ser.cfg file? -Chi Original Message: ----------------- From: serusers (Jiri) serusers(a)lists.iptel.org Date: Tue, 11 Feb 2003 17:30:52 +0100 To: chid(a)eglobalcall.com, serusers(a)lists.iptel.org Subject: Re: [Serusers] New Setup of SER At 01:22 PM 2/11/2003, Chi Dang wrote: >Hi, > >Sorry to be greedy but I have two questions. I've just finished >installed the ser 0.8 version on Solaris 2.8. > >1. When I ran ser, it said it is listening to only 3 servers. I have >added 2 more into my /etc/hosts file but make no difference. Where does >ser daemon get the ip of servers that it is listening to? /etc/hosts configures you resolver and does not affect the interfaces configured on your host. ser determines existing interfaces but does not care about your resolver's configuration. >2. I plan to use ser with my cisco voip gateways. Is there anything >special that I need to configure ser to make it work with Cisco >gateways? Maybe access control http://www.iptel.org/ser/doc/seruser-html/x740.html#AEN786 Note that Cisco gateways have no digest support, so you are left only with source IP address "authentication". -Jiri _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

21 years, 4 months

3
2
0 0

[Serusers] New Setup of SER

by Chi Dang

Hi, Sorry to be greedy but I have two questions. I've just finished installed the ser 0.8 version on Solaris 2.8. 1. When I ran ser, it said it is listening to only 3 servers. I have added 2 more into my /etc/hosts file but make no difference. Where does ser daemon get the ip of servers that it is listening to? 2. I plan to use ser with my cisco voip gateways. Is there anything special that I need to configure ser to make it work with Cisco gateways? Thanks, Chi Dang

21 years, 4 months

2
1
0 0

[Serusers] 3PCC-Szenario

by Karsten Knuettel

Hi, I am working on a 3rd Party Call Control implementation. Is it possible to get notifyed as a 3rd Party (SER owner) when Sip Party A connects SIP Party B? Thank you! karsten

21 years, 4 months

4
3
0 0

RE: [Serusers] user permission problem on ser-jabber gw

by Toni Barata (EPS)

Hi Daniel, Ok, I found a configuration error on ser.cfg. On the Jaddress parameter the Ip address had a sintax error (one of the dots was replaceded by a comma). But now there is another problem: - When the sip client (messenger) sends a IM to the Jabber client, the jabber client do not receive the message but he is "notified" that the sip-client is on-line. - When the jabber client send an IM to the sip client the messages is received by the sip client. Any idea of what is going on? Best regards, Toni -----Original Message----- From: Daniel-Constantin MIERLA [mailto:mierla@fokus.fraunhofer.de] Sent: sexta-feira, 31 de Janeiro de 2003 18:30 To: Toni Barata (EPS) Subject: Re: [Serusers] user permission problem on ser-jabber gw You have to set debug=9 and log_stderror=yes in ser's config file. Debug messages will be displayed on console and you can copy/paste in a file. If you got that error message, means that ser-jabber gw was connected to Jabber server, but something was happening and the connection was broken. So some messages should have been exchanged between ser and Jabber. Did you check all your network interfaces (I told you in last mail you have to sniff loopback interface if Jabber server and ser is on the same machine)? Regards, Daniel Toni Barata (EPS) wrote: Hi, I forgot to tell you that I put the ethereal sniffing the network and no packet was sent by the ser-jabber gw to the port 5222 on the jabber server. I seems that this is an internal problem on the ser-jabber. Is there a way to send the logs to a file? Best regards, Toni

21 years, 4 months

2
1
0 0

[Serusers] Simple methods

by Anuradha Kalyan

hello, we are using ser 0.8.10. it worked fine with SIP methods. we would like to know whether we can use the ser to test the simple methods (simple, subscribe and notify methods) with thanks and regards, Anuradha -- ************************************************************** eRiva provides IT Solutions & Services to companies worldwide. Our State of the Art Research & Development Center provides Innovative Solutions to global customers. eRiva's unique value proposition is further delivered through our Offshore Outsourcing Model and stringent Quality Processes of SEI / ISO and Six Sigma. [www.erivasystems.com] ************************************************************** --

21 years, 4 months

2
1
0 0

[Serusers] Bug in new_hash2() function [patch]

by Maxim Sobolev

Folks, There is a bug in ser, which results in different hashes to be generated if some of the fields participating in hash generation has extra spaces before value in reply that were not present in request, i.e.: request: From: <vasia_pupkin(a)1.2.3.4> reply: From: <vasia_pupkin(a)1.2.3.4> This leads to matching failure and as a result causes useless retransmition, if tm module is used. For example, Vovida's SIP stack is found to be guilty in inserting extra spaces into reply's headers (which isn't really prohibited by the RFC). Attached little patch should fix the problem. It would be nice to have it integrated into the next release. Thanks! -Maxim

21 years, 4 months

3
3
0 0

[Serusers] SER and SIP-CGI

by Stephan Reiff-Marganiec

Hi, I was wondering whether there is a ser module for SIP-CGI. Or whether there are attempts at creating one? If so, could anyone point me in the right direction? thanks, Stephan -- Dr Stephan Reiff-Marganiec Research Fellow Department of Computing Science; University of Stirling email: srm(a)cs.stir.ac.uk tel: 01786 46 7448 -- The University of Stirling is a university established in Scotland by charter at Stirling, FK9 4LA. Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not disclose, copy or deliver this message to anyone and any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of the University of Stirling shall be understood as neither given nor endorsed by it.

21 years, 4 months

2
1
0 0

[Serusers] core when running the rad_acc module

by Claudio Thorell dos Santos

Hello, I'm trying to setup the radius accounting module but SER craches wherever I make a call. The call does complete, but the core is generated a couple seconds later. Without rad_acc moudule SER works fine, so I assume this have something to do with the module. I'm attaching some resumed debugs for the crash. I also have the complete debug (log level 10), wich is quite big so I decided not so send it to the list unless the following debugs are not enough. Any ideas on what's the problem? Thanks and regards, Claudio Thorell ########### ... 6(24956) qm_free(0x80adf80, 0x80b5174), called from parser/msg_parser.c: free_sip_msg(487) 6(24956) qm_free: freeing block alloc'ed from action.c: do_action(346) 6(24956) qm_free(0x80adf80, 0x80b5090), called from parser/parse_via.c: free_via_param_list(1816) 6(24956) qm_free: freeing block alloc'ed from parser/parse_via.c: parse_via(1642) 6(24956) qm_free(0x80adf80, 0x80b52ec), called from parser/parse_via.c: free_via_list(1828) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: get_hdr_field(85) 6(24956) qm_free(0x80adf80, 0x80b5128), called from parser/hf.c: free_hdr_field_lst(103) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: parse_headers(229) 6(24956) qm_free(0x80adf80, 0x80b4ff0), called from parser/hf.c: free_hdr_field_lst(103) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: parse_headers(229) 6(24956) qm_free(0x80adf80, 0x80b4fa4), called from parser/hf.c: free_hdr_field_lst(103) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: parse_headers(229) 6(24956) qm_free(0x80adf80, 0x80b46cc), called from parser/parse_to.c: free_to(741) 6(24956) qm_free: freeing block alloc'ed from parser/parse_to.c: parse_to_param(265) 6(24956) qm_free(0x80adf80, 0x80b482c), called from parser/parse_to.c: free_to(744) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: get_hdr_field(123) 6(24956) qm_free(0x80adf80, 0x80b479c), called from parser/hf.c: free_hdr_field_lst(103) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: parse_headers(229) 6(24956) qm_free(0x80adf80, 0x80b51dc), called from parser/hf.c: free_hdr_field_lst(103) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: parse_headers(229) 6(24956) qm_free(0x80adf80, 0x80b47e8), called from parser/parse_cseq.c: free_cseq(94) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: get_hdr_field(104) 6(24956) qm_free(0x80adf80, 0x80b5228), called from parser/hf.c: free_hdr_field_lst(103) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: parse_headers(229) 6(24956) qm_free(0x80adf80, 0x80b4f58), called from parser/hf.c: free_hdr_field_lst(103) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: parse_headers(229) 6(24956) qm_free(0x80adf80, 0x80b50dc), called from parser/hf.c: free_hdr_field_lst(103) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: parse_headers(229) 6(24956) qm_free(0x80adf80, 0x80b4c70), called from parser/hf.c: free_hdr_field_lst(103) 6(24956) qm_free: freeing block alloc'ed from parser/msg_parser.c: parse_headers(229) 6(24956) qm_free(0x80adf80, 0x80b4d08), called from data_lump.c: free_lump_list(248) 6(24956) qm_free: freeing block alloc'ed from data_lump.c: del_lump(153) 6(24956) qm_free(0x80adf80, 0x80b475c), called from data_lump.c: free_lump(212) 6(24956) qm_free: freeing block alloc'ed from textops.c: append_hf(231) 6(24956) qm_free(0x80adf80, 0x80b4418), called from data_lump.c: free_lump_list(237) 6(24956) qm_free: freeing block alloc'ed from data_lump.c: insert_new_lump_before(129) 6(24956) qm_free(0x80adf80, 0x80b4cbc), called from data_lump.c: free_lump_list(248) 6(24956) qm_free: freeing block alloc'ed from data_lump.c: anchor_lump(183) 6(24956) qm_free(0x80adf80, 0x80b54bc), called from parser/msg_parser.c: free_sip_msg(493) 6(24956) qm_free: freeing block alloc'ed from receive.c: receive_msg(83) 6(24956) qm_free(0x80adf80, 0x80b4adc), called from receive.c: receive_msg(177) 6(24956) qm_free: freeing block alloc'ed from receive.c: receive_msg(63) 6(24956) qm_malloc(0x80adf80, 356) called from receive.c: receive_msg(63) 6(24956) qm_malloc(0x80adf80, 356) returns address 0x80b4adc on 0 -th hit 6(24956) qm_malloc(0x80adf80, 415) called from receive.c: receive_msg(83) 6(24956) qm_malloc(0x80adf80, 416) returns address 0x80b54bc on 0 -th hit 6(24956) SIP Request: 6(24956) method: <ACK> 6(24956) uri: <sip:1005@200.219.173.141;branch=0> 6(24956) version: <SIP/2.0> 6(24956) parse_headers: flags=1 6(24956) qm_malloc(0x80adf80, 28) called from parser/msg_parser.c: parse_headers(229) 6(24956) qm_malloc(0x80adf80, 28) returns address 0x80b4cbc on 0 -th hit 6(24956) qm_malloc(0x80adf80, 104) called from parser/msg_parser.c: get_hdr_field(85) 6(24956) qm_malloc(0x80adf80, 104) returns address 0x80b52ec on 0 -th hit 0(24946) child process 24961 exited by a signal 11 0(24946) core was generated 0(24946) INFO: terminating due to SIGCHLD 4(24954) Memory status (pkg): 4(24954) qm_status (0x80adf80): 4(24954) heap size= 1022872 4(24954) used= 1040, used+overhead=27272, free=995600 4(24954) max used (+overhead)= 27340 4(24954) dumping all allocked. fragments: ...

21 years, 4 months

1
0
0 0

Re: [Serusers] How to configure Serweb

by Jiri Kuthan

Dan Austin's howto (see SER webpage) is probably the currently most extensive documentation available. -Jiri At 05:16 PM 2/6/2003, Jerry Yin wrote: >Hi All, > >Can somebody tell me how to configure the serweb? Which directory should I >put those files and which file and parameters should I modify. Or maybe this >question was asked previously by somebody already, then please provide me a >like to those answers. > >Thanks, > >Jerry Yin >Mitel Networks. >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

21 years, 4 months

1
0
0 0

[Serusers] How to configure Serweb

by Jerry Yin

Hi All, Can somebody tell me how to configure the serweb? Which directory should I put those files and which file and parameters should I modify. Or maybe this question was asked previously by somebody already, then please provide me a like to those answers. Thanks, Jerry Yin Mitel Networks.

21 years, 4 months

1
0
0 0

RE: [Serusers] ser crashes

by Klaus Darilion

Hi! I'm really very sorry that I have wasted your time - I've made a really stupid mistake. Now I fixed the proper line (103) and everything works fine. No messages in the log file, no crashes. Thanks a lot! Klaus > -----Original Message----- > From: Jan Janak [mailto:J.Janak@sh.cvut.cz] > Sent: Thursday, February 06, 2003 4:45 PM > To: Klaus Darilion > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] ser crashes > > > On 06-02 16:25, Klaus Darilion wrote: > > My experience is the following: > > > > Line 109 in t_msgbuilder.c: > > > > len += USER_AGENT_LEN + CRLF_LEN; > > ==> ser crashes when I send the special invite! > > > > *len += USER_AGENT_LEN + CRLF_LEN; > > ==> ser doesn't crash but logs this in /val/log/messages: > > Feb 6 15:48:24 obelix /usr/local/sbin/ser[6985]: ERROR: > > t_build_and_send_CANCEL: cannot allocate memory > > > > > > hope my explanation is a little bit clearer now: > > i also downloaded > > ftp://ftp.berlios.de/pub/ser/0.8.10/src/ser-0.8.10_src.tar.gz > > and this tarball contains: *len += USER_AGENT_LEN + CRLF_LEN; > > > > That's another line, look at line 103: > > len+=((hdr->body.s+hdr->body.len ) - hdr->name.s ) + > CRLF_LEN; > > This should be changed to: > > *len+=((hdr->body.s+hdr->body.len ) - hdr->name.s ) + > CRLF_LEN; > > regards, Jan. > >

21 years, 4 months

1
0
0 0

RE: [Serusers] ser crashes

by Klaus Darilion

My experience is the following: Line 109 in t_msgbuilder.c: len += USER_AGENT_LEN + CRLF_LEN; ==> ser crashes when I send the special invite! *len += USER_AGENT_LEN + CRLF_LEN; ==> ser doesn't crash but logs this in /val/log/messages: Feb 6 15:48:24 obelix /usr/local/sbin/ser[6985]: ERROR: t_build_and_send_CANCEL: cannot allocate memory hope my explanation is a little bit clearer now: i also downloaded ftp://ftp.berlios.de/pub/ser/0.8.10/src/ser-0.8.10_src.tar.gz and this tarball contains: *len += USER_AGENT_LEN + CRLF_LEN; regards, klaus > -----Original Message----- > From: Jan Janak [mailto:J.Janak@sh.cvut.cz] > Sent: Thursday, February 06, 2003 4:19 PM > To: Klaus Darilion > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] ser crashes > > > Hello, > > On 06-02 16:02, Klaus Darilion wrote: > > Thank you, the path to the modules was the problem! > > > > Now ser runs also as self compiled version and doesnt > crash. I didn't > > had to change the source because the source code available > to download > > is already corrected. To proof your guess I inserted the > error again ( > > len+=) and than it crashes again. > > ser-0.8.10_src.tar.gz has this bug too. > > > Conclusion: with the source code version from 0.8.10 ser > doesn't crash > > anymore. Nevertheless, /var/log/messages shows an error > message when I > > send my special invite: > > > > Feb 6 15:48:24 obelix /usr/local/sbin/ser[6985]: ERROR: > > t_build_and_send_CANCEL: cannot allocate memory > > That's the bug I told you about, AFAIK it is caused by the missing > dereference operator in t_msgbuilder.c. See my previous email for > description how to fix it. (rewrite len+= to *len+=, recompile and > reinstall). > > regards, Jan. > >

21 years, 4 months

2
1
0 0

RE: [Serusers] ser crashes

by Klaus Darilion

Thank you, the path to the modules was the problem! Now ser runs also as self compiled version and doesnt crash. I didn't had to change the source because the source code available to download is already corrected. To proof your guess I inserted the error again ( len+=) and than it crashes again. Conclusion: with the source code version from 0.8.10 ser doesn't crash anymore. Nevertheless, /var/log/messages shows an error message when I send my special invite: Feb 6 15:48:24 obelix /usr/local/sbin/ser[6985]: ERROR: t_build_and_send_CANCEL: cannot allocate memory thanks and regards, Klaus > -----Original Message----- > From: Jan Janak [mailto:J.Janak@sh.cvut.cz] > Sent: Thursday, February 06, 2003 3:36 PM > To: Klaus Darilion > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] ser crashes > > > Double check path of the modules. Probably you are using > config file from the rpm package, after make install the > modules will be in /usr/local/lib/ser/modules. The rpm > package installs them in /usr/lib/ser/modules so you will > have to change it. > > There is no uninstall in the makefiles, you can uninstall > only by hand right now. > > regards, Jan. > > On 06-02 15:19, Klaus Darilion wrote: > > Hello! > > > > I have problems running the self compiled ser version (without any > > sourcecode changes). > > > > I uninstalled the rpms ("rpm -e ser-mysql" and "rpm -e ser" - I use > > the mysql authentication). Then I compiled ser with "make > all" without > > errors. I installed ser with "make install". Then I tried > to start ser > > with: > > # /usr/local/sbin/ser -f /etc/ser/ser.cfg > > ERROR: bad config file (25 errors) > > > > Why does my config file doesn't work anymore (it worked > with the rpm > > version)? When I start ser with -f, than it starts (but than it > > doesn't use the mysql database). > > > > Have I done something wrong during the installation/compiling? > > > > How can I delete the files that were installed by "make > install"? make > > uninstall? > > > > regards, > > klaus > > > > > -----Original Message----- > > > From: Jan Janak [mailto:J.Janak@sh.cvut.cz] > > > Sent: Thursday, February 06, 2003 12:12 AM > > > To: Klaus Darilion > > > Cc: serusers(a)lists.iptel.org > > > Subject: Re: [Serusers] ser crashes > > > > > > > > > Hello, > > > > > > I wasn't able to reproduce it, but I think I know where the > > > problem is. There is a bug in 0.8.10 which shows up when an > > > INVITE contains Route header field. The bug has been fixed > > > in the CVS already. > > > > > > If you can compile ser from sources, you can easily fix > it in your > > > release: > > > > > > 1) Edit ser-0.8.10/modules/tm/t_msgbuilder.c > > > 2) Jump to line 103 > > > 3) replace len+= with *len+= > > > 4) Recompile ser > > > > > > I can send you a patch if it is more convinient for you. > > > > > > regards, Jan. > > > > > > On 05-02 12:13, Klaus Darilion wrote: > > > > Hello! > > > > > > > > During playing around with route headers I discovered that > > > ser crashes > > > > reproduceable when I send the following request to it with > > > sipsak, I > > > > think the invite is a valid request with strict routing. > > > > > > > > sipsak.exe -f invite3.txt -s sip:obelix.ict.tuwien.ac.at -vvv > > > > > > > > invite3.txt: > > > > INVITE sip:obelix.ict.tuwien.ac.at SIP/2.0 > > > > Via: SIP/2.0/UDP 128.131.80.191:5070;branch=z9hG4bK2024693217 > > > > Route: <sip:iptel.org> > > > > Route: <sip:klaus3000@klausix.ict.tuwien.ac.at> > > > > From: <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618 > > > > To: <sip:klaus3000@iptel.org> > > > > Call-ID: 744056460(a)128.131.80.191 > > > > CSeq: 20 INVITE > > > > Contact: <sip:brutus@128.131.80.191:5070> > > > > max-forwards: 10 > > > > user-agent: oSIP/Linphone-0.9.1 > > > > Content-Type: application/sdp > > > > Content-Length: 335 > > > > > > > > .. > > > > sdp > > > > .. > > > > > > > > > > > > then ser stops to respond: > > > > > > > > >[root@obelix darilion]# /etc/init.d/ser status > > > > >ser dead but subsys locked > > > > > > > > and in /var/log/messages > > > > Feb 5 11:57:21 obelix ser: Listening on > > > > Feb 5 11:57:21 obelix ser: 128.131.80.136 > > > > [128.131.80.136]::5060 > > > > Feb 5 11:57:21 obelix ser: Aliases: > obelix.ict.tuwien.ac.at:5060 > > > > Feb 5 11:57:21 obelix ser: ser startup succeeded Feb > 5 11:57:21 > > > > obelix /usr/sbin/ser[21426]: mod_init(): Database connection > > > > opened successfuly Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: > > > > INFO: > > > udp_init: SO_RCVBUF > > > > is initially 65535 > > > > Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: INFO: > > > udp_init: SO_RCVBUF > > > > is finally 131070 > > > > Feb 5 11:57:21 obelix /usr/sbin/ser[21432]: INFO: fifo process > > > > starting: 21432 > > > > Feb 5 11:57:21 obelix /usr/sbin/ser[21432]: SER: > > > open_uac_fifo: fifo > > > > server up at /tmp/ser_fifo... > > > > > > > > ..up to here everything works fine, than I send the request: > > > > > > > > Feb 5 11:57:30 obelix /usr/sbin/ser[21428]: BUG: qm_*: fragm. > > > > 0x422b9ad0 end overwritten(35322e64, 39306665)! Feb 5 > > > 11:57:30 obelix > > > > /usr/sbin/ser[21426]: child process 21428 exited by a signal 11 > > > > Feb 5 11:57:30 obelix /usr/sbin/ser[21426]: core was not > > > > generated Feb 5 11:57:30 obelix /usr/sbin/ser[21426]: INFO: > > > terminating due to > > > > SIGCHLD > > > > > > > > Here is the ngrep output: > > > > > > > > U 128.131.80.101:1558 -> 128.131.80.136:5060 > > > > INVITE sip:obelix.ict.tuwien.ac.at SIP/2.0..Via: SIP/2.0/UDP > > > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP > > > > 128.131.80.191:5070;branch=z9hG4bK2024693217..Route: <sip:iptel. > > > > org>..Route: <sip:klaus3000@klausix.ict.tuwien.ac.at>..From: > > > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > > > <sip:klaus3000@iptel.org>..Call-ID: 744056460(a)128.131.80 > > > > .191..CSeq: 20 INVITE..Contact: > > > > <sip:brutus@128.131.80.191:5070>..max-forwards: 10..user-agent: > > > > oSIP/Linphone-0.9.1..Content-Type: > > > > application/sdp..Content-Length: > > > > 335 .... > > > > v=0..o=brutus 123456 654321 IN IP4 128.131.80.191..s=A > > > > c..onversation..c=IN IP4 128.131.80.191..t=0 0..m=audio > > > 7078 RTP/AVP 3 > > > > 115 8 110 111 101..a=rtpmap:3 gsm/8000/1..a=rtp > > > > map:115 lpc10-1.5/8000/1..a=rtpmap:8 PCMA/8000/1..a=rtpmap:110 > > > > speex-4/8000/1..a=rtpmap:111 speex_lbr-4/8000/1..a=rtpmap:101 > > > > telephone-event/8000..a=fmtp:101 0-11.. > > > > # > > > > U 128.131.80.136:5060 -> 128.131.80.101:1557 > > > > SIP/2.0 100 trying -- your call is important to us..Via: > > > SIP/2.0/UDP > > > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP > > > > 128.131.80.191:5070;branch=z9hG4bK2024693217..From: <sip > > > > :brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > > > <sip:klaus3000@iptel.org>..Call-ID: > > > 744056460@128.131.80.191..CSeq: 20 > > > > INVITE..Server: Sip EXpress router (0.8.10 (i386/l > > > > inux))..Content-Length: 0..Warning: 392 > > > 128.131.80.136:5060 "Noisy > > > > feedback tells: pid=21552 req_src_ip=128.131.80.101 > > > > in_uri=sip:obelix.ict.tuwien.ac.at out_uri=sip:iptel.o > > > > rg via_cnt==2".... > > > > > > > > # > > > > U 128.131.80.136:5060 -> 195.37.77.101:5060 > > > > INVITE sip:iptel.org SIP/2.0..Via: SIP/2.0/UDP > > > > 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..Via: SIP/2.0/UDP > > > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 128.131.80.191: > > > > 5070;branch=z9hG4bK2024693217..Route: > > > > <sip:klaus3000@klausix.ict.tuwien.ac.at>..From: > > > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > > > <sip:klaus3000@iptel.org>..Call > > > > -ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Contact: > > > > <sip:brutus@128.131.80.191:5070>..max-forwards: 9 ..user-agent: > > > > oSIP/Linphone-0.9.1..Content-Type: application/sdp.. > > > > Content-Length: 335 ....v=0..o=brutus 123456 654321 IN IP4 > > > > 128.131.80.191..s=A c..onversation..c=IN IP4 > 128.131.80.191..t=0 > > > > 0..m=audio 7078 RTP/AVP 3 115 8 110 111 101..a=r > > > > tpmap:3 gsm/8000/1..a=rtpmap:115 lpc10-1.5/8000/1..a=rtpmap:8 > > > > PCMA/8000/1..a=rtpmap:110 speex-4/8000/1..a=rtpmap:111 > > > > speex_lbr-4/8000/1..a=rtpmap:101 telephone-event/8000..a > > > > =fmtp:101 0-11.. > > > > > > > > # > > > > U 195.37.77.101:5060 -> 128.131.80.136:5060 > > > > SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP > > > > 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..Via: SIP/2.0/UDP > > > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 12 > > > > 8.131.80.191:5070;branch=z9hG4bK2024693217..From: > > > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > > > > <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07.3f3c > > > > ..Call-ID: 744056460@128.131.80.191..CSeq: 20 > > > > INVITE..Proxy-Authenticate: Digest realm="iptel.org", > > > > nonce="3e40f29900000000d6e1790446755f1b4b96f5f5bd97b283", > > > > algorithm=MD5.. > > > > Server: Sip EXpress router (0.8.9 > (i386/linux))..Content-Length: > > > > 0..Warning: 392 195.37.77.101:5060 "Noisy feedback > tells: pid=7651 > > > > req_src_ip=128.131.80.136 in_uri=sip:ipte > > > > l.org out_uri=sip:klaus3000@klausix.ict.tuwien.ac.at > > > via_cnt==3".... > > > > > > > > # > > > > U 128.131.80.136:5060 -> 128.131.80.101:1557 > > > > SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP > > > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP > > > > 128.131.80.191:5070;branch=z9hG4bK2024693217..From: > <sip:brutus@o > > > > belix.ict.tuwien.ac.at>;tag=262992618..To: > > > > > > > > <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07.3f3c. > > > .C > > > > al > > > > l-ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Proxy-Aut > > > > henticate: Digest realm="iptel.org", > > > > nonce="3e40f29900000000d6e1790446755f1b4b96f5f5bd97b283", > > > > algorithm=MD5..Server: Sip EXpress router (0.8.9 > > > > (i386/linux))..Content-Length > > > > : 0..Warning: 392 195.37.77.101:5060 "Noisy feedback > > > tells: pid=7651 > > > > req_src_ip=128.131.80.136 in_uri=sip:iptel.org > > > > out_uri=sip:klaus3000@klausix.ict.tuwien.ac.at via_cnt==3 > > > > ".... > > > > > > > > # > > > > U 128.131.80.136:5060 -> 195.37.77.101:5060 > > > > ACK sip:iptel.org SIP/2.0..Via: SIP/2.0/UDP > > > > 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..From: > > > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..Call-ID: > > > > 744056460(a)128.13 > > > > 1.80.191..To: > > > > > > > <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07 > > > .3f3c..CSe > > > > q: 20 ACK.. > > > > > > > > > > > > > > > > If you need more details please let me know. > > > > > > > > regards, > > > > Klaus > > > > _______________________________________________ > > > > Serusers mailing list > > > > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > > > >

21 years, 4 months

2
1
0 0

RE: [Serusers] ser crashes

by Klaus Darilion

Hello! I have problems running the self compiled ser version (without any sourcecode changes). I uninstalled the rpms ("rpm -e ser-mysql" and "rpm -e ser" - I use the mysql authentication). Then I compiled ser with "make all" without errors. I installed ser with "make install". Then I tried to start ser with: # /usr/local/sbin/ser -f /etc/ser/ser.cfg ERROR: bad config file (25 errors) Why does my config file doesn't work anymore (it worked with the rpm version)? When I start ser with -f, than it starts (but than it doesn't use the mysql database). Have I done something wrong during the installation/compiling? How can I delete the files that were installed by "make install"? make uninstall? regards, klaus > -----Original Message----- > From: Jan Janak [mailto:J.Janak@sh.cvut.cz] > Sent: Thursday, February 06, 2003 12:12 AM > To: Klaus Darilion > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] ser crashes > > > Hello, > > I wasn't able to reproduce it, but I think I know where the > problem is. There is a bug in 0.8.10 which shows up when an > INVITE contains Route header field. The bug has been fixed > in the CVS already. > > If you can compile ser from sources, you can easily fix it in your > release: > > 1) Edit ser-0.8.10/modules/tm/t_msgbuilder.c > 2) Jump to line 103 > 3) replace len+= with *len+= > 4) Recompile ser > > I can send you a patch if it is more convinient for you. > > regards, Jan. > > On 05-02 12:13, Klaus Darilion wrote: > > Hello! > > > > During playing around with route headers I discovered that > ser crashes > > reproduceable when I send the following request to it with > sipsak, I > > think the invite is a valid request with strict routing. > > > > sipsak.exe -f invite3.txt -s sip:obelix.ict.tuwien.ac.at -vvv > > > > invite3.txt: > > INVITE sip:obelix.ict.tuwien.ac.at SIP/2.0 > > Via: SIP/2.0/UDP 128.131.80.191:5070;branch=z9hG4bK2024693217 > > Route: <sip:iptel.org> > > Route: <sip:klaus3000@klausix.ict.tuwien.ac.at> > > From: <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618 > > To: <sip:klaus3000@iptel.org> > > Call-ID: 744056460(a)128.131.80.191 > > CSeq: 20 INVITE > > Contact: <sip:brutus@128.131.80.191:5070> > > max-forwards: 10 > > user-agent: oSIP/Linphone-0.9.1 > > Content-Type: application/sdp > > Content-Length: 335 > > > > .. > > sdp > > .. > > > > > > then ser stops to respond: > > > > >[root@obelix darilion]# /etc/init.d/ser status > > >ser dead but subsys locked > > > > and in /var/log/messages > > Feb 5 11:57:21 obelix ser: Listening on > > Feb 5 11:57:21 obelix ser: 128.131.80.136 > > [128.131.80.136]::5060 > > Feb 5 11:57:21 obelix ser: Aliases: obelix.ict.tuwien.ac.at:5060 > > Feb 5 11:57:21 obelix ser: ser startup succeeded > > Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: mod_init(): Database > > connection opened successfuly > > Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: INFO: > udp_init: SO_RCVBUF > > is initially 65535 > > Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: INFO: > udp_init: SO_RCVBUF > > is finally 131070 > > Feb 5 11:57:21 obelix /usr/sbin/ser[21432]: INFO: fifo process > > starting: 21432 > > Feb 5 11:57:21 obelix /usr/sbin/ser[21432]: SER: > open_uac_fifo: fifo > > server up at /tmp/ser_fifo... > > > > ..up to here everything works fine, than I send the request: > > > > Feb 5 11:57:30 obelix /usr/sbin/ser[21428]: BUG: qm_*: fragm. > > 0x422b9ad0 end overwritten(35322e64, 39306665)! Feb 5 > 11:57:30 obelix > > /usr/sbin/ser[21426]: child process 21428 exited by a signal 11 > > Feb 5 11:57:30 obelix /usr/sbin/ser[21426]: core was not generated > > Feb 5 11:57:30 obelix /usr/sbin/ser[21426]: INFO: > terminating due to > > SIGCHLD > > > > Here is the ngrep output: > > > > U 128.131.80.101:1558 -> 128.131.80.136:5060 > > INVITE sip:obelix.ict.tuwien.ac.at SIP/2.0..Via: SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP > > 128.131.80.191:5070;branch=z9hG4bK2024693217..Route: <sip:iptel. > > org>..Route: <sip:klaus3000@klausix.ict.tuwien.ac.at>..From: > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > <sip:klaus3000@iptel.org>..Call-ID: 744056460(a)128.131.80 > > .191..CSeq: 20 INVITE..Contact: > > <sip:brutus@128.131.80.191:5070>..max-forwards: 10..user-agent: > > oSIP/Linphone-0.9.1..Content-Type: application/sdp..Content-Length: > > 335 .... > > v=0..o=brutus 123456 654321 IN IP4 128.131.80.191..s=A > > c..onversation..c=IN IP4 128.131.80.191..t=0 0..m=audio > 7078 RTP/AVP 3 > > 115 8 110 111 101..a=rtpmap:3 gsm/8000/1..a=rtp > > map:115 lpc10-1.5/8000/1..a=rtpmap:8 PCMA/8000/1..a=rtpmap:110 > > speex-4/8000/1..a=rtpmap:111 speex_lbr-4/8000/1..a=rtpmap:101 > > telephone-event/8000..a=fmtp:101 0-11.. > > # > > U 128.131.80.136:5060 -> 128.131.80.101:1557 > > SIP/2.0 100 trying -- your call is important to us..Via: > SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP > > 128.131.80.191:5070;branch=z9hG4bK2024693217..From: <sip > > :brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > <sip:klaus3000@iptel.org>..Call-ID: > 744056460@128.131.80.191..CSeq: 20 > > INVITE..Server: Sip EXpress router (0.8.10 (i386/l > > inux))..Content-Length: 0..Warning: 392 > 128.131.80.136:5060 "Noisy > > feedback tells: pid=21552 req_src_ip=128.131.80.101 > > in_uri=sip:obelix.ict.tuwien.ac.at out_uri=sip:iptel.o > > rg via_cnt==2".... > > > > # > > U 128.131.80.136:5060 -> 195.37.77.101:5060 > > INVITE sip:iptel.org SIP/2.0..Via: SIP/2.0/UDP > > 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..Via: SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 128.131.80.191: > > 5070;branch=z9hG4bK2024693217..Route: > > <sip:klaus3000@klausix.ict.tuwien.ac.at>..From: > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > <sip:klaus3000@iptel.org>..Call > > -ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Contact: > > <sip:brutus@128.131.80.191:5070>..max-forwards: 9 ..user-agent: > > oSIP/Linphone-0.9.1..Content-Type: application/sdp.. > > Content-Length: 335 ....v=0..o=brutus 123456 654321 IN IP4 > > 128.131.80.191..s=A c..onversation..c=IN IP4 128.131.80.191..t=0 > > 0..m=audio 7078 RTP/AVP 3 115 8 110 111 101..a=r > > tpmap:3 gsm/8000/1..a=rtpmap:115 lpc10-1.5/8000/1..a=rtpmap:8 > > PCMA/8000/1..a=rtpmap:110 speex-4/8000/1..a=rtpmap:111 > > speex_lbr-4/8000/1..a=rtpmap:101 telephone-event/8000..a > > =fmtp:101 0-11.. > > > > # > > U 195.37.77.101:5060 -> 128.131.80.136:5060 > > SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP > > 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..Via: SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 12 > > 8.131.80.191:5070;branch=z9hG4bK2024693217..From: > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07.3f3c > > ..Call-ID: 744056460@128.131.80.191..CSeq: 20 > > INVITE..Proxy-Authenticate: Digest realm="iptel.org", > > nonce="3e40f29900000000d6e1790446755f1b4b96f5f5bd97b283", > > algorithm=MD5.. > > Server: Sip EXpress router (0.8.9 (i386/linux))..Content-Length: > > 0..Warning: 392 195.37.77.101:5060 "Noisy feedback tells: pid=7651 > > req_src_ip=128.131.80.136 in_uri=sip:ipte > > l.org out_uri=sip:klaus3000@klausix.ict.tuwien.ac.at > via_cnt==3".... > > > > # > > U 128.131.80.136:5060 -> 128.131.80.101:1557 > > SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP > > 128.131.80.191:5070;branch=z9hG4bK2024693217..From: <sip:brutus@o > > belix.ict.tuwien.ac.at>;tag=262992618..To: > > > <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07.3f3c..C > > al > > l-ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Proxy-Aut > > henticate: Digest realm="iptel.org", > > nonce="3e40f29900000000d6e1790446755f1b4b96f5f5bd97b283", > > algorithm=MD5..Server: Sip EXpress router (0.8.9 > > (i386/linux))..Content-Length > > : 0..Warning: 392 195.37.77.101:5060 "Noisy feedback > tells: pid=7651 > > req_src_ip=128.131.80.136 in_uri=sip:iptel.org > > out_uri=sip:klaus3000@klausix.ict.tuwien.ac.at via_cnt==3 > > ".... > > > > # > > U 128.131.80.136:5060 -> 195.37.77.101:5060 > > ACK sip:iptel.org SIP/2.0..Via: SIP/2.0/UDP > > 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..From: > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..Call-ID: > > 744056460(a)128.13 > > 1.80.191..To: > > > <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07 > .3f3c..CSe > > q: 20 ACK.. > > > > > > > > If you need more details please let me know. > > > > regards, > > Klaus > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers > > >

21 years, 4 months

2
1
0 0

RE: [Serusers] ser crashes

by Jiri Kuthan

Looking at log files may help you to discover the issue. It is very likely that the module paths are different for the compiled than for the installed modules. -jiri At 03:19 PM 2/6/2003, Klaus Darilion wrote: >Hello! > >I have problems running the self compiled ser version (without any >sourcecode changes). > >I uninstalled the rpms ("rpm -e ser-mysql" and "rpm -e ser" - I use the >mysql authentication). Then I compiled ser with "make all" without >errors. I installed ser with "make install". Then I tried to start ser >with: ># /usr/local/sbin/ser -f /etc/ser/ser.cfg >ERROR: bad config file (25 errors) > >Why does my config file doesn't work anymore (it worked with the rpm >version)?

21 years, 4 months

1
0
0 0

Re: [Serusers] Sip server

by Geetha Shree

Hi, Thanks for the Reply. I am using the SER server with the default configuration. Infact I have not installed the SQL database also. I am using the SER 0.8.10 verison. With Linux 7.3 as OS. I registered with the following SIP URI to SER server from two different machines. sip:anuradha@there.com sip:LittleGuy@there.com It registered Successfully. But When I sent an INVITE request from sip:anuradha@there.com to LittleGuy(a)there.com it gives the server error. Thanks Geetha ---------- Original Message ---------------------------------- From: Jiri Kuthan <serusers(a)lists.iptel.org> Date: Wed, 05 Feb 2003 19:13:48 +0100 >Please send a complete description of the case: >full network dumps, your configuration file, your >logs and information about version of ser and OS >you are using. > >Thank you, > >-Jiri > >At 02:02 PM 2/5/2003, Geetha Shree wrote: >>Hi, >> >>I am new to SIP. >>I have installed the SER server and my REGISTER method is working ok. >>But when I send the INVITE method I am getting the following error from SER server. >> >>The invite packet which has been sent by me is: >> >>INVITE sip:anuradha@there.com SIP/2.0 >>From: <sip:LittleGuy@there.com>;tag=1044365919410 >>To: <sip:anuradha@there.com > >>Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK1159de0c6cca18f9131c8ff342527668 >>CSeq: 1 INVITE >>Call-Id: a1371c790546f9a2df76be1f59f6a7dc(a)192.168.1.9 >>Contact: <sip:192.168.1.9:5060;transport=UDP> >>Content-Length: 0 >> >>192.168.1.9 is my SER server's address >> >>The response got from the SER server is: >> >>SIP/2.0 500 I'm terribly sorry, server error occured (1/SL) >>From: <sip:LittleGuy@there.com>;tag=1044365919410 >>To: <sip:anuradha@there.com>;tag=d907c037823644515dfe0ede38ca9976.3592 >>Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK1159de0c6cca18f9131c8ff342527668;received=192.168.1.21 >>CSeq: 1 INVITE >>Call-Id: a1371c790546f9a2df76be1f59f6a7dc(a)192.168.1.9 >>Server: Sip EXpress router (0.8.10 (i386/linux)) >>Content-Length: 0 >>Warning: 392 192.168.1.9:5060 "Noisy feedback tells: pid=1587 req_src_ip=192.168.1.21 in_uri=sip:LittleGuy@there.com out_uri=sip:LittleGuy@there.com via_cnt==1" >> >>Can you help on this please >> >>Thanks in advance >>Geetha >>_______________________________________________ >>Serusers mailing list >>serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers > >

21 years, 4 months

2
1
0 0

[Serusers] ser crashes

by Klaus Darilion

Hello! During playing around with route headers I discovered that ser crashes reproduceable when I send the following request to it with sipsak, I think the invite is a valid request with strict routing. sipsak.exe -f invite3.txt -s sip:obelix.ict.tuwien.ac.at -vvv invite3.txt: INVITE sip:obelix.ict.tuwien.ac.at SIP/2.0 Via: SIP/2.0/UDP 128.131.80.191:5070;branch=z9hG4bK2024693217 Route: <sip:iptel.org> Route: <sip:klaus3000@klausix.ict.tuwien.ac.at> From: <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618 To: <sip:klaus3000@iptel.org> Call-ID: 744056460(a)128.131.80.191 CSeq: 20 INVITE Contact: <sip:brutus@128.131.80.191:5070> max-forwards: 10 user-agent: oSIP/Linphone-0.9.1 Content-Type: application/sdp Content-Length: 335 .. sdp .. then ser stops to respond: >[root@obelix darilion]# /etc/init.d/ser status >ser dead but subsys locked and in /var/log/messages Feb 5 11:57:21 obelix ser: Listening on Feb 5 11:57:21 obelix ser: 128.131.80.136 [128.131.80.136]::5060 Feb 5 11:57:21 obelix ser: Aliases: obelix.ict.tuwien.ac.at:5060 Feb 5 11:57:21 obelix ser: ser startup succeeded Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: mod_init(): Database connection opened successfuly Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: INFO: udp_init: SO_RCVBUF is initially 65535 Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: INFO: udp_init: SO_RCVBUF is finally 131070 Feb 5 11:57:21 obelix /usr/sbin/ser[21432]: INFO: fifo process starting: 21432 Feb 5 11:57:21 obelix /usr/sbin/ser[21432]: SER: open_uac_fifo: fifo server up at /tmp/ser_fifo... ..up to here everything works fine, than I send the request: Feb 5 11:57:30 obelix /usr/sbin/ser[21428]: BUG: qm_*: fragm. 0x422b9ad0 end overwritten(35322e64, 39306665)! Feb 5 11:57:30 obelix /usr/sbin/ser[21426]: child process 21428 exited by a signal 11 Feb 5 11:57:30 obelix /usr/sbin/ser[21426]: core was not generated Feb 5 11:57:30 obelix /usr/sbin/ser[21426]: INFO: terminating due to SIGCHLD Here is the ngrep output: U 128.131.80.101:1558 -> 128.131.80.136:5060 INVITE sip:obelix.ict.tuwien.ac.at SIP/2.0..Via: SIP/2.0/UDP klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 128.131.80.191:5070;branch=z9hG4bK2024693217..Route: <sip:iptel. org>..Route: <sip:klaus3000@klausix.ict.tuwien.ac.at>..From: <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: <sip:klaus3000@iptel.org>..Call-ID: 744056460(a)128.131.80 .191..CSeq: 20 INVITE..Contact: <sip:brutus@128.131.80.191:5070>..max-forwards: 10..user-agent: oSIP/Linphone-0.9.1..Content-Type: application/sdp..Content-Length: 335 .... v=0..o=brutus 123456 654321 IN IP4 128.131.80.191..s=A c..onversation..c=IN IP4 128.131.80.191..t=0 0..m=audio 7078 RTP/AVP 3 115 8 110 111 101..a=rtpmap:3 gsm/8000/1..a=rtp map:115 lpc10-1.5/8000/1..a=rtpmap:8 PCMA/8000/1..a=rtpmap:110 speex-4/8000/1..a=rtpmap:111 speex_lbr-4/8000/1..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-11.. # U 128.131.80.136:5060 -> 128.131.80.101:1557 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 128.131.80.191:5070;branch=z9hG4bK2024693217..From: <sip :brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: <sip:klaus3000@iptel.org>..Call-ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Server: Sip EXpress router (0.8.10 (i386/l inux))..Content-Length: 0..Warning: 392 128.131.80.136:5060 "Noisy feedback tells: pid=21552 req_src_ip=128.131.80.101 in_uri=sip:obelix.ict.tuwien.ac.at out_uri=sip:iptel.o rg via_cnt==2".... # U 128.131.80.136:5060 -> 195.37.77.101:5060 INVITE sip:iptel.org SIP/2.0..Via: SIP/2.0/UDP 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..Via: SIP/2.0/UDP klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 128.131.80.191: 5070;branch=z9hG4bK2024693217..Route: <sip:klaus3000@klausix.ict.tuwien.ac.at>..From: <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: <sip:klaus3000@iptel.org>..Call -ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Contact: <sip:brutus@128.131.80.191:5070>..max-forwards: 9 ..user-agent: oSIP/Linphone-0.9.1..Content-Type: application/sdp.. Content-Length: 335 ....v=0..o=brutus 123456 654321 IN IP4 128.131.80.191..s=A c..onversation..c=IN IP4 128.131.80.191..t=0 0..m=audio 7078 RTP/AVP 3 115 8 110 111 101..a=r tpmap:3 gsm/8000/1..a=rtpmap:115 lpc10-1.5/8000/1..a=rtpmap:8 PCMA/8000/1..a=rtpmap:110 speex-4/8000/1..a=rtpmap:111 speex_lbr-4/8000/1..a=rtpmap:101 telephone-event/8000..a =fmtp:101 0-11.. # U 195.37.77.101:5060 -> 128.131.80.136:5060 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..Via: SIP/2.0/UDP klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 12 8.131.80.191:5070;branch=z9hG4bK2024693217..From: <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07.3f3c ..Call-ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Proxy-Authenticate: Digest realm="iptel.org", nonce="3e40f29900000000d6e1790446755f1b4b96f5f5bd97b283", algorithm=MD5.. Server: Sip EXpress router (0.8.9 (i386/linux))..Content-Length: 0..Warning: 392 195.37.77.101:5060 "Noisy feedback tells: pid=7651 req_src_ip=128.131.80.136 in_uri=sip:ipte l.org out_uri=sip:klaus3000@klausix.ict.tuwien.ac.at via_cnt==3".... # U 128.131.80.136:5060 -> 128.131.80.101:1557 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 128.131.80.191:5070;branch=z9hG4bK2024693217..From: <sip:brutus@o belix.ict.tuwien.ac.at>;tag=262992618..To: <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07.3f3c..Cal l-ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Proxy-Aut henticate: Digest realm="iptel.org", nonce="3e40f29900000000d6e1790446755f1b4b96f5f5bd97b283", algorithm=MD5..Server: Sip EXpress router (0.8.9 (i386/linux))..Content-Length : 0..Warning: 392 195.37.77.101:5060 "Noisy feedback tells: pid=7651 req_src_ip=128.131.80.136 in_uri=sip:iptel.org out_uri=sip:klaus3000@klausix.ict.tuwien.ac.at via_cnt==3 ".... # U 128.131.80.136:5060 -> 195.37.77.101:5060 ACK sip:iptel.org SIP/2.0..Via: SIP/2.0/UDP 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..From: <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..Call-ID: 744056460(a)128.13 1.80.191..To: <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07.3f3c..CSe q: 20 ACK.. If you need more details please let me know. regards, Klaus

21 years, 4 months

2
2
0 0

[Serusers] ser status update 2003/II

by Jiri Kuthan

Folks, we've been asked frequently questions "when will be the next release out", "what new features can I be looking forward to", "will the next ser release include a b2bua", etc. This update gives you answers to some of these question, don't hesitate to ask me if you want to know more. Also, on this opportunity I would like to thank wholeheartly to our contributors -- they came up with many excellent ideas, running code and their work has been a great encouragement to us. New Features ------------ - presence agent and presence support in SIMPLE2Jabber gateway - dynamic domain management (simplifies hosting multiple domains, which was quite manual work till now) - enum support - nathelper module for getting over NATs with ATAs - beta-version of voicemail - 3261-alignment: support for TCP and loose-routing - accounting improved, reporting to serweb's "missed calls" now possible There is many other tiny useful things: exec module was made more comfortable, support for powerPC was introduced, CC-Diversion support for talking to Cisco gateways, netbsd support, ser is now 64 bits clean, and generally lot of clean-ups were applied to keep code-base sane in spite of all the new features. All bugs reported so far have been fixed. User's guide documents more usage scenarios with more examples. Performance has been boosted too -- we achieved 5kCPS with a tuned ser version for stateful forwarding without user location. Good for dealing with many stress situations. There are also many other things frequently asked for, which will not be part of the next release. The most frequently asked one, b2bua, for example. If you miss a feature urgently, implementing and contributing it may be quicker than waiting until someone else does that. We will be glad to provide guidance. Features that have been asked until now and I have not forgotten are b2bua, FCP client, SIP Address Translator. When ---- I better don't tell you -- I would set your expectations and they would lead to disappointment if it takes longer than hoped for (which simply happens too often). I hope to have a pre-alpha, testers-only release in course of February -- and we will invite all impatient testers to use it. SIP Accounts ------------ Don't forget -- you don't need to run your own server -- if all you need is a SIP account, get one from iptel at http://www.iptel.org/user/reg/index.php, of course ser-powered :-) -Jiri on behalf of all who have contributed to SER advancement -- Jiri Kuthan http://iptel.org/~jiri/

21 years, 4 months

3
2
0 0

[Serusers] Sip server

by Geetha Shree

Hi, I am new to SIP. I have installed the SER server and my REGISTER method is working ok. But when I send the INVITE method I am getting the following error from SER server. The invite packet which has been sent by me is: INVITE sip:anuradha@there.com SIP/2.0 From: <sip:LittleGuy@there.com>;tag=1044365919410 To: <sip:anuradha@there.com > Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK1159de0c6cca18f9131c8ff342527668 CSeq: 1 INVITE Call-Id: a1371c790546f9a2df76be1f59f6a7dc(a)192.168.1.9 Contact: <sip:192.168.1.9:5060;transport=UDP> Content-Length: 0 192.168.1.9 is my SER server's address The response got from the SER server is: SIP/2.0 500 I'm terribly sorry, server error occured (1/SL) From: <sip:LittleGuy@there.com>;tag=1044365919410 To: <sip:anuradha@there.com>;tag=d907c037823644515dfe0ede38ca9976.3592 Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK1159de0c6cca18f9131c8ff342527668;received=192.168.1.21 CSeq: 1 INVITE Call-Id: a1371c790546f9a2df76be1f59f6a7dc(a)192.168.1.9 Server: Sip EXpress router (0.8.10 (i386/linux)) Content-Length: 0 Warning: 392 192.168.1.9:5060 "Noisy feedback tells: pid=1587 req_src_ip=192.168.1.21 in_uri=sip:LittleGuy@there.com out_uri=sip:LittleGuy@there.com via_cnt==1" Can you help on this please Thanks in advance Geetha

21 years, 4 months

3
2
0 0

[Serusers] kernel: Out of Memory: Killed process 3780 (ser).

by jaime.gill＠orange.co.uk

Hi, We have had a strange crash in the SER server we use. The load was not that big - around 10 users being served at that time. All of a sudden, the server stops responding and reports the following error in /var/log/messages: Feb 4 14:41:35 sip kernel: Out of Memory: Killed process 3780 (ser). Feb 4 14:54:52 sip kernel: Out of Memory: Killed process 3857 (ser). Feb 4 14:58:08 sip last message repeated 10 times Feb 4 15:02:17 sip kernel: Out of Memory: Killed process 3860 (ser). Feb 4 15:13:32 sip last message repeated 66 times [continues.....] Has someone else met this before? Jaime ******************************************************************************* Important. Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately. Monitoring/Viruses Orange may monitor all incoming and outgoing emails in line with current legislation. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. Orange PCS Limited is a subsidiary of Orange SA and is registered in England No 2178917, with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ. *******************************************************************************

21 years, 4 months

2
1
0 0

RE: [Serusers] ser crashes

by Klaus Darilion

Hi! > From: Jan Janak [mailto:J.Janak@sh.cvut.cz] > could you, please, generate a core dump ? Use ulimit -c > 1000000 to enable core generation and reproduce the crash. Sorry, but I'm not familiar with core dump, ulimit .... Could you please give me more detailed instructions? Where can I find the core dump? > Then compress the compiled sources along with the core dump > and send it to me. I don't use sources compiled sources, I use the rpms. regards, klaus > > thanks, Jan. > > On 05-02 12:13, Klaus Darilion wrote: > > Hello! > > > > During playing around with route headers I discovered that > ser crashes > > reproduceable when I send the following request to it with > sipsak, I > > think the invite is a valid request with strict routing. > > > > sipsak.exe -f invite3.txt -s sip:obelix.ict.tuwien.ac.at -vvv > > > > invite3.txt: > > INVITE sip:obelix.ict.tuwien.ac.at SIP/2.0 > > Via: SIP/2.0/UDP 128.131.80.191:5070;branch=z9hG4bK2024693217 > > Route: <sip:iptel.org> > > Route: <sip:klaus3000@klausix.ict.tuwien.ac.at> > > From: <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618 > > To: <sip:klaus3000@iptel.org> > > Call-ID: 744056460(a)128.131.80.191 > > CSeq: 20 INVITE > > Contact: <sip:brutus@128.131.80.191:5070> > > max-forwards: 10 > > user-agent: oSIP/Linphone-0.9.1 > > Content-Type: application/sdp > > Content-Length: 335 > > > > .. > > sdp > > .. > > > > > > then ser stops to respond: > > > > >[root@obelix darilion]# /etc/init.d/ser status > > >ser dead but subsys locked > > > > and in /var/log/messages > > Feb 5 11:57:21 obelix ser: Listening on > > Feb 5 11:57:21 obelix ser: 128.131.80.136 > > [128.131.80.136]::5060 > > Feb 5 11:57:21 obelix ser: Aliases: obelix.ict.tuwien.ac.at:5060 > > Feb 5 11:57:21 obelix ser: ser startup succeeded > > Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: mod_init(): Database > > connection opened successfuly > > Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: INFO: > udp_init: SO_RCVBUF > > is initially 65535 > > Feb 5 11:57:21 obelix /usr/sbin/ser[21426]: INFO: > udp_init: SO_RCVBUF > > is finally 131070 > > Feb 5 11:57:21 obelix /usr/sbin/ser[21432]: INFO: fifo process > > starting: 21432 > > Feb 5 11:57:21 obelix /usr/sbin/ser[21432]: SER: > open_uac_fifo: fifo > > server up at /tmp/ser_fifo... > > > > ..up to here everything works fine, than I send the request: > > > > Feb 5 11:57:30 obelix /usr/sbin/ser[21428]: BUG: qm_*: fragm. > > 0x422b9ad0 end overwritten(35322e64, 39306665)! Feb 5 > 11:57:30 obelix > > /usr/sbin/ser[21426]: child process 21428 exited by a signal 11 > > Feb 5 11:57:30 obelix /usr/sbin/ser[21426]: core was not generated > > Feb 5 11:57:30 obelix /usr/sbin/ser[21426]: INFO: > terminating due to > > SIGCHLD > > > > Here is the ngrep output: > > > > U 128.131.80.101:1558 -> 128.131.80.136:5060 > > INVITE sip:obelix.ict.tuwien.ac.at SIP/2.0..Via: SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP > > 128.131.80.191:5070;branch=z9hG4bK2024693217..Route: <sip:iptel. > > org>..Route: <sip:klaus3000@klausix.ict.tuwien.ac.at>..From: > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > <sip:klaus3000@iptel.org>..Call-ID: 744056460(a)128.131.80 > > .191..CSeq: 20 INVITE..Contact: > > <sip:brutus@128.131.80.191:5070>..max-forwards: 10..user-agent: > > oSIP/Linphone-0.9.1..Content-Type: application/sdp..Content-Length: > > 335 .... > > v=0..o=brutus 123456 654321 IN IP4 128.131.80.191..s=A > > c..onversation..c=IN IP4 128.131.80.191..t=0 0..m=audio > 7078 RTP/AVP 3 > > 115 8 110 111 101..a=rtpmap:3 gsm/8000/1..a=rtp > > map:115 lpc10-1.5/8000/1..a=rtpmap:8 PCMA/8000/1..a=rtpmap:110 > > speex-4/8000/1..a=rtpmap:111 speex_lbr-4/8000/1..a=rtpmap:101 > > telephone-event/8000..a=fmtp:101 0-11.. > > # > > U 128.131.80.136:5060 -> 128.131.80.101:1557 > > SIP/2.0 100 trying -- your call is important to us..Via: > SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP > > 128.131.80.191:5070;branch=z9hG4bK2024693217..From: <sip > > :brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > <sip:klaus3000@iptel.org>..Call-ID: > 744056460@128.131.80.191..CSeq: 20 > > INVITE..Server: Sip EXpress router (0.8.10 (i386/l > > inux))..Content-Length: 0..Warning: 392 > 128.131.80.136:5060 "Noisy > > feedback tells: pid=21552 req_src_ip=128.131.80.101 > > in_uri=sip:obelix.ict.tuwien.ac.at out_uri=sip:iptel.o > > rg via_cnt==2".... > > > > # > > U 128.131.80.136:5060 -> 195.37.77.101:5060 > > INVITE sip:iptel.org SIP/2.0..Via: SIP/2.0/UDP > > 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..Via: SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 128.131.80.191: > > 5070;branch=z9hG4bK2024693217..Route: > > <sip:klaus3000@klausix.ict.tuwien.ac.at>..From: > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > <sip:klaus3000@iptel.org>..Call > > -ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Contact: > > <sip:brutus@128.131.80.191:5070>..max-forwards: 9 ..user-agent: > > oSIP/Linphone-0.9.1..Content-Type: application/sdp.. > > Content-Length: 335 ....v=0..o=brutus 123456 654321 IN IP4 > > 128.131.80.191..s=A c..onversation..c=IN IP4 128.131.80.191..t=0 > > 0..m=audio 7078 RTP/AVP 3 115 8 110 111 101..a=r > > tpmap:3 gsm/8000/1..a=rtpmap:115 lpc10-1.5/8000/1..a=rtpmap:8 > > PCMA/8000/1..a=rtpmap:110 speex-4/8000/1..a=rtpmap:111 > > speex_lbr-4/8000/1..a=rtpmap:101 telephone-event/8000..a > > =fmtp:101 0-11.. > > > > # > > U 195.37.77.101:5060 -> 128.131.80.136:5060 > > SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP > > 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..Via: SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP 12 > > 8.131.80.191:5070;branch=z9hG4bK2024693217..From: > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..To: > > <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07.3f3c > > ..Call-ID: 744056460@128.131.80.191..CSeq: 20 > > INVITE..Proxy-Authenticate: Digest realm="iptel.org", > > nonce="3e40f29900000000d6e1790446755f1b4b96f5f5bd97b283", > > algorithm=MD5.. > > Server: Sip EXpress router (0.8.9 (i386/linux))..Content-Length: > > 0..Warning: 392 195.37.77.101:5060 "Noisy feedback tells: pid=7651 > > req_src_ip=128.131.80.136 in_uri=sip:ipte > > l.org out_uri=sip:klaus3000@klausix.ict.tuwien.ac.at > via_cnt==3".... > > > > # > > U 128.131.80.136:5060 -> 128.131.80.101:1557 > > SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP > > klausix.ict.tuwien.ac.at:1557..Via: SIP/2.0/UDP > > 128.131.80.191:5070;branch=z9hG4bK2024693217..From: <sip:brutus@o > > belix.ict.tuwien.ac.at>;tag=262992618..To: > > > <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07.3f3c..C > > al > > l-ID: 744056460@128.131.80.191..CSeq: 20 INVITE..Proxy-Aut > > henticate: Digest realm="iptel.org", > > nonce="3e40f29900000000d6e1790446755f1b4b96f5f5bd97b283", > > algorithm=MD5..Server: Sip EXpress router (0.8.9 > > (i386/linux))..Content-Length > > : 0..Warning: 392 195.37.77.101:5060 "Noisy feedback > tells: pid=7651 > > req_src_ip=128.131.80.136 in_uri=sip:iptel.org > > out_uri=sip:klaus3000@klausix.ict.tuwien.ac.at via_cnt==3 > > ".... > > > > # > > U 128.131.80.136:5060 -> 195.37.77.101:5060 > > ACK sip:iptel.org SIP/2.0..Via: SIP/2.0/UDP > > 128.131.80.136;branch=z9hG4bK3a6d.25ef09d1.0..From: > > <sip:brutus@obelix.ict.tuwien.ac.at>;tag=262992618..Call-ID: > > 744056460(a)128.13 > > 1.80.191..To: > > > <sip:klaus3000@iptel.org>;tag=fb86ad2694115d75c77dce61523c9f07 > .3f3c..CSe > > q: 20 ACK.. > > > > > > > > If you need more details please let me know. > > > > regards, > > Klaus > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers > > >

21 years, 4 months

2
1
0 0

RE: [Serusers] Routing with ser / Problems with linphone

by Klaus Darilion

I just read the "ser status update" from jiri and he wrote in the "new features" section: - 3261-alignment: support for TCP and loose-routing So I think this will be fixed in the next release? Klaus > -----Original Message----- > From: Klaus Darilion > Sent: Wednesday, February 05, 2003 11:19 AM > To: serusers(a)lists.iptel.org > Cc: Aymeric Moizard > Subject: [Serusers] Routing with ser / Problems with linphone > > > Hello! > > I've installed ser (sip:obelix.ict.tuwien.ac.at) und want'ed > to use it with linphone, so I configured linphone to use ser > as outbound proxy and registrar. The registration works fine > but not the INVITEs. ser answers to an INVITE from linphone > with a 404 Not Found and I found out that the problem is the > "Route" header in the INVITE from linphone. > > Route: <sip:obelix.ict.tuwien.ac.at;lr> > > When I remove the header from the invite and send it manually > (sipsak) the ser proxy accepts the invite and forwards it. I > think ser reacts wrong because if an RFC3261 proxy gets an > request with a route header which points to itself it should > remove the header and forward the request. > > Than I tried the same with an different proxy in the route header: > > Route: <sip:iptel.org;lr> > > Now, my ser proxy (sip:obelix.ict.tuwien.ac.at) accepts the > request and forwards it to iptel.org, but it rewrites the > invite to: INVITE sip:iptel.org;lr SIP/2.0 > > Thats what an RFC2543 proxy would do, but not an RFC3261 > proxy, which only is allowed to do that if the route header > has no "lr" parameter or if he is responsible for the domain > in the request URI. If there is an "lr" parameter the proxy > must not change the request URI. > > If I'm wrong please let me know. > > I use ser 0.8.10 with the standard config file and linphone > 0.9.1 & 0.10.0 > > Regards, > Klaus > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers > >

21 years, 4 months

2
1
0 0

[Serusers] Routing with ser / Problems with linphone

by Klaus Darilion

Hello! I've installed ser (sip:obelix.ict.tuwien.ac.at) und want'ed to use it with linphone, so I configured linphone to use ser as outbound proxy and registrar. The registration works fine but not the INVITEs. ser answers to an INVITE from linphone with a 404 Not Found and I found out that the problem is the "Route" header in the INVITE from linphone. Route: <sip:obelix.ict.tuwien.ac.at;lr> When I remove the header from the invite and send it manually (sipsak) the ser proxy accepts the invite and forwards it. I think ser reacts wrong because if an RFC3261 proxy gets an request with a route header which points to itself it should remove the header and forward the request. Than I tried the same with an different proxy in the route header: Route: <sip:iptel.org;lr> Now, my ser proxy (sip:obelix.ict.tuwien.ac.at) accepts the request and forwards it to iptel.org, but it rewrites the invite to: INVITE sip:iptel.org;lr SIP/2.0 Thats what an RFC2543 proxy would do, but not an RFC3261 proxy, which only is allowed to do that if the route header has no "lr" parameter or if he is responsible for the domain in the request URI. If there is an "lr" parameter the proxy must not change the request URI. If I'm wrong please let me know. I use ser 0.8.10 with the standard config file and linphone 0.9.1 & 0.10.0 Regards, Klaus

21 years, 4 months

1
0
0 0

FW: [Serusers] Initial setup on FreeBSD of ser using Cisco 7960 SIP

by Lenny Tropiano

Nils, Thanks! Setting listen=sip.voiping.com worked. I had listen=192.70.239.1 (which the reverse DNS records resolve to: voiping.com). So, that worked. Thanks for the help and the quick response. Regarding "not forking" it was purely for debugging purposes. It'll work now with fork=yes. Now I have: fork=yes log_stderr=no alias=voiping.com listen=sip.voiping.com Later, L. -----Original Message----- From: Nils Ohlmeier [mailto:nils@ohlmeier.de] Sent: Tuesday, February 04, 2003 1:57 PM To: Lenny Tropiano; serusers(a)lists.iptel.org Cc: 'VoIPing, LLC (IT Consulting)' Subject: Re: [Serusers] Initial setup on FreeBSD of ser using Cisco 7960 SIP Hi, On Tuesday 04 February 2003 19:09, Lenny Tropiano wrote: > I'm "playing" with SER trying to understand how it all works, and to > be completely honest I haven't finished reading all the docs. > Basically I'm using the default ser.cfg (installed in > /usr/local/etc/ser) and I have two 7960s with the latest SIP code. I > know it works, since I can call the other phone with our > user(a)iptel.org extension ... The 2nd line is setup to register to > sip.voiping.com [192.70.239.1]. Immediately the phone gets to trying, > I have ser running to "not fork, debug 3, and log to stderr". Is their any special reason why you not allow to fork? Because from the repsonse packet bellow you can see that your request is going through end (nearly) endless loop. The via_cnt==12 means the request was forwarded 12 times (before it was stoped by the maxfws rule). I guess that ser cant detect that sip.voiping.com is one of its "myself" names. Maybe this is caused by the 'fork=no'. If not you can try to add 'listen=sip.voiping.com' to your configuration or the commandline switch '-l sip.voiping.com'. This should fix your problem. Regards Nils Ohlmeier

21 years, 4 months

1
0
0 0

[Serusers] Initial setup on FreeBSD of ser using Cisco 7960 SIP

by Lenny Tropiano

I'm "playing" with SER trying to understand how it all works, and to be completely honest I haven't finished reading all the docs. Basically I'm using the default ser.cfg (installed in /usr/local/etc/ser) and I have two 7960s with the latest SIP code. I know it works, since I can call the other phone with our user(a)iptel.org extension ... The 2nd line is setup to register to sip.voiping.com [192.70.239.1]. Immediately the phone gets to trying, I have ser running to "not fork, debug 3, and log to stderr". ngrep indicates the following: U 192.70.239.150:53087 -> 192.70.239.1:5060 REGISTER sip:sip.voiping.com SIP/2.0..Via: SIP/2.0/UDP 192.70.239.150:5060..From: sip:lenny@sip.voiping.com..To: sip:lenny@sip. voiping.com..Call-ID: 00036b54-b62d1fe8-314ef9d4-1cca7f7b@192.70.239.150..Date: Tue, 04 Feb 2003 18:07:32 GMT..CSeq: 101 REGIST ER..User-Agent: CSCO/4..Contact: <sip:lenny@192.70.239.150:5060>..Content-Length: 0..Expires: 3600.... # U 192.70.239.1:5060 -> 192.70.239.150:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 192.70.239.150:5060..From: sip:lenny@sip.voiping.com..To: sip:lenny@sip.voiping.com ;tag=e755c894a31056969aa313d5267cd575.f7b7..Call-ID: 00036b54-b62d1fe8-314ef9d4-1cca7f7b@192.70.239.150..CSeq: 101 REGISTER..Se rver: Sip EXpress router (0.8.10 (i386/freebsd))..Content-Length: 0..Warning: 392 192.70.239.1:5060 "Noisy feedback tells: pid= 71976 req_src_ip=192.70.239.1 in_uri=sip:sip.voiping.com out_uri=sip:sip.voiping.com via_cnt==12".... I would appreciate any advice in getting this going (btw, I compiled the version of SER 0.8.10 and didn't use the already compiled binaries). Thanks, Lenny --- Lenny Tropiano E-mail: lenny(a)voiping.com Partner, Networking Specialist Pager: pager-lenny(a)voiping.com VoIPing, LLC URL: http://www.voiping.com/ PO Box 867, Cedar Park, TX 78630-0867 Mobile: 512-698-VOIP [8647]

21 years, 4 months

2
1
0 0

[Serusers] New feature for the tm module [sticky proxy]

by Maxim Sobolev

Folks, We are currently trying to implement owerflow routing with sip and b2bua. Our network setup looks like the following (two GWs here is for simplicity, actually there would be dozens of them): --------- /--|PSTN GW|-\ ---- ----------------- ------- /~~~~~~\/ --------- \ /~~~~~~~~\ |UA|--|PROXY/REGISTRAR|--|B2BUA|--<IP CLOUD> <PSTN CLOUD> ---- ----------------- ------- \______/\ --------- / \________/ \--|PSTN GW|-/ --------- Since potentially each destination in the PSTN could be reached through more than one GW we would like to use that for adding some more robustness to the system, beause from time to time some of gateways might be unavailable for one reason of another (network outage, maintenance, overload etc.). t_on_negative() looks like a pretty suitable feature for the job modulo that we need to add some scheme for distinguishing real failures, such as "number is busy", from transient ones. The problem here is that b2bua is unable to do prefix-based routing, while we can't put b2bua between the UA and PROXY because for accounting reasons we should be able to get from b2bua IP number of the gateway the call was forwarded to. Therefore, we do gateway selection based on prefix in ser (using rewritehostport) and then just forward request to the b2bua using t_relay_to(). To catch failures and perform retries we use t_on_negative() and number of reply_route[] blocks and it is where the problem lies - after appending a new branch ser forwards the request to the host:port specified in the uri directly, but not through the b2bua. Attached patch adds a new variable sticky_relay_to, which if set to non-zero value instructs ser to record proxy address to which transaction was originally forwarded with t_relay_to(). On failure ser forwards request to that address if another branch was appended in reply_route[]. I think that it is generally useful feature and it would be nice to see it integrated into the next release. Thanks! -Maxim

21 years, 4 months

2
2
0 0

[Serusers] (no subject)

by mko＠cs.stir.ac.uk

Hi, I have installed SER on linux and created a few users. I can register these users from SIP phones and soft-phones and can also establish connections between them. I have also created a user on the iptel.org server. I can ring from a client registered with my domain (cs.stir.ac.uk) the client registered with iptel.org. It works perfectly. However, ringing from the client registered with iptel.org a client registered locally doesn't work. Is this a config problem? How can I fix this? Any help is greatly appreciated! Best regards, Mario Kolberg -- Mario Kolberg phone: +44 (0)1786 46 7440 Lecturer in Computing Science fax : +44 (0)1786 46 4551 email: mko(a)cs.stir.ac.uk Department of Computing Science and Mathematics University of Stirling Stirling FK9 4LA Scotland, UK -- The University of Stirling is a university established in Scotland by charter at Stirling, FK9 4LA. Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not disclose, copy or deliver this message to anyone and any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of the University of Stirling shall be understood as neither given nor endorsed by it.

21 years, 4 months

2
1
0 0

[Serusers] Error message I don't understand

by s-ser-maillinglist＠hilft.net

Hello, I'm trying to use the presence agent that is in the CVS version. I added the module and the lines ---- if (method=="SUBSCRIBE") { subscribe("registrar"); break; }; ---- to my ser.cfg file. By changing this I get the following error message when trying to "sign in" with the msn messenger UA: ---- 15(23129) ERROR: t_reply: cannot send a t_reply to a message for which no T-state has been established 15(23129) send_reply(): Error while sending 200 OK ---- What does this mean? I admit I don't know a lot about the details of the SIP protocol, but if you'd give me a hint on where to search, it'd help me a lot. Is the presence agent in CVS already usable at all? If yes, could someone please provide me a working config file? Thanks in advance, Stefan Schmidt

21 years, 4 months

2
1
0 0

[Serusers] Routing to the PSTN

by Phillip Haynes

Hi, I have set up the SER and its working. The only problem is I cant get the routing logic to simultaneously route to either the User Loc or the PSTN. Its only doing one of the other. I am new to SIP, can u show me a sample script that will do both at the same time? Best regards, Phillip

21 years, 5 months

5
7
0 0

[Serusers] Windows Messenger authentication fails.

by Ivan Vignola

Hi, I have successfully (I think that) installed SER server with ser-mysql package. I have set the environment variable 'SIP_DOMAIN="192.168.11.237"' (that is server IP address). I have succesfully added a user to subscriber table: 'serctl add ivan ivanpswd ivan(a)hotmail.com', but registering WM to server fails: URI = 'ivan(a)192.168.11.237' Passwowd = 'ivanpswd' User = 'ivan' This is my ser.cfg file: # ----------- global configuration parameters ------------------------ debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=yes # (cmd line: -E) 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 ---------------------------------- loadmodule "//usr/lib/ser/modules/mysql.so" loadmodule "//usr/lib/ser/modules/sl.so" loadmodule "//usr/lib/ser/modules/tm.so" loadmodule "//usr/lib/ser/modules/rr.so" loadmodule "//usr/lib/ser/modules/maxfwd.so" loadmodule "//usr/lib/ser/modules/usrloc.so" loadmodule "//usr/lib/ser/modules/registrar.so" loadmodule "//usr/lib/ser/modules/auth.so" # ----------------- setting module-specific parameters --------------- modparam("usrloc", "db_mode", 2) modparam("auth", "db_url", "sql://ser:heslo@localhost/ser") modparam("auth", "calculate_ha1", yes) modparam("auth", "password_column", "password") # ------------------------- request routing logic ------------------- alias="engiweb.com" alias="sip.engiweb.com" route{ 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; }; rewriteFromRoute(); if (uri=~"^sip:(.+@)?(192\.168\.11\.237|(sip\.)?engiweb\.com)([:;\?].*)?$") { if (method=="REGISTER") { if (!www_authorize("192.168.11.237", "subscriber")) { if (!proxy_authorize("192.168.11.237", "subscriber")) { www_challenge("engiweb.org", "0"); break; }; save("location"); break; }; lookup("aliases"); if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; if (!t_relay()) { sl_reply_error(); }; } What could be the problem? Best regards. Ivan Vignola. _________________________________________________________________ MSN Extra Storage: piena libertà di esprimersi e comunicare http://www.msn.it/msnservizi/es/extra_storage_tag/

21 years, 5 months

4
5
0 0

RE: [Serusers] user permission problem on ser-jabber gw

by Toni Barata (EPS)

Hi Daniel, The problem related with the permition to use de jabber gateway seems to be solved. Now I have a new problem. In the same scenario (Messenger sending a message to Jabber client) the messenger receives from the jabber gw the following error message: " ERROR:Connection to Jabber server lost. You have to login to Jabber server again (join the conferences again that you were participating, too)<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />" Can you figure what is happening here? Thanks, Toni -----Original Message----- From: Daniel-Constantin MIERLA [mailto:mierla@fokus.fraunhofer.de] Sent: sexta-feira, 31 de Janeiro de 2003 12:51 To: Toni Barata (EPS) Cc: 'serusers(a)lists.iptel.org' Subject: Re: [Serusers] user permission problem on ser-jabber gw Hello, the SIP_ID field must be the SIP URI of the SIP user (e.g. ' sip:user1@mydomain.com <mailto:sip:user1@mydomain.com> ') -- that is for fast matching - From tag includes sip: in address of the origin. If you check the manual or the mail I pointed, the samples show that. Toni Barata (EPS) wrote: Hi Daniel, I have done this (creating the database sip_jab) before sending my first email. Regarding the association of SIP users with Jabber IDs, I have added an entry on table jusers this way on mysql: mysql> INSERT INTO jusers VALUES ('1','user1','user1',' user1(a)mydomain.com <mailto:user1@mydomain.com> ','0'); Should it be done this way or there are others ways to do it? If you take the sources of the module, in directory 'doc' you can find some perl or php scripts which can help you. You have to change the values from the beginning of scripts according with your configuration. The same problem persists. Try again now. Regards, Daniel Regards, Toni -----Original Message----- From: Daniel-Constantin MIERLA [ mailto:mierla@fokus.fraunhofer.de <mailto:mierla@fokus.fraunhofer.de> ] Sent: quinta-feira, 30 de Janeiro de 2003 19:54 To: Toni Barata (EPS) Cc: ' serusers(a)lists.iptel.org <mailto:serusers@lists.iptel.org> ' Subject: Re: [Serusers] user permission problem on ser-jabber gw Hello, you have to create the database for SIMPLE2Jabber gateway and after that you have to associate SIP users with Jabber IDs. I wrote a manual for gateway, but is more related to next ser release. Anyway, the database is the same, exported methods too, only some parameters has changed. The database can be created using sql script from CVS http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/jabber/doc/ <http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/jabber/doc /> xjab.sql?rev=1.1&content-type=text/vnd.viewcvs-markup or from manual http://www.iptel.org/ser/doc/jabgw/xjab-manual.html#5._Admins_guide <http://www.iptel.org/ser/doc/jabgw/xjab-manual.html#5._Admins_guide> It might provide a good help to read next message (especially last part of it) posted on this list http://lists.iptel.org/pipermail/serusers/2002-December/000049.html <http://lists.iptel.org/pipermail/serusers/2002-December/000049.html> After that if you still have problems do not hesitate to post a new message on the list. Best regards, Daniel Toni Barata (EPS) wrote: Hi folks, ( I think!) I have successfully installed SER server with the ser-mysql and ser-jabber packages ( I have also a mysql server and a Jabber server running). For testing I have established a SIP IM session between two MS Messengers and it did work. After this I have tried to establish a IM session between a user SIP (MS Messenger) and a user Jabber (Exodus), but when the messenger sends a message for the jabber gateway the following error occurs: "ERROR: Your message was not sent. You do not have permision to use the gateway." What could be the problem here? Best regards, Toni _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org <mailto:serusers@lists.iptel.org> http://lists.iptel.org/mailman/listinfo/serusers <http://lists.iptel.org/mailman/listinfo/serusers> _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org <mailto:serusers@lists.iptel.org> http://lists.iptel.org/mailman/listinfo/serusers <http://lists.iptel.org/mailman/listinfo/serusers>

21 years, 5 months

2
1
0 0

Re: [Serusers] Windows Messenger authentication fails.

by Ivan Vignola

Hi Nils, thank you for your suggestion. 192.168.11.237 is my sever IP address and realm. I've added a user with USER_ID=ivan(a)192.168.11.237 PASSWORD=ivanpswd EMAIL-ADDRESS=ivan(a)hotmail.com in subscriber table as you wrote e I'm trying to register WM: ACCOUNT=ivan(a)192.168.11.237 PASSWORD=ivanpswd USER=ivan(a)192.168.11.237 Authentication doesn't work!!! Where am I wrong? Thank you in advance. Ivan. >From: Nils Ohlmeier <nils(a)ohlmeier.de> >To: "Ivan Vignola" <ivanvignola(a)hotmail.com>, serusers(a)lists.iptel.org >Subject: Re: [Serusers] Windows Messenger authentication fails. >Date: Fri, 31 Jan 2003 14:36:47 +0100 > >Hi Ivan, > >the problem with WM is that the address of the server have to be the same >as >the domain part of the URI (which is not RFC conform). For example you have >to add ivan(a)192.168.11.237 to the subscriber table and also use this >account >within your WM to get authentication working. > >Regards > Nils Ohlmeier > >On Friday 31 January 2003 13:30, Ivan Vignola wrote: > > Hi, > > I have successfully (I think that) installed SER server with ser-mysql > > package. > > I have set the environment variable 'SIP_DOMAIN="192.168.11.237"' (that >is > > server IP address). > > I have succesfully added a user to subscriber table: 'serctl add ivan > > ivanpswd ivan(a)hotmail.com', but registering WM to server fails: > > URI = 'ivan(a)192.168.11.237' > > Passwowd = 'ivanpswd' > > User = 'ivan' > > > > This is my ser.cfg file: > > > > > > # ----------- global configuration parameters ------------------------ > > > > debug=3 # debug level (cmd line: -dddddddddd) > > fork=yes > > log_stderror=yes # (cmd line: -E) > > 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 ---------------------------------- > > > > loadmodule "//usr/lib/ser/modules/mysql.so" > > loadmodule "//usr/lib/ser/modules/sl.so" > > loadmodule "//usr/lib/ser/modules/tm.so" > > loadmodule "//usr/lib/ser/modules/rr.so" > > loadmodule "//usr/lib/ser/modules/maxfwd.so" > > loadmodule "//usr/lib/ser/modules/usrloc.so" > > loadmodule "//usr/lib/ser/modules/registrar.so" > > loadmodule "//usr/lib/ser/modules/auth.so" > > > > > > > > # ----------------- setting module-specific parameters --------------- > > > > modparam("usrloc", "db_mode", 2) > > modparam("auth", "db_url", "sql://ser:heslo@localhost/ser") > > modparam("auth", "calculate_ha1", yes) > > modparam("auth", "password_column", "password") > > > > # ------------------------- request routing logic ------------------- > > > > alias="engiweb.com" > > alias="sip.engiweb.com" > > > > route{ > > 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; > > }; > > > > rewriteFromRoute(); > > > > if > > (uri=~"^sip:(.+@)?(192\.168\.11\.237|(sip\.)?engiweb\.com)([:;\?].*)?$") >{ > > > > > > if (method=="REGISTER") { > > > > if (!www_authorize("192.168.11.237", "subscriber")) { > > if (!proxy_authorize("192.168.11.237", "subscriber")) { > > www_challenge("engiweb.org", "0"); > > break; > > }; > > > > > > save("location"); > > break; > > }; > > > > lookup("aliases"); > > if (!lookup("location")) { > > sl_send_reply("404", "Not Found"); > > break; > > }; > > }; > > > > if (!t_relay()) { > > sl_reply_error(); > > }; > > > > } > > > > What could be the problem? > > > > Best regards. > > > > Ivan Vignola. > > > > > > > > > > > > > > _________________________________________________________________ > > MSN Extra Storage: piena libertà di esprimersi e comunicare > > http://www.msn.it/msnservizi/es/extra_storage_tag/ > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > >-- >gpg-key: http://www.ohlmeier.org/public_key.asc ><< attach3 >> _________________________________________________________________ Vuoi ricevere fantastiche offerte promozionali via email? http://www.msn.it/msnservizi/so/

21 years, 5 months

2
2
0 0

RE: [Serusers] user permission problem on ser-jabber gw

by Toni Barata (EPS)

Hi Daniel, I have done this (creating the database sip_jab) before sending my first email. Regarding the association of SIP users with Jabber IDs, I have added an entry on table jusers this way on mysql: mysql> INSERT INTO jusers VALUES ('1','user1','user1','user1(a)mydomain.com','0'); Should it be done this way or there are others ways to do it? The same problem persists. Regards, Toni -----Original Message----- From: Daniel-Constantin MIERLA [mailto:mierla@fokus.fraunhofer.de] Sent: quinta-feira, 30 de Janeiro de 2003 19:54 To: Toni Barata (EPS) Cc: 'serusers(a)lists.iptel.org' Subject: Re: [Serusers] user permission problem on ser-jabber gw Hello, you have to create the database for SIMPLE2Jabber gateway and after that you have to associate SIP users with Jabber IDs. I wrote a manual for gateway, but is more related to next ser release. Anyway, the database is the same, exported methods too, only some parameters has changed. The database can be created using sql script from CVS http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/jabber/doc/ xjab.sql?rev=1.1&content-type=text/vnd.viewcvs-markup or from manual http://www.iptel.org/ser/doc/jabgw/xjab-manual.html#5._Admins_guide It might provide a good help to read next message (especially last part of it) posted on this list http://lists.iptel.org/pipermail/serusers/2002-December/000049.html After that if you still have problems do not hesitate to post a new message on the list. Best regards, Daniel Toni Barata (EPS) wrote: >Hi folks, > >( I think!) I have successfully installed SER server with the ser-mysql and >ser-jabber packages ( I have also a mysql server and a Jabber server >running). >For testing I have established a SIP IM session between two MS Messengers >and it did work. >After this I have tried to establish a IM session between a user SIP (MS >Messenger) and a user Jabber (Exodus), but when the messenger sends a >message for the jabber gateway the following error occurs: > >"ERROR: Your message was not sent. You do not have permision to use the >gateway." > >What could be the problem here? > >Best regards, >Toni > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers > > >

21 years, 5 months

2
1
0 0

[Serusers] [Fwd: ser-0.8.10: Server shutdown, deinstall and reinstalling

by Savasar Sinan UYGUR

Hello, I am now working with iptel express router source code ver 0.8.10 on a Suse 8.0 machine with gcc version 3.2 How can i send a signal to the server for shutdown and deinstall the installed server later which ist installed from a 1) tar.gz source with make install and if different 2) tar.gz source by unzipping the code under directory "/" Thanks

21 years, 5 months

2
1
0 0

[Serusers] user permission problem on ser-jabber gw

by Toni Barata (EPS)

Hi folks, ( I think!) I have successfully installed SER server with the ser-mysql and ser-jabber packages ( I have also a mysql server and a Jabber server running). For testing I have established a SIP IM session between two MS Messengers and it did work. After this I have tried to establish a IM session between a user SIP (MS Messenger) and a user Jabber (Exodus), but when the messenger sends a message for the jabber gateway the following error occurs: "ERROR: Your message was not sent. You do not have permision to use the gateway." What could be the problem here? Best regards, Toni

21 years, 5 months

2
1
0 0

[Serusers] sip server test on a local network

by Savasar Sinan UYGUR

I have installed IpTel on a SuSe 8.0 machine and have 2 Windows machines attached with a hub. When i try to add a user with: serctl add username ....- then i have a problem executing mysql. So is it because of the wrong installation or do i have to install the mysql packet from the SuSe control center? Thanks in advance.

21 years, 5 months

2
1
0 0

[Serusers] Progress on *BSD Platforms

by Art Mason

I also have found myself moving over to Free- and OpenBSD for most workstation and server needs, but I keep an install of Mandrake handy for those few apps that don't port to well over to the BSD platforms. What I'm really interested in is stund support in OpenBSD that integrated w/ pf, seeing as how the majority of my firewalls are now OpenBSD 3.1-3.2 boxes running the new pf code. Ser itself runs great on FreeBSD 4.7-RELEASE, which is what I use as my testing platform, but this NAT stuff is really killing me when it comes to bringing in potential callers over the WAN. Any word on when a *BSD-compatible binary of stund might be available? Thanks. -- Art Mason CCNA Network Consultant Maverick Datacom E-mail: amason(a)maverickdatacom.com

21 years, 5 months

4
4
0 0

[Serusers] The tm module generates non-compliant branch id for final 200 OK ACKs

by Maxim Sobolev

Folks, I discovered that the tm module generates non RFC3261 compliant branch id when forwarding ACK to the final 200 OK response. The RFC, to which ser claims to complain by prefixing generated branch id with magic "z9hG4bK", mandates that ACK to the final 200 OK response should carry on the same branch id as that response and the initial INVITE. On contrary, ser currently adds RFC3261-compliant branch ids for everything, but that final ACK, which in default configuration is being sent with branch id of `0'. This creates a compatibility problem when the next hop uses that branch id for matching 200 OKs to subsequent ACKs, example of such UA is Vovida's b2bua software. I do not have a fix right now, as I am away from my lab, but it should be pretty trivial to fix by pre-loading msg->add_to_branch_s with a correct value in tm module before calling forward() and non-overriding it in the forward() if it is already non-NULL. -Maxim

21 years, 5 months

2
1
0 0

[Serusers] [Fwd: ser-0.8.10: Fehler beim Kompilierung der Quellencode.]

by Savasar Sinan UYGUR

Ich habe Suse 8.0 auf dem der Kernel 2.4.18-4GB läuft. Ich habe iptel express router ser-0.8.10.tar.gz bereits entpackt und versucht mit "make " zu kompilieren. Die Kompilation bricht mit der unten angefügten Fehlermeldung ab. Was kann ich tun ? Wurde dieser Server auf dem Suse-Linux getestet bzw. unter welchem Suse-Kernel ist es lauffähig ? MfG. >*************************************************************** >CoRiMM:/home/sinan/SIP_Project/OpenSourceServers/IPTEL/ser-0.8.10 # make >modules >make[1]: Entering directory >`/home/sinan/SIP_Project/OpenSourceServers/IPTEL/ser-0.8.10/modules/acc' >../../Makefile.rules:77: acc.d: No such file or directory >../../Makefile.rules:77: acc_mod.d: No such file or directory >make[1]: Leaving directory >`/home/sinan/SIP_Project/OpenSourceServers/IPTEL/ser-0.8.10/modules/acc' >make[1]: Entering directory >`/home/sinan/SIP_Project/OpenSourceServers/IPTEL/ser-0.8.10/modules/acc' >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c acc.c -o acc.o >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c acc_mod.c -o acc_mod.o >gcc -shared -Wl,-O2 -Wl,-E acc.o acc_mod.o -o acc.so >/usr/lib/gcc-lib/i486-suse-linux/3.2/../../../../i486-suse-linux/bin/ld: >unrecognized option '--eh-frame-hdr' >/usr/lib/gcc-lib/i486-suse-linux/3.2/../../../../i486-suse-linux/bin/ld: >use the --help option for usage information >collect2: ld returned 1 exit status >make[1]: *** [acc.so] Error 1 >make[1]: Leaving directory >`/home/sinan/SIP_Project/OpenSourceServers/IPTEL/ser-0.8.10/modules/acc' > > >make[1]: Entering directory >`/home/sinan/SIP_Project/OpenSourceServers/IPTEL/ser-0.8.10/modules/auth' > >../../Makefile.rules:77: auth_mod.d: No such file or directory >../../Makefile.rules:77: authorize.d: No such file or directory >../../Makefile.rules:77: challenge.d: No such file or directory >../../Makefile.rules:77: checks.d: No such file or directory >../../Makefile.rules:77: common.d: No such file or directory >../../Makefile.rules:77: group.d: No such file or directory >../../Makefile.rules:77: nonce.d: No such file or directory >../../Makefile.rules:77: rfc2617.d: No such file or directory >make[1]: Leaving directory >`/home/sinan/SIP_Project/OpenSourceServers/IPTEL/ser-0.8.10/modules/auth' > >make[1]: Entering directory >`/home/sinan/SIP_Project/OpenSourceServers/IPTEL/ser-0.8.10/modules/auth' > >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c auth_mod.c -o auth_mod.o >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c authorize.c -o authorize.o >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c challenge.c -o challenge.o >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c checks.c -o checks.o >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c common.c -o common.o >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c group.c -o group.o >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c nonce.c -o nonce.o >gcc -fPIC -DPIC -O9 -funroll-loops -Wcast-align -Wall >-minline-all-stringops -malign-double -falign-loops -march=athlon >-DNAME='"ser"' -DVERSION='"0.8.10"' -DARCH='"i386"' -DOS='"linux"' >-DCOMPILER='"gcc 3.2"' -D__CPU_i386 -DCFG_DIR='"/usr/local/etc/ser/"' >-DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT >-DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC >-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD >-c rfc2617.c -o rfc2617.o >gcc -shared -Wl,-O2 -Wl,-E auth_mod.o authorize.o challenge.o checks.o >common.o group.o nonce.o rfc2617.o -o auth.so >/usr/lib/gcc-lib/i486-suse-linux/3.2/../../../../i486-suse-linux/bin/ld: >unrecognized option '--eh-frame-hdr' >/usr/lib/gcc-lib/i486-suse-linux/3.2/../../../../i486-suse-linux/bin/ld: >use the --help option for usage information >collect2: ld returned 1 exit status >make[1]: *** [auth.so] Error 1 >make[1]: Leaving directory >`/home/sinan/SIP_Project/OpenSourceServers/IPTEL/ser-0.8.10/modules/auth' > >***************************************************************

21 years, 5 months

4
3
0 0

[Serusers] MY MAIN QUESTION: SIP Router Express (ser-0.8.10) Compilation on SuSe 8.0

by Savasar Sinan UYGUR

Hello, Above all my questions before, i would like to make everything clear from the beginning. I was trying to IPTEL express router under the directory which came after unzipping ser-0.8.10_src.tar.gz with the command "tar -xzvf" on my SuSe-Linux 8.0 machine with kernel 2.4.18-4GB . I got some errors during compilation. Is this version 0.8.10 compatible with SuSe 8.0? When not with which SuSe Linux distributions is it working properly? Could you send me compilation and installation procedures or refer to the related files if possible? Waiting for your reply, Best regards,

21 years, 5 months

2
1
0 0

[Serusers] Modify existing Sessions with SER?

by Karsten Knuettel

Hi *, we have a 3PCC-scenario and we want to modify an existing session. (Change IP and Port an UA is listening to) In RFC 3261 section 14 is described how to modify existing sessions throught an re-Invite but SER sends me an OK without sending the 2nd Invite to the UAC. Can you imagine what I have done wrong? (My scenario acts like Flow II in draft-ietf-sipping-3pcc-02.txt, becourse my UAC is buggy and gives me to to an Invite without SDP a 500) (The Screenshots of my test are attached) Thank you! Karsten

21 years, 5 months

2
1
0 0

[Serusers] SER and TCP

by Cinzia Raineri

Hello, I would like know if SER support also the trasmission protocol TCP, or TLS. Thanks, Cinzia.

21 years, 5 months

2
1
0 0

[Serusers] SIP2Jabber Presence Support

by jaime.gill＠orange.co.uk

Daniel, Not sure if it has been asked before. Is presence support from SIP to Jabber and viceversa completely working in cvs version? Regards, Jaime ******************************************************************************* Important. Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately. Monitoring/Viruses Orange may monitor all incoming and outgoing emails in line with current legislation. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. Orange PCS Limited is a subsidiary of Orange SA and is registered in England No 2178917, with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ. *******************************************************************************

21 years, 5 months

2
1
0 0

[Serusers] [Fwd: ser-0.8.10: Fehler beim Kompilierung der Quellencode.]

by Savasar Sinan UYGUR

21 years, 5 months

1
0
0 0

[Serusers] Connection to Jabber server lost

by jaime.gill＠orange.co.uk

Hi, When using the Jabber Gateway, some users get the following error from time to time: ERROR: Connection to Jabber server lost. You have to login to Jabber server again (join again the conferences that you were participating, too). sip_to_jabber_gateway says: INFO: Your are now offline in Jabber network. Thank you for using SIP-Jabber gateway. Do you know the reason why these messages appear and if it is possible to avoid them? Thanks, Jaime ******************************************************************************* Important. Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately. Monitoring/Viruses Orange may monitor all incoming and outgoing emails in line with current legislation. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. Orange PCS Limited is a subsidiary of Orange SA and is registered in England No 2178917, with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ. *******************************************************************************

21 years, 5 months

2
1
0 0

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