sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

[Users] subst_body with nated client problem
by Oleg A Chernov 27 Dec '06

27 Dec '06

Hello everyone! My setup is as follow: for local PSTN calls UA (with G.711 and G.729) - my Openser - my Asterisk B2BUA for prepaid - PSTN gateway (G.711 codec only) for international calls UA (with G.711 and G.729) - my Openser - my Asterisk B2BUA for prepaid - ITSP gateway (G.729 codec only) B2BUA on the second leg (B2BUA - gateway) always negotiate the right codec, so no problem, but on the first leg (UA - B2BUA) it always negotiate codec that is more prefered by the client UA side. So we can get situation, when the codecs are different on the both legs. Inspired by the http://lists.iptel.org/pipermail/serusers/2006-August/030129.html I decided to normalize codec preference. Sorry for such a long introduction, at last here goes my problem. I have the following code in my openser.cfg in INVITE section # INVITE section route[3] { ... if ( route to G.711 capable gateway) { subst_body("/^m=audio(.*)RTP\/AVP(.*) 8 (.*)/m=audio\1RTP\/AVP 8 \2 \3/ig"); .... } ... } and it works like a charm for non-nated clients with real IPs. But when we should fire use_media_proxy() for a nated one client we get the problem. SDP body before our substitution (UA-Openser): v=0 o=20000 12893 12893 IN IP4 192.168.2.134 s=ATA186 Call c=IN IP4 192.168.2.134 t=0 0 m=audio 16384 RTP/AVP 0 18 8 101 a=rtpmap:0 PCMU/8000/1 a=rtpmap:18 G729/8000/1 a=fmtp:18 annexb=yes a=rtpmap:8 PCMA/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 After (Openser - B2BUA): v=0 o=20000 12893 12893 IN IP4 192.168.2.134 s=ATA186 Call c=IN IP4 217.77.208.184 t=0 0 m=audio 16384 RTP/AVP 8 0 18 101\01560136\012a=rtpmap:0 PCMU/8000/1 a=rtpmap:18 G729/8000/1 a=fmtp:18 annexb=yes a=rtpmap:8 PCMA/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 So our subst_body() rearrange codecs as expected, but use_media_proxy() (it her fault, I think) inserted the mediaproxy fixed port number 60136 between symbols with ASCII codes \015 CR and \012 LF. This behavior was accepted by stable Openser 1.1 and latest cvs 1.2. So the question is : What to do and who is guilty ? :-) -- Best regards, Oleg A. Chernov OAC4-RIPE WildPark ISP, Nikolaev, Ukraine +380512 470555 +380512 500314

2 1

[Serusers] SER server as a client
by jk 27 Dec '06

27 Dec '06

Hello List, I am working on an assignment to develop a load balancing asterisk cluster. I started with google and found out that SER+ASTERISK is the best way to do it. Here is what I am trying to do. I have a sip account / DID (18xx xxx xxxx ) from an abc company. Now the company is gateway for between my asterisk server and PSTN network. My Asterisk server registers with abc company's gateway to receive and make calls. How can I do load balancing in this case. I understand that my SER server should register with the gateway, the gateway should forward call to SER server and then the server should forward call to one of the asterisk servers. Is it possible have the SER server register with another SER or Asterisk server and act like a client to receive and make calls? Can some one please point me to some documentation or case study? Thank you, -JK

2 2

[Users] LCR db_only mode problem
by Jayesh Nambiar 26 Dec '06

26 Dec '06

Hi all, A merry christmas and a great new year to all of you. I am trying to implement LCR in my openser 1.1. My problem is that I have around 40,000 prefix patterns which i need to enter into the LCR table. When I populate my LCR table and try to start my openser it dies. I can see the following messages in my log: convert_row: No memory left convert_rows: Error while converting row #9055 convert_result: Error while converting rows store_result: Error while converting result lcr_reload_gws(): Failed to query lcr data ERROR: lcr:mod_init(): failed to reload gateways and routes init_mod(): Error while initializing module lcr The openser starts properly when I tested with 1000 rows in the LCR table but with 40,000 rows it just dies. Can anyone please help me overcome this issue. Is there any parameter available to make openser properly run with these many rows in the LCR table. I am using the LCR in db_only mode. I have not tried this in caching mode. Will the caching mode work with these many rows?? w/regards, jayesh. Send free SMS to your Friends on Mobile from your Yahoo! Messenger. Download Now! http://messenger.yahoo.com/download.php

2 1

[Serusers] Flex and Bison
by Digital Tuffy 26 Dec '06

26 Dec '06

Could anybody pls brief the use of Flex and Bison with SER. _________________________________________________________________ Christmas is drawing near and the excitement is in the air! Check out this cool photofeature on Christmas celebrations the world over http://www.msnspecials.in/photogallery/photogallery.asp?id=a200611814137906

1 0

[Users] Sending REGISTER adn INVITE--plz help
by imran ahmed 26 Dec '06

26 Dec '06

Hi Users; I am new to use openser so having some problems. I have installed openser-1.0.0.I have the task to do load test of openser through SIPp with AUTHENTICATION. I have added some users in the subscriber table of openser. Now the problem is how to set the openser.cfg so that it can response for INVITE and REGISTER request both like: The flow goes like: 1)SIPp UAC send REGISTER -------> OPENSER 2)407 Proxy Authentication required <------ OPENSER 3)SIPp send REGISTERwith credential------>OPENSER(check from subscrible tables and on the bases of that allow or disallow) hope someone help me; Thanks and Regards; Imran __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Re: [Users] OpenSer Sending CANCEL after receiving 200 OK for a INVITE
by Klaus Darilion 26 Dec '06

26 Dec '06

Hi! TAke a look at this line: Dec 20 14:47:46 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's destination set: $ds=Contact: sip:02111@xx.87.220.xx:6060, sip:02111@xx.87.220.xx:6060 The destination set include 2 destinations: sip:02111@xx.87.220.xx:6060 and sip:02111@xx.87.220.xx:6060 Thus, openser will fork the call with 2 branches (if you take a look at the message flow you will see 2 INVITEs from openser to Asterisk which are nearly identical, only the branch parameter in openser's Via header will be different.) Asterisk is buggy and does not recognize that the 2 INVITEs are different branches but think the second INVITE is a retransmission. Thus when Asterisk accepts the call (accepting on of the two branches), openser will cancel the other branch. As the second branch is identical to the first one, it will send the CANCEL to Asterisk. As Asterisk cann not handle multiple dialog it wil think this is the recently accepted call and will hang up. Conclusion: fix your openser config. Probably in your exec script (or somewhere in openser.cfg) you create a second branch which will be filled with the same URI as the first destination. regards klaus PS: please always Cc the mailing list. Md. Samiul Aftad Chowdhury wrote: > Sorry for quite a late reply... > > but i found same scenario when i am sending the call to an asterisk box. > > Here is the log you asked for: > > In following scenario: > > xx.35.32.xx <- My Openser IP which is running on 5060 port > > xx.87.220.xx:6060 <- Asterisk Box where i am forwarding the calls > which is running on 6060 port > > xx.88.13.xx <- ipphone ip > > Same thing is happening here just after receiving 200 OK Openser > generating a CANCEL. > > i am using : > > ============================================ > exec_dset("/usr/local/route"); # here route is a script which returns > a desired host port (URI) > append_branch(); > ============================================ > > to rewrite the host port. > > > Dec 20 14:47:45 openser[17368]: Invite -> > [CallerID=sip:707234121839@xx.35.32.xx] and [DialedNo=02111] > Dec 20 14:47:46 openser[17366]: Invite -> > [CallerID=sip:707234121839@xx.35.32.xx] and [DialedNo=02111] > > Dec 20 14:47:46 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > first branch: $br=sip:02111@xx.87.220.xx:6060 > Dec 20 14:47:46 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > all branches: $bR=sip:02111@xx.87.220.xx:6060 > Dec 20 14:47:46 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > destination set: $ds=Contact: sip:02111@xx.87.220.xx:6060, > sip:02111@xx.87.220.xx:6060 > Dec 20 14:47:46 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > destination uri: $du= > Dec 20 14:47:46 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > uri: $ru=sip:02111@xx.87.220.xx:6060 > > Dec 20 14:48:01 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > first branch: $br=<null> > Dec 20 14:48:01 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > all branches: $bR= > Dec 20 14:48:01 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > destination set: $ds=<null> > Dec 20 14:48:01 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > destination uri: $du= > Dec 20 14:48:01 openser[17366]: oRnbgCwOGh9EngQ1(a)xx.88.13.xx request's > uri: $ru=sip:02111@xx.87.220.xx:6060 > > > > On 12/7/06, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote: >> >> Hi! >> >> I could not find any suspect messages. I guess there is some parallel >> forking inside openser, thus, the second branch is cancelled when the >> first branch picks up. >> >> Can you add this just before t_relay(): >> >> xlog("L_INFO","$ci request's first branch: $$br=$br\n"); >> xlog("L_INFO","$ci request's all branches: $$bR=$bR\n"); >> xlog("L_INFO","$ci request's destination set: $$ds=$ds\n"); >> xlog("L_INFO","$ci request's destination uri: $$du=$du\n"); >> xlog("L_INFO","$ci request's uri: $$ru=$ru\n"); >> >> >> regards >> klaus >> -- Klaus Darilion nic.at

2 1

[Users] Merry Christmas and A Happy New Year!
by Daniel-Constantin Mierla 24 Dec '06

24 Dec '06

Hello, it was a year full of achievements and events for OpenSER. We had a major release in summer (1.1.0), and a continuous increase in features set and robustness. What was new in 1.1.0 was summarized in release news: http://www.openser.org/index.php?option=com_content&task=view&id=47&Itemid=… Since then we went though many milestones. We had the first OpenSER summit where we were able to meet many folks from the lists, have nice chats and present interesting VoIP solutions based on OpenSER. http://www.openser.org/index.php?option=com_content&task=view&id=57&Itemid=… A very important statistic is the number of new modules and features introduced in current development version after 1.1.0: - domainpolicy - policies to connect federations - imc - instant messaging conferencing - mi_fifo and mi_xmlrpc - FIFO and XMLRPC transports for the new management interface (MI) - perl - embed perl programming in configuration file - presence - SIMPLE Presence Server implementation - pua, pua_mi, pua_usrloc - presence user agent client implementations for user location records and management interface - seas - connector to SIP Application Server - WeSIP - Java SIP Servlet Application Server (http://www.wesip.eu) - snmpstats - SNMP (Simple Network Management Interface) interface to OpenSER statistics - sst - SIP session timer support - xmpp - transparent SIP-XMPP gateway Documentation and news about all these: http://www.openser.org/docs/modules/1.2.x/ http://www.openser.org/index.php?option=com_content&task=blogsection&id=2&I… A lot of other significant improvements and addons were included in existing code (management interface, fetch database support, postgres, usrloc, dialog, enum, acc modules polishing), openser web administrator was developed. There is not very long time to the next release, along with few pending new features, the next period will be allocated to core components like timers, dns and configuration file flexibility. By end of January we should approach a new testing phase. This year the OpenSER community collaboration exploded, dokuwiki has lot of content, many tutorials were submitted, new developers and many modules sponsored by companies, mailing lists and web forum are places to get reliable information about OpenSER... We want to thank to all of you (developers, contributors with patches, tools and documentation, testers and OpenSER users) for supporting the project. 2006 was a very good year for OpenSER and 2007 looks very challenging. We wish you Merry Christmas and a very Happy New Year!

2 1

[Serusers] Service Empty
by raj gopal 23 Dec '06

23 Dec '06

Hi All, I am trying presence snapshot SER. I am getting 0(4189) Empty service! 0(4189) ERROR: rls_handler.c:484: XCAP query problems 0(4189) XCAP query failed error for SUBSCRIBE request. I am following presence handbook. Whats worng i am doing????? Can anyone help me?? Thanks in advance Venkat

1 0

[Serusers] Re: [asterisk-users] Happy X-mas
by Arun Kumar 23 Dec '06

23 Dec '06

Hi All, Wish you a very HAPPY and Merry Christmas to all and your beloved once. Arun On 12/23/06, Josué Conti <josueconti(a)gmail.com> wrote: > > Hi ALL, > > ** I like very to desire you and your family, a Merry Christmas, with much > love, peace, professional and personal success. > > Best Regards > Josue > > > 2006/12/23, raviprakash sunkara <sunkara.raviprakash.feb14(a)gmail.com>: > > > > > > Hello > > * * * * * * * * > > * * * * * Happy X-mas and Adv Happy New Year ....... > > ************************************ > > **** > > **** > > ******** > > ** > > > > ************* > > > > > > -- > > Thanks and Regards > > Ravi Prakash Sunkara > > ravi.sunkara(a)hyperion-tech.com > > M:+91 9985077535 > > O:+91 40 23114549 > > F:+91 40 40208727 > > ravi.sunkara(a)hyperion-tech.com > > www.hyperion-tech.com > > _______________________________________________ > > --Bandwidth and Colocation provided by Easynews.com<http://easynews.com/>-- > > > > asterisk-users mailing list > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > > > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > >

1 0

[Users] Happy X-mas
by raviprakash sunkara 23 Dec '06

23 Dec '06

Hello * * * * * * * * * * * * * Happy X-mas and Adv Happy New Year ....... ************************************ **** **** ******** ** ************* -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 O:+91 40 23114549 F:+91 40 40208727 ravi.sunkara(a)hyperion-tech.com www.hyperion-tech.com

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users