June 2012 - sr-users - kamailio.org

Re: [SR-Users] Kamailio Unexpectedly Terminating
by Nathaniel L. Keeling III 12 Jun '12

12 Jun '12

Yes, This is a 64bit system T-Mobile. America’s First Nationwide 4G Network Jason Penton <jason.penton(a)smilecoms.com> wrote: >from the logs he has sent the mem addresses all look 64 bit. Sparc AFAIK is >only 64 bit anyway > >Cheers >Jason > >On Tue, Jun 12, 2012 at 8:50 AM, Daniel-Constantin Mierla <miconda(a)gmail.com >> wrote: > >> Hello, >> >> is it 64bit architecture? >> >> Cheers, >> Daniel >> >> >> On 6/11/12 9:12 PM, Akan wrote: >> >>> Here is the information requested: >>> >>> System = SunOS >>> Node = -f >>> Release = 5.10 >>> KernelID = Generic_141444-09 >>> Machine = sun4u >>> BusType = <unknown> >>> Serial = <unknown> >>> Users = <unknown> >>> OEM# = 0 >>> Origin# = 1 >>> NumCPU = 1 >>> >>> One machine is a Sun Fire V120, 2g memory, UltraSPARC-IIe 650MHz, >>> UltraAX-i2 >>> The other machine is a Sun Netra T1 200, 1g memory, UltraSparc-IIe >>> 500MHz, UltraAX-i2 >>> >>> Thanks >>> >>> Nathaniel L Keeling >>> >>> >>> >>> On 6/11/2012 8:33 AM, Daniel-Constantin Mierla wrote: >>> >>>> Hello, >>>> >>>> I committed a patch that should make it work when realm_prefix is not >>>> set for registrar module: >>>> >>>> http://git.sip-router.org/cgi-**bin/gitweb.cgi/sip-router/?a=**commit;h= >>>> **d42379da90f2ec87cb5dbb00ebb563**c7528ec910<http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=d42379d…> >>>> >>>> For the moment I have no idea why SIGBUS is triggered, i tried to access >>>> the structure directly, not via defines, and there is still a problem when >>>> realm_prefix is set. It's ok accessing the .len field but not .s of the >>>> same structure. The field .s is the first, making me think it's not >>>> alignment issue, or it is something very specific to this system. >>>> >>>> Overall, I am not familiar with sparc/solaris systems, maybe if you send >>>> here full details about OS version, architecture and CPU type, others using >>>> similar systems can give hints. >>>> >>>> Jason reported that on solaris with x86, this problem was not >>>> encountered. >>>> >>>> Cheers, >>>> Daniel >>>> >>>> On 6/4/12 8:57 AM, Daniel-Constantin Mierla wrote: >>>> >>>>> Hello, >>>>> >>>>> still strange with the crash on that if condition. One of your previous >>>>> reports showed a different line, when assigning a pointer. Also, I kind of >>>>> understood that save() was ok, but lookup() not. Is not the case anymore as >>>>> the backtrace shows. >>>>> >>>>> SIGBUS can occur because of alignment in memory which is thrown in >>>>> solaris, does not happen in linux flavours. I am thinking of putting the >>>>> prefix field first so the access to it is at beginning of the straucture, >>>>> just to see if that is the problem, although is should not be. >>>>> >>>>> I will add a patch soon, otherwise I am out of ideas for the moment >>>>> with the SIGBUS, I would need access to the machine to do some testing by >>>>> myself. >>>>> >>>>> Cheers, >>>>> Daniel >>>>> >>>>> On 6/2/12 10:36 PM, Akan wrote: >>>>> >>>>>> Ok, I reloaded the servers with v3.2 from git without performing the >>>>>> checkout and with just the master branch. Reran my tests on 2 servers and >>>>>> Kamailio terminated with a core dump. I have included the full trace of one >>>>>> of the servers. The other trace has the same results. >>>>>> >>>>>> Thanks >>>>>> >>>>>> Nathaniel >>>>>> >>>>>> On 5/30/2012 2:25 PM, Daniel-Constantin Mierla wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> On 5/30/12 9:10 PM, Akan wrote: >>>>>>> >>>>>>>> This was a re-pull from the git master. I had deleted all of the old >>>>>>>> files and issued these commands: >>>>>>>> >>>>>>>> git clone --depth 1 git://git.sip-router.org/sip-**router<http://git.sip-router.org/sip-router>kamailio >>>>>>>> cd kamailio >>>>>>>> git checkout -b 3.2 origin/3.2 >>>>>>>> >>>>>>>> This is the source that I got. Could this be a problem within git? >>>>>>>> >>>>>>> do not checkout branch 3.2, just try with the master branch, as said, >>>>>>> not all patches are backported to stable 3.2. >>>>>>> >>>>>>> For sake of completeness, here are some guidelines: >>>>>>> http://www.kamailio.org/wiki/**install/devel/git<http://www.kamailio.org/wiki/install/devel/git> >>>>>>> >>>>>>> Cheers, >>>>>>> Daniel >>>>>>> >>>>>>> >>>>>> >>>>>> ______________________________**_________________ >>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>>>>> sr-users(a)lists.sip-router.org >>>>>> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> >>>>>> >>>>> >>>>> -- >>>>> Daniel-Constantin Mierla -http://www.asipto.com >>>>> http://twitter.com/#!/miconda -http://www.linkedin.com/in/**miconda<http://www.linkedin.com/in/miconda> >>>>> Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - >>>>> http://asipto.com/u/katu >>>>> Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - >>>>> http://asipto.com/u/kpw >>>>> >>>>> >>>>> >>>> -- >>>> Daniel-Constantin Mierla -http://www.asipto.com >>>> http://twitter.com/#!/miconda -http://www.linkedin.com/in/**miconda<http://www.linkedin.com/in/miconda> >>>> Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - >>>> http://asipto.com/u/katu >>>> Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - >>>> http://asipto.com/u/kpw >>>> >>>> >>>> No virus found in this message. >>>> Checked by AVG - www.avg.com <http://www.avg.com> >>>> Version: 2012.0.2178 / Virus Database: 2433/5061 - Release Date: 06/10/12 >>>> >>>> >>> >>> >>> ______________________________**_________________ >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>> sr-users(a)lists.sip-router.org >>> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> >>> >> >> -- >> Daniel-Constantin Mierla - http://www.asipto.com >> http://twitter.com/#!/miconda - http://www.linkedin.com/in/**miconda<http://www.linkedin.com/in/miconda> >> Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - >> http://asipto.com/u/katu >> >> Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - >> http://asipto.com/u/kpw >> >> >> >> >> ______________________________**_________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> sr-users(a)lists.sip-router.org >> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> >> > >This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at http://www.smilecoms.com/disclaimer > >_______________________________________________ >SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >sr-users(a)lists.sip-router.org >http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 0

High availability design with Kamailio
by Reinhard, Carel (GD) 12 Jun '12

12 Jun '12

Dear all, hope to get some information from you guys! For a redundant service we have to build up SIP proxy/registrar server in a high available scenario. Therefore, we will have 2 SIP proxy/registrar on two completely independent servers. They should be SIP dialog stateful and replicate all the session/call states between each other. If one server fails, the other should have all the SIP dialog information for call handling and accounting. How can this done in a stable and reliable way? Is this feature mature enough to support enterprise requirements? The only information I have is to build it up with the DISPATCHER module, but it seems more to be a stateless load-balancer instead of a HA module. Who has experience with HA failover designs with Kamailio and can give me some hints? Thank you very much in advance Kind regards Carel Carel Reinhard Security and VoIP Engineer SRG SSR Switzerland Telefon direkt +41 31 350 94 07 Carel.Reinhard(a)srgssr.ch<mailto:Carel.Reinhard@srgssr.ch>

5 10

Shared memory fragmentation
by Morten Isaksen 12 Jun '12

12 Jun '12

Hi, We have 2 Kamailio 3.0.3 servers that has been running with carrierroute for about 2 years without any problems. They have 128 MB shared memory and modparam("carrierroute", "config_source", "db") modparam("carrierroute", "db_url", "<DBURL>") modparam("carrierroute", "fetch_rows", 500) The carrierroute table is about 91K lines and have been growing slowly. Suddenly we get this ERROR: carrierroute [cr_data.c:585]: could not allocate shared memory from available pool after a few "kamctl cr reload". I increased the shared memory to 256 MB but with the same result. I have now increased it to 512 MB and it seems to work better now. I have noticed this. After a restart the shmem counters is like this: shmem:total_size = 536870912 shmem:used_size = 28486752 shmem:real_used_size = 40147128 shmem:max_used_size = 41135424 shmem:free_size = 496723784 shmem:fragments = 555 And after the first "kamctl cr reload" it is like this: shmem:total_size = 536870912 shmem:used_size = 28619016 shmem:real_used_size = 51842768 shmem:max_used_size = 76993616 shmem:free_size = 485028144 shmem:fragments = 722063 Notice the increase in fragments. Sequentials "kamctl cr reload" does not change the fragments allot. Any ideas? -- Morten Isaksen

3 4

maddr parameter in contact header and fix_nated_contact
by Morten Isaksen 12 Jun '12

12 Jun '12

Hi, I have this setup: Mediation server with internal ip -- NAT firewall -- Kamailio proxy -- PSTN gateway The mediation server sends a contact header with maddr=<internal IP> fix_nated_contact only changes the host part and leaves the maddr intact. When the PSTN gateway sends a PRACK or a BYE it puts the <internal IP> in the RURI, and kamailio then try to forward the message directly to the <internal IP> and not the NAT ip. >From RFC 3261 19.1.1: The maddr parameter indicates the server address to be contacted for this user, overriding any address derived from the host field. When an maddr parameter is present, the port and transport components of the URI apply to the address indicated in the maddr parameter value. [4] describes the proper interpretation of the transport, maddr, and hostport in order to obtain the destination address, port, and transport for sending a request. I can see that OpenSIPS has fixed this. http://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3312423&group_… Would it be possible to get this patch into Kamailio also? -- Morten Isaksen

2 5

Install Kamailio v3.3.x from GIT
by Daniel-Constantin Mierla 12 Jun '12

12 Jun '12

Hello, now that the branch 3.3 is available, I created the tutorial about how to install Kamailio v3.3.x from GIT: * http://www.kamailio.org/wiki/install/3.3.x/git Feedback and improvements are welcome! Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw

1 0

git branch 3.3 created
by Daniel-Constantin Mierla 11 Jun '12

11 Jun '12

Hello, GIT branch 3.3 was created to hold the release series 3.3.x -- version 3.3.0 will be out in max. 1 week, a decision after collecting eventual issues still open to be reported today. Here are few details about how to use it. Download and use branch 3.3 from git: git clone --depth 1 git://git.sip-router.org/sip-router kamailio cd kamailio git checkout -b 3.3 origin/3.3 Pushing patches: - only bug fixes or documentation improvements have to be committed to branch 3.3 - first commit to master branch (if the bug applies there as well), cherry-pick the commit to branch 3.3 and push to remote repository Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw

1 0

development for future version 3.4.0 is open
by Daniel-Constantin Mierla 11 Jun '12

11 Jun '12

Hello, short note to let everyone know that new features can be committed again to the master branch -- they will be part of future version 3.4.0 (if no other numbering release will be decided). Testing phase of version 3.3.0 within master is ended, a dedicated branch being created for it (details in a separate message). Happy coding, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw

1 0

Capturing a users call (SIP+RTP+T.38)
by Klaus Darilion 11 Jun '12

11 Jun '12

Hi all! Do you know any comfortable tools to filter out a certain users call? e.g. searching in SIP packets for the user pattern, get the media port out of SDP and capture also RTP+T.38 I found pcapsipdump but have not tried it yet. Any suggestions or do I have to write my own tool? thanks Klaus

4 6

branching 3.3 - to be used for 3.3.x releases
by Daniel-Constantin Mierla 11 Jun '12

11 Jun '12

Hello, I am going to create the GIT branch 3.3 in short time -- this branch will be used for releasing 3.3.x versions. After that master can take again commits of new features, to be part of next major release 3.4.x. Branch 3.3 will take only fixes. From my point of view, I have two issues that I am trying to solve and the 3.3.0 is ready to go out, namely: - a solaris sigbus - pua_dialoginfo issue reported on mailing list Otherwise, nothing else critcal is out there, to my knowledge. Report them if you have other ones. Packaging specs were updated, so we are pretty much ready to release when no relevant issues is open. The wiki page with what is new in this release was updated a bit as well, add if you find something missing at: - http://www.kamailio.org/wiki/features/new-in-devel Also, contribute to the upgrade guidelines: - http://www.kamailio.org/wiki/install/upgrade/3.2.x-to-3.3.0 Cheer, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw

2 2

About kamailio 3.3 msrp module and sylkserver
by Min Wang 11 Jun '12

11 Jun '12

Hi I am wondering what are the major differences between kamailio 3.3 msrp module and sylkserver (http://sylkserver.com/features.phtml ) ? thanks. min

2 2