sr-users May 2004

sr-users@lists.kamailio.org

154 participants
333 discussions

by Ri Liang

Hello, I'am using The standar nathelper.cfg,v 1.1.2.1 CVS ser - stable (version: ser 0.8.12-tcp_nonb (i386/linux)) and rtpproxy 20040107 I got these error from the debug log ----------------------------------- May 29 15:51:59 sip /usr/local/sbin/ser[17674]: ERROR: extract_body: message body has lenght zero May 29 15:51:59 sip /usr/local/sbin/ser[17674]: ERROR: force_rtp_proxy: can't extract body from the message May 29 15:51:59 sip /usr/local/sbin/ser[17674]: ERROR: on_reply processing failed ----------------------------------- I also got this error running rtpproxy -f ------------------------------------- [root@sip ]# rtpproxy -f rtpproxy: rtpproxy started, pid 17940 rtpproxy: command syntax error rtpproxy: command syntax error ------------------------------------- Please advise if there is something wrong with the versión (and how i can get the correct version) Thanks Ri Liang

20 years, 2 months

[Serusers] private ip registration error

by varala ramakanth

hello friends, iam having the rel_0_8_12 running when i am registering with windows messenger from a nat client its ethereal report show that malformed sip packet so whats the problem? ser( 202.*.*.19)-->dhcp nat(202.*.*.252)-->private ip(192.168.1.18)msn messenger 4.7 please guide me with reagards rama kanth this is the log message iam getting when debug =8 *************************************************** 6(3777) SIP Request: 6(3777) method: <REGISTER> 6(3777) uri: <sip:server.pol.net.in> 6(3777) version: <SIP/2.0> 6(3777) parse_headers: flags=1 6(3777) end of header reached, state=5 6(3777) parse_headers: Via found, flags=1 6(3777) parse_headers: this is the first via 6(3777) After parse_msg... 6(3777) preparing to run routing scripts... 6(3777) DEBUG : is_maxfwd_present: searching for max_forwards header 6(3777) parse_headers: flags=128 6(3777) DEBUG: is_maxfwd_present: value = 70 6(3777) check_via_address(202.*.*.252, 192.168.1.18, 0) 6(3777) LOG: Someone trying to register from private IP, rewriting 6(3777) parse_headers: flags=64 6(3777) end of header reached, state=9 6(3777) DEBUG: get_hdr_field: <To> [29]; uri=[sip:102@server.pol.net.in] 6(3777) DEBUG: to body [<sip:102@server.pol.net.in> ] 6(3777) get_hdr_field: cseq <CSeq>: <2> <REGISTER> 6(3777) parse_headers: flags=256 6(3777) DEBUG: get_hdr_body : content_length=0 6(3777) found end of header 6(3777) find_first_route(): No Route headers found 6(3777) loose_route(): There is no Route HF 6(3777) check_self - checking if host==us: 17==9 && [server.pol.net.in] == [127.0.0.1] 6(3777) check_self - checking if port 5060 matches port 5060 6(3777) check_self - checking if host==us: 17==13 && [server.pol.net.in] == [202.*.*.19] 6(3777) check_self - checking if port 5060 matches port 5060 6(3777) check_self - checking if host==us: 17==9 && [server.pol.net.in] == [127.0.0.1] 6(3777) check_self - checking if port 5060 matches port 5060 6(3777) check_self - checking if host==us: 17==13 && [server.pol.net.in] == [202.*.*.19] 6(3777) check_self - checking if port 5060 matches port 5060 6(3777) parse_headers: flags=-1 6(3777) parse_headers: flags=-1 6(3777) check_via_address(202.*.*.252, 192.168.1.18, 0) 6(3777) receive_msg: cleaning up ************************************************* the ethereal report is ************************************************* Frame 1 (544 bytes on wire, 544 bytes captured) Arrival Time: May 29, 2004 18:00:28.644433000 Time delta from previous packet: 0.000000000 seconds Time relative to first packet: 0.000000000 seconds Frame Number: 1 Packet Length: 544 bytes Capture Length: 544 bytes Ethernet II, Src: 00:e0:2b:90:1f:00, Dst: 00:e0:18:ed:04:61 Destination: 00:e0:18:ed:04:61 (Asustek__ed:04:61) Source: 00:e0:2b:90:1f:00 (Extreme__90:1f:00) Type: IP (0x0800) Internet Protocol, Src Addr: 202.65.148.252 (202.65.148.252), Dst Addr: 202.65.128.19 (202.65.128.19) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 530 Identification: 0xcc8e Flags: 0x00 .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 125 Protocol: UDP (0x11) Header checksum: 0xc5b9 (correct) Source: 202.*.*.252 (202.*.*.252) Destination: 202.*.*.19 (202.*.*.19) User Datagram Protocol, Src Port: 61863 (61863), Dst Port: 5060 (5060) Source port: 61863 (61863) Destination port: 5060 (5060) Length: 510 Checksum: 0xde85 (correct) Session Initiation Protocol Request line: REGISTER sip:server.pol.net.in SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.1.18:15992 Max-Forwards: 70 From: <sip:102@server.pol.net.in>;tag=ddb4f954b19811d8aafe00e01846e257;epid=b28b013e73 To: <sip:102@server.pol.net.in> Call-ID: ddb4f955b19811d8aafe00e01846e257(a)192.168.1.18 CSeq: 1 REGISTER Contact: <sip:192.168.1.18:15992>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER" User-Agent: RTC/1.2.4949 Event: registration Allow-Events: presence Content-Length: 0 Frame 2 (687 bytes on wire, 687 bytes captured) Arrival Time: May 29, 2004 18:00:28.645466000 Time delta from previous packet: 0.001033000 seconds Time relative to first packet: 0.001033000 seconds Frame Number: 2 Packet Length: 687 bytes Capture Length: 687 bytes Ethernet II, Src: 00:e0:18:ed:04:61, Dst: 00:e0:2b:90:1f:00 Destination: 00:e0:2b:90:1f:00 (Extreme__90:1f:00) Source: 00:e0:18:ed:04:61 (Asustek__ed:04:61) Type: IP (0x0800) Internet Protocol, Src Addr: 202.*.*.19 (202.*.*.19), Dst Addr: 202.*.*.252 (202.*.*.252) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00) 0001 00.. = Differentiated Services Codepoint: Unknown (0x04) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 673 Identification: 0x0000 Flags: 0x04 .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0x8ea9 (correct) Source: 202.*.*.19 (202.*.*.19) Destination: 202.*.*.252 (202.*.*.252) User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 61863 (61863) Source port: 5060 (5060) Destination port: 61863 (61863) Length: 653 Checksum: 0x7bd2 (correct) Session Initiation Protocol Status line: SIP/2.0 200 OK Message Header Via: SIP/2.0/UDP 192.168.1.18:15992;rport=61863;received=202.65.148.252 From: <sip:102@server.pol.net.in>;tag=ddb4f954b19811d8aafe00e01846e257;epid=b28b013e73 To: <sip:102@server.pol.net.in>;tag=b27e1a1d33761e85846fc98f5f3a7e58.7f7e Call-ID: ddb4f955b19811d8aafe00e01846e257(a)192.168.1.18 CSeq: 1 REGISTER Contact: <sip:202.*.*.252:61863>;q=0.00;expires=3600 Server: Sip EXpress router (0.8.12-tcp_nonb (i386/linux)) Content-Length: 0 Warning: 392 202.*.*.19:5060 "Noisy feedback tells: pid=3779 req_src_ip=202.*.*.252 req_src_port=61863 in_uri=sip:server.pol.net.in out_uri=sip:server.pol.net.in via_cnt==1" Frame 3 (46 bytes on wire, 46 bytes captured) Arrival Time: May 29, 2004 18:00:54.592260000 Time delta from previous packet: 25.946794000 seconds Time relative to first packet: 25.947827000 seconds Frame Number: 3 Packet Length: 46 bytes Capture Length: 46 bytes Ethernet II, Src: 00:e0:18:ed:04:61, Dst: 00:e0:2b:90:1f:00 Destination: 00:e0:2b:90:1f:00 (Extreme__90:1f:00) Source: 00:e0:18:ed:04:61 (Asustek__ed:04:61) Type: IP (0x0800) Internet Protocol, Src Addr: 202.*.*.19 (202.*.*.19), Dst Addr: 202.*.*.252 (202.*.*.252) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00) 0001 00.. = Differentiated Services Codepoint: Unknown (0x04) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 32 Identification: 0x0000 Flags: 0x04 .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0x912a (correct) Source: 202.*.*.19 (202.*.*.19) Destination: 202.*.*.252 (202.*.*.252) User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 61863 (61863) Source port: 5060 (5060) Destination port: 61863 (61863) Length: 12 Checksum: 0x50d7 (correct) [Malformed Packet: SIP] ********************************************** __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/

20 years, 2 months

[Serusers] Call routing

by Humberto Atristain

Hello, Please help me with this I need all the calls from URI sip user xxx@serserver to be forwarded to 192.168.10.50 plus a e164 number (this is the port where the calls goes out to pstn) Fow do I do a static forwarding for this? Regards HA

20 years, 2 months

[Serusers] serweb download locations please

by Nathan

Hi I have been looking for a place to download serweb tonight. now I am pretty sure I downloaded it before from this link http://developer.berlios.de/projects/serweb/ . But now it is not available there anymore nor is it available on the ftp://ftp.berlios.de/ is serweb still being distributed? thanks for any info -Nathan -http://www.netdigix.com

20 years, 2 months

[Serusers] delay

by Kapil Dhawan

Hi List I am having a delay in network of around 1 sec...and getting one side voice from there...any reason _________________________________________________________________ Best of Indian handicrafts. http://www.fabmall.com/affiliatehtml/redir/nl8.asp At MSN Shopping.

20 years, 2 months

[Serusers] Serving Multiple Domains

by Ziad Richa

Hello, serusers Can someone helps me to configure my SER to serve multiple domains. Best regards. Richa_Ziad(a)yahoo.fr 2004-05-29 --------------------------------- Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! Créez votre Yahoo! Mail Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !

20 years, 2 months

[Serusers] ser behind firewall?

by Peter Liu

My home lan: cable modem-->routre(192.168.0.1): one linux (192.168.0.123) and one windows(192.168.0.124) I have installe ser in linux machine and I can use xten lite(UA) register with ser, but my friend can't register his xten to my ser using my public ip from cable company. I have configure my route with ser vitual server. and serctl ps shows 192.168.0.123:5060 is listening.. why my friend can't register to my ser. please help! by the way, I am new to ser, if some one want to share ser experience, please call me anytime use my FreeWorldDealup 395104. Peter __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/

20 years, 2 months

[Serusers] Sip -> h323 and vice versa

by Sergio Gerardo Festa

Hello I have a question... as I am able redireccionar a call sip to a team h323 and vice versa?? Client | | SIP Server <----> H323 | | client Saludos! Sergio Gerardo Festa Dto. Técnica Tel. 011-5219-0654 // 4334-1014 24HS 011-15-5183-9203

20 years, 2 months

[Serusers] NAT

by Ri Liang C.

Please advise what kind of media proxy or rtproxy is using at for the free users iptel.org. Is posible to get the ser.cfg that iptel.org is using ? Ri Liang

20 years, 2 months

Re: [Serusers] SEMS & mediaproxy

by Adrian Georgescu

You need to use the corresponding function (fix_nated_sdp) from nathelper module. This function is not available in mediaproxy module. See the mail archives, there are several configuration examples posted. This would work if your call to the Cisco gateway. Receiving calls from the Cisco would not help in this scenario, you need to use a rtp proxy for this either flavour your chose. Adrian >>>>>>>>> Thanks Jan, i am trying without use_media_proxy() but when SEMS answer the call, try to send RTP of greeting to the ip/port of the received SDP invite message. If i dont use media_proxy the c= line of the SDP received by sems is a private ip address. For this reason SEMS receive an icmp error message, cannot reach the private address. Also if the caller is a Cisco gateway with a public IP address, sems start sending the RTP of greeting to the public ip/port of the gateway, but receive an icmp port unrecheable message. (the Cisco gateway dont send a=direction in your SDP body). You explain about the SDP a=direction:active. This must be set in the SDP of the INVITE or in the SDP of the 200OK sent back by sems ? If i am using mediaproxy and not nathelper, can i set the a=direction:active in the SDP contents ??? -- Adrian Georgescu Founder ag-projects.com

20 years, 2 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users May 2004