sr-users January 2005

sr-users@lists.kamailio.org

199 participants
399 discussions

by edison

Hi everyone: I am trying to setup SER and Asterisk in one box.I used SER to deal with SIP packet and used Asterisk to handle RTP packet,because I want implement Voicemail/conference/Holdonmusic and so on,in my soft swith system.I am implemented basic things seems already.But I found some big problems. If I let SER outbound up.The register infomation will bypass [location] table on SER.Why is happened? And I am confused about the relationship between SER and Asterisk?How SIP packet flow through them ? Thanks for reading Regards edison

19 years, 10 months

[Serusers] HELP: How To Safely Allow Incoming INVITE Messages

by Java Rockx

Hi All. Can someone please show me an example ser.cfg snippet which allows __incoming__ INVITE messages from other SIP domains without becoming an open relay? Right now I www_challenge() when a REGISTER message comes in. I know I need to proxy_authorize() somewhere, but I'm not sure how to Many Thanks! Paul __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com

19 years, 10 months

[Serusers] hello,every one. where can I get the last SERWEB?

by fu.qihong＠zte.com.cn

*********************************************** 信息安全声明：本邮件包含信息归ZTE所有， ZTE对该邮件拥有所有权利。请接收者注意保密，未经发件人书面许可，不得向任何第三方组织和个人透露本邮件所含信息的全部或部分。以上声明仅适用于工作邮件。 Information Security Notice： The information contained in this mail is solely property of ZTE Corporation. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. ***********************************************

19 years, 10 months

[Serusers] problem re to installation from source

by pranav_mnit

hello sir, i have installed the ser from the source 8.12 but the i tried to login through messenger it is not signing in. and giving the message �sip service is not available� is there any body who can help me from pranav Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now!

19 years, 10 months

[Serusers] Configuring SER wth Asterisk

by Ashling O'Driscoll

Hi, I currently have Asterisk running behind a linux router running nat. Clients register with the public address and when the sip requests reach the router, port forwarding is used to divert the traffic to * i.e. all sip and rtp go to the asterisk box. I now want to set up ser (so that i can have sip client with urls and also to prevent the rtp stream going through asterisk). SER will also be behind the nat router. My plan is to set up port forwarding at the router forwarding all sip traffic to the ser pc. I though there might be some way from there to contact asterisk if needed by modifying the ser.cfg script. I'd really appreciate if somebody can let me know how I should modify the scripts (in asterisk and ser) and also whether this is going to be a big underatking with regard to setting up stun for nat traversal etc. I have already looked at the "asterisk at large" site on the wiki but there seems to be many ways (some more complex than others) of doing this. I would like to be able to get it done in a few hours (if possible!) as I'm being put under pressure from the powers that be!. Thanks in advance, Aisling. -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.

19 years, 10 months

[Serusers] subst() usage - weird behavior?

by Kanakatti Mahesh Subramanya

One of my clients has a weird Cisco router which is chopping off the end of the Contact headers that are being sent to me. They look like Contact: <sip:foo@192.168.28.102:5060;transport=udp;line=8hzddhav>;q= Thats right, "q=" So, I figured that as a temporary hack (till they got the Cisco patched), i'd check incoming packets, and replace the "q=" with a "q=1.0" i.e., doing the following if ( subst( '/^Contact:(.*);q=$/Contact:\1q=1.0/' ) { ... } however, as far as I can tell, the above substitution never actually takes place? What gives? Do I need to match for '\r' too? Ideas?

19 years, 10 months

[Serusers] installation

by dynamite media

i want to know a few things about installing this and what features to add... i wantto have instant messaging and voicemail as well as a-z termination and accounting features as well as my own numbering plan as well as how to make prompts in spanish basically all the features that they have here is as well http://www.wifi.com.ar/english/voip.html but i can not use the live cd and will be installed on a dedicated linux hosting, can anyone help me? i want to have a FWD type service but have it in spanish... i need help asap someone please contact me

19 years, 10 months

[Serusers] run ser as different user

by Nicolas Fauvel

Hi, I'd like to run ser as a different user as root. Actually, it creates the fifo file /tmp/ser_fifo with uid=root and gid=root. Hence, as my apache server needs to access it, I'm forced to grant apache as gid=root... and I don't want to ! I tried to pass "-u ser -g ser" in the command line, but it doesn't work. The same from the config file. Is there any other solution ??? Thanks, Nicolas Fauvel Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

19 years, 10 months

[Serusers] SER/NAT/PSTN/CISCO

by Andrea G

Hi All, I'm a very "brand new" ser user and I'm tring to set-up a SER LAB. Now, I've successfully configured my server with RTP/NAT support but, what I cannot see is how to tell SER to cut off PSTN calls coming from my SIP clients. I also have a cisco 2600 and I would like to get SER be able to perform PSTN calls using it. I've seen and old post (http://lists.iptel.org/pipermail/serusers/2004-March/006722.html) on this mailing-list and so I would like to know if somebody could help me both with SER & CISCO config. Any help is very very very appreciated! Thanks in advance! _________________________________________________________________ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/

19 years, 10 months

[Serusers] SER + syslog errors

by Darren Nay

Hey all, I have been running SER 0.8.12 for the past few months without incident. However, last night at 3am it stopped responding. I have an daemon running that checks SER once per minute to verify that it is responding, and if it stops then it restarts SER. This daemon did restart SER last night and SER started responding again .. But I would like to know the root cause of why SER stopped responding in the first place. While scanning through the syslog I see some errors that start at exactly the same time that SER stopped responding, and end after SER has been restarted. I have included a snippet from syslog below. Can anyone tell me what these errors mean, and what would cause them? Thanks for your help! Darren Nay dnay(a)ionosphere.net ----- Jan 14 03:03:12 ss1 ser[6137]: contact_parser(): Empty body Jan 14 03:03:12 ss1 ser[6137]: parse_contact(): Error while parsing Jan 14 03:03:12 ss1 ser[6137]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:12 ss1 ser[6137]: contact_parser(): Empty body Jan 14 03:03:12 ss1 ser[6137]: parse_contact(): Error while parsing Jan 14 03:03:12 ss1 ser[6137]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:12 ss1 ser[6137]: contact_parser(): Empty body Jan 14 03:03:12 ss1 ser[6137]: parse_contact(): Error while parsing Jan 14 03:03:12 ss1 ser[6137]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6126]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6126]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6126]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6126]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6126]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6126]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6126]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6126]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6126]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6117]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6117]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6117]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6117]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6117]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6117]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6117]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6117]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6117]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6148]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6148]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6148]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6148]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6148]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6148]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6148]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6148]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6148]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6144]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6144]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6120]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6120]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6144]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6120]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6144]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6120]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6150]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6144]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6120]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6150]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6144]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6145]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6134]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6150]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6144]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6145]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6134]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6120]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6150]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6144]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6149]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6123]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6134]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6120]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6109]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6144]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6149]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6145]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6146]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6134]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6120]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6109]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6137]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6149]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6145]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6146]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6123]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6134]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6120]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6109]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6137]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6150]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6149]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6145]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6146]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6123]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6134]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6109]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6137]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6150]: get_contact_uri: Error while parsing Contact body Jan 14 03:03:13 ss1 ser[6149]: parse_contact(): Error while parsing Jan 14 03:03:13 ss1 ser[6127]: contact_parser(): Empty body Jan 14 03:03:13 ss1 ser[6145]: get_contact_uri: Error while parsing Contact body

19 years, 10 months

← Newer
1
...
20
21
22
23
24
25
26
...
40
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 January 2005