I answer to myself (it may help others) as I could test successfully the
configuration below. Also there is a typo (isbflagset instead of isflagset):
so when I detect a UA is behind NAT, I do:
if (nat_uac_test("19")) {
if (method=="REGISTER") {
setbflag(7);
fix_nated_register();
...
Then when my B2BUA sends invite to this UA I do (after lookup("location") ):
lookup("location");
...
if (is_method("INVITE")) {
if (isbflagset(7)) {
setflag(5);
Regards,
Pascal
On Mon, Jul 13, 2009 at 2:43 PM, Pascal Maugeri <pascal.maugeri(a)gmail.com>wrote:
> I'm not that familiar with flag management.
>
> so when I detect a UA is behind NAT, I do:
>
> if (nat_uac_test("19")) {
> if (method=="REGISTER") {
> setbflag(7);
> fix_nated_register();
> ...
>
> Then when my B2BUA sends invite to this UA I do (after lookup("location")
> ):
>
> if (is_method("INVITE")) {
> if (isflagset(7)) {
> setflag(5);
>
> Is that correct ?
>
> BTW, regarding the flag number, is there a table of reserved numbers ? Can
> I use "7" in this case ?
>
> -pascal
>
>
>
>
> On Mon, Jul 13, 2009 at 12:00 PM, Daniel-Constantin Mierla <
> miconda(a)gmail.com> wrote:
>
>> Hello,
>>
>> On 07/13/2009 11:54 AM, Pascal Maugeri wrote:
>>
>>> Hi
>>>
>>> A quick question, when I apply a fix_nated_register() to a remote user
>>> when he/she registers, how can I know later on if this user is behind NAT ?
>>>
>> set a branch flag for REGISTER before save location. After lookup location
>> that flag is recovered and you can test it in the config file.
>>
>> Cheers,
>> Daniel
>>
>>
>>> All my calls go through a B2BUA:
>>>
>>> Caller ------> kamailio/rtpproxy ------> B2BUA ------> kamailio/rtpproxy
>>> ------> Callee
>>>
>>> When my B2BUA calls a user, I want to know if this user is behind NAT or
>>> not. For now all the calls go through rtpproxy but I would like to apply
>>> this path only when user is behind NAT.
>>>
>>> Regards,
>>> Pascal
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Kamailio (OpenSER) - Users mailing list
>>> Users(a)lists.kamailio.org
>>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
>>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
>>>
>>
>> --
>> Daniel-Constantin Mierla
>> http://www.asipto.com/
>>
>>
>
Hello Marco,
On 13.07.2009 14:28 Uhr, Marco Bungalski wrote:
> Hello, Daniel,
>
> i know how to compile, but where to download the version with the bugfix
> included?
>
if you fetch from svn the branch 1.5 then it has the fix. Here is a
short description of how the versioning was done so far for kamilio
(openser) from svn:
- when a major version is released, a branch with the first two numbers
in the version is created (e.g., 1.5)
- for each minor version (including the .0 - corresponding to the major
version) a tag is created with name of the three numbers in version
- any fix for the major version is committed in the branch. Once a new
minor release is out, a new tag is created. Therefore, the branch has
all the time the most updated code for a specific major release. The
tags are snapshots at the time of release.
For the case of 1.5.x series:
- there is one branch 1.5
- now there are two tags on svn: 1.5.0 and 1.5.1, soon there will be 1.5.2.
- the tarballs are created from a svn checkout done as exampled in the
wiki page I sent to you.
probably reading a bit about svn (subversion) will help you. Anyhow,
next major version will use GIT.
Now, just to download the latest 1.5.x version, do:
svn co http://openser.svn.sourceforge.net/svnroot/openser/branches/1.5
kamailio-1.5
You need subversion package installed. The continue installation as you
do with the tarball.
Cheers,
Daniel
> Hello,
>
> this one should help you:
> http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-1.5.x-from-svn
>
> Cheers,
> Daniel
>
> On 07/13/2009 01:30 PM, Marco Bungalski wrote:
>
>> Hello,
>>
>> i am sorry to say that i've not testet it because i don't know where to
>> download the fix and how to implementate that :-(
>>
>> But if you give me a link i will test it today (i can simulate the bug)
>>
> and
>
>> will send you a feedback.
>>
>> Greetings,
>>
>> Marco
>>
>>
>>
>>
>> Mit freundlichen Grüßen
>>
>> Marco Bungalski
>>
>>
>> Marco Bungalski GmbH
>> Traversale 5
>> 27283 Verden
>>
>> Telefon: +49 4231 - 776 9999
>> Fax: +49 4231 - 776 9998
>> Mobil: +49 172 4204774
>>
>> e-mail: Marco(a)Bungalski.de
>> web: www.bungalski.de
>>
>> Geschäftsführender Gesellschafter: Marco Bungalski
>> Sitz der Gesellschaft: D-27283 Verden, AG Walsrode HRB 120586
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
>> Gesendet: Montag, 13. Juli 2009 12:32
>> An: Marco Bungalski
>> Cc: users(a)lists.kamailio.org
>> Betreff: Re: [Kamailio-Users] preparing kamailio 1.5.2
>>
>> Hello
>>
>> On 07/13/2009 12:28 PM, Marco Bungalski wrote:
>>
>>
>>> Hello, Daniel!
>>>
>>>
>>>
>>> Will the bug "Kamailio crashes when receiving an empty
>>> Record-Route-field with using the dialog-module" be fixed in 1.5.2?
>>>
>>>
>>>
>>> If yes: Thanks for that :-)
>>>
>>>
>>>
>> it should be already in the svn (therefore yes). Have you tested it?
>>
>> Cheers,
>> Daniel
>>
>>
>>
>
>
Hello,
this one should help you:
http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-1.5.x-from-svn
Cheers,
Daniel
On 07/13/2009 01:30 PM, Marco Bungalski wrote:
> Hello,
>
> i am sorry to say that i've not testet it because i don't know where to
> download the fix and how to implementate that :-(
>
> But if you give me a link i will test it today (i can simulate the bug) and
> will send you a feedback.
>
> Greetings,
>
> Marco
>
>
>
>
> Mit freundlichen Grüßen
>
> Marco Bungalski
>
>
> Marco Bungalski GmbH
> Traversale 5
> 27283 Verden
>
> Telefon: +49 4231 - 776 9999
> Fax: +49 4231 - 776 9998
> Mobil: +49 172 4204774
>
> e-mail: Marco(a)Bungalski.de
> web: www.bungalski.de
>
> Geschäftsführender Gesellschafter: Marco Bungalski
> Sitz der Gesellschaft: D-27283 Verden, AG Walsrode HRB 120586
>
> -----Ursprüngliche Nachricht-----
> Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
> Gesendet: Montag, 13. Juli 2009 12:32
> An: Marco Bungalski
> Cc: users(a)lists.kamailio.org
> Betreff: Re: [Kamailio-Users] preparing kamailio 1.5.2
>
> Hello
>
> On 07/13/2009 12:28 PM, Marco Bungalski wrote:
>
>> Hello, Daniel!
>>
>>
>>
>> Will the bug "Kamailio crashes when receiving an empty
>> Record-Route-field with using the dialog-module" be fixed in 1.5.2?
>>
>>
>>
>> If yes: Thanks for that :-)
>>
>>
> it should be already in the svn (therefore yes). Have you tested it?
>
> Cheers,
> Daniel
>
>
--
Daniel-Constantin Mierla
http://www.asipto.com/
Hello, Daniel!
Will the bug "Kamailio crashes when receiving an empty Record-Route-field
with using the dialog-module" be fixed in 1.5.2?
If yes: Thanks for that :-)
Greetings,
Marco
Hello,
the roadmap to next major release of Kamailio, codenamed 3.0, was
sketched during last week IRC meeting as:
- freezing in 1-1.5 months
- 1-1.5 months testing
- release by end of September/ beginning of October
Right now, current development state is:
- all but one module (seas) were updated to work with the new core
- several addons in kamailio core and tm still to be included in GIT
master branch
- many new features developed: mecached, event_route, xml doc handling
... see:
http://sip-router.org/wiki/features/new-in-devel
I invite all of you to test, startup guidelines at:
http://sip-router.org/wiki/migration/kamailio-3.0-config
Any feedback is very much appreciated, thanks,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
Hi
A quick question, when I apply a fix_nated_register() to a remote user when
he/she registers, how can I know later on if this user is behind NAT ?
All my calls go through a B2BUA:
Caller ------> kamailio/rtpproxy ------> B2BUA ------> kamailio/rtpproxy
------> Callee
When my B2BUA calls a user, I want to know if this user is behind NAT or
not. For now all the calls go through rtpproxy but I would like to apply
this path only when user is behind NAT.
Regards,
Pascal
Hello,
last week during the IRC meeting it was proposed to release kamailio
1.5.2 tomorrow. If anyone of you is aware of some show stopper, please
reply.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
Hello,
two of the last three modules that were not ported to use the new sip
router core are ready now: nat_traversal and siptrace.
Particularly, siptrace was refurbished, should catch now forwarded ACK.
Before release, there are couple of new features that should get in
trunk since sip route core offers support for such extensions:
- ability to filter the ACK for negative replies issued by sl module in
the script
- ability to store stateless forwarded messages (now only stateful ones
being stored)
Testing is very much appreciated.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
Good day everyone.
As I am new to kamailio, I would like to ask help on the CFG file. I have successfully installed kamailio 1.4.1 but having problems to set it up on my desired functionality.
Below is what i want to achieve.
All sip clients (asterisk box, sip enabled box, pbx) should pass sip calls to my kamailio server. Clients connections to my Kamailio are via IP to IP.
From my kamailio server i should be able to route them on my carrier, USA carrier and International Carrier. Connections to carrier is via IP to IP.
I have set up Kamailio to support MYSQL authentication, its just that i have having problems to put my idea on the kamailio.cfg.
Any sample working configurations similar to want I want to achieve is greatly appreciated.
Thank you in advance for any support.
Dennis Cristobal.
jtom25(a)yahoo.com
Feel safer online. Upgrade to the new, safer Internet Explorer 8 optimized for Yahoo! to put your mind at peace. It's free. Get IE8 here! http://downloads.yahoo.com/sg/internetexplorer/
Hi
I recently read the following in order to optimize OpenSER in handling
TCP connections:
"First, the TCP supervisor process must be given an elevated priority
level in order to prevent anomalous behavior due to the Linux
scheduler."
First of all, as this is quite old paper (it refers to OpenSER 1.2),
I'm wondering if such a tuning is still needed for Kamailio 1.5 branch
? If yes, how can I do this ?
Regards,
Pascal