date:20161201

[SR-Users] Dual Stack Environments

2016-12-01 Thread Colin Morelli

Hey all,

Sorry for two questions out at the same time!

I'm using kamailio in front of FS, and I'm about to enable IPv6, but I have
a question that I'm not entirely clear on.

What's the proper way to forward traffic using the same interface that it
came in on? Specifically, if a client connects to kamailio on IPv6, it
should connect to FS on IPv6, so that FS knows to advertise its v6 address
in the SDP. The same should be true for v4.

Is this possible?

Best,
Colin
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code

2016-12-01 Thread Juha Heinanen

Brandon Armstead writes:

> +1 - I'm all for cleaning up any technical debt and moving on with more
> normalized concept.

I'm also in favor of getting rid on MI interface. I'm myself relying
only on one MI command (pua_publish) for which an RPC command does not
exist (or did not exist last time when I checked).

Some years ago I tried to implement RPC version of pua_publish, but was
not able to get the call back working correctly.  I also sent some
messages including a piece of code to the dev list, but it was a dead
end then.

Very nice if pua.publish would see a day of light again.

-- Juha

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Limiting Registration Contacts

2016-12-01 Thread Alex Balashov

Wouldn't it be more fruitful to delete and reach old bindings in such a 
scenario? Or are these bindings not only for web clients? 

On December 1, 2016 5:54:06 PM EST, Colin Morelli  
wrote:
>Hey all,
>
>I know Kamailio's registrar module has a max_contacts parameter that
>will
>limit the number of active contacts for an AOR. However, is there any
>mechanism to control what happens when that number is hit?
>
>When using a web client where every page refresh registers a new
>contact
>with Kamailio, it would be useful to automatically roll off the oldest
>registrations and replace to make room for the new ones. I know this
>can be
>manually accomplished with sqlops, but I was hoping something like this
>already existed.
>
>Best,
>Colin
>
>
>
>
>___
>SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>sr-users@lists.sip-router.org
>http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


-- Alex

--
Principal, Evariste Systems LLC (www.evaristesys.com)

Sent from my Google Nexus.


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

2016-12-01 Thread Jonathan Hunter

Hi Daniel,

I am trying tm.t_uac_start and its stating Content-Type Missing, I have tried 
to add to params but it doesnt like it, where should it be defined?

Command below;


jsonrpc_exec('{"jsonrpc":"2.0","method":"tm.t_uac_start","params": ["INFO", 
"$dlg(to_uri)",".",".","From:$var(testjon)\r\n","To:$var(testjon2)\r\n","Contact:$var(testjon4)\r\n","Content-Type:
 application/json\r\n","Content-Length: 0\r\n"]}');

And logs;

Dec  1 16:09:15 POC_ProxyA /usr/sbin/kamailio[11883]: INFO:

Re: [SR-Users] VERY IMPORTANT: deciding when to remove the MI code

2016-12-01 Thread Brandon Armstead

+1 - I'm all for cleaning up any technical debt and moving on with more
normalized concept.

:)

Sincerely,
Brandon Armstead

On Thu, Dec 1, 2016 at 6:17 AM Daniel-Constantin Mierla 
wrote:

> Hello,
>
> we started discussing about removing MI (so called management interface)
> for very long time, more or less since 2008. The RPC should remain the
> control interface, given its better structure for commands, parameters,
> etc ... MI is custom protocol using a line-oriented communication via
> fifo or socket file with kamailio (e.g., implemented mi_fifo and
> mi_datagram modules). RPC is the alternative, a more standardized
> concept, with better structured format.
>
> I think it's time to set a clear roadmap for doing the removal. Overall,
> it will be easier to maintain the code, right now being duplicated code
> for doing the same operation over MI or RPC, and MI shows its
> limitations (or complexity to deal with) for advanced needs (see the
> discussions about how to provide multi-line value parameters over MI).
>
> So, I want to know if there are many relying on MI directly and they
> still want to keep it, what would be the expected duration they need for
> upgrading their tools to work with RPC interface, other relevant aspects
> people have in favour of mi vs rpc.
>
> I am even willing to do the removal in time befire freezing the 5.0
> branch. We will ensure a clean start of 5.x series.
>
> The main concern from my point of view is kamctl -- but I think we can
> preserve the compatibility for kamctl commands and parameters (so
> command line execution of kamctl will be the same), but the output might
> be different. That's because it should be easy to updated it to
> communicate with jsonrpc-s module, but then it will get json-formatted
> results.
>
> To summarize, two big questions to answer:
>
> a) Are you ok to remove the MI code/commands?
>
> b) If yes to a), are you ok to be done for v5.0?
>
> Not providing feedback will be considered as 'yes' for both questions,
> so **speak up if you want MI to be kept or delay it removal**.
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla
> www.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
-- 
Sent from Gmail Mobile
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] VERY IMPORTANT: deciding when to remove the MI code

2016-12-01 Thread Daniel-Constantin Mierla

Hello,

we started discussing about removing MI (so called management interface)
for very long time, more or less since 2008. The RPC should remain the
control interface, given its better structure for commands, parameters,
etc ... MI is custom protocol using a line-oriented communication via
fifo or socket file with kamailio (e.g., implemented mi_fifo and
mi_datagram modules). RPC is the alternative, a more standardized
concept, with better structured format.

I think it's time to set a clear roadmap for doing the removal. Overall,
it will be easier to maintain the code, right now being duplicated code
for doing the same operation over MI or RPC, and MI shows its
limitations (or complexity to deal with) for advanced needs (see the
discussions about how to provide multi-line value parameters over MI).

So, I want to know if there are many relying on MI directly and they
still want to keep it, what would be the expected duration they need for
upgrading their tools to work with RPC interface, other relevant aspects
people have in favour of mi vs rpc.

I am even willing to do the removal in time befire freezing the 5.0
branch. We will ensure a clean start of 5.x series.

The main concern from my point of view is kamctl -- but I think we can
preserve the compatibility for kamctl commands and parameters (so
command line execution of kamctl will be the same), but the output might
be different. That's because it should be easy to updated it to
communicate with jsonrpc-s module, but then it will get json-formatted
results.

To summarize, two big questions to answer:

a) Are you ok to remove the MI code/commands?

b) If yes to a), are you ok to be done for v5.0?

Not providing feedback will be considered as 'yes' for both questions,
so **speak up if you want MI to be kept or delay it removal**.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

2016-12-01 Thread Jonathan Hunter

Hello,

Ok cool I will look at it, will it help with syntax issues I have seen with the 
double quotes so far?

Many thanks

Jon

Get Outlook for iOS




On Thu, Dec 1, 2016 at 12:31 PM +, "Daniel-Constantin Mierla" 
> wrote:


Hello,

tm.t_uac_start is another rpc command than what was tried before, this one 
doesn't do async operation.

Cheers,
Daniel

On 01/12/2016 13:28, Jonathan Hunter wrote:

Hello,


I am currently still using the exec module, so within the .cfg file, as when 
using jsonrpc-s its coming up with the async command issue again, I presume 
this will still be the case?


Ok I will try with the combinations you mention.


Many thanks


Jon



From: Daniel-Constantin Mierla 
Sent: 01 December 2016 12:24
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using 
$uac_req(method)="INFO"


Hello,


are you still trying with MI command via kamctl? Not with the jsonrpc-s module 
and tm.t_uac_start?


When double quotes disappear is likely due to command line interpreter, so you 
need to put two of them for each one you have now, then ones than need to stay 
should be with more backslashes.


Also, you can try to use single quotes to enclose the parameter values and let 
the double quotes in the content of the parameter.


Cheers,
Daniel

On 30/11/2016 15:38, Jonathan Hunter wrote:
Hi,

I am just testing with the mi t_uac_dlg command, and I am trying to create an 
additional header, which is sent in the SIP INFO message and actually contains 
double quotes.

So in my kamailio.cfg script file I set the variable;


$var(testjon8) = "p1=\"STOP\"";

xlog("L_INFO","We are going to try and use $var(testjon8)\n");

And when seeing in the logs I see it states;

We are going to try and use p1="STOP"

And p1="STOP" is exactly what I want.

However when I generate the SIP INFO message, and check on the wire using 
wireshark I see;

Event:p1=STOP

So it doesnt have the double quotes I would like.

How can I escape them so the t_uac_dlg command includes them?

The portion where this header is generated in the command is;


exec_avp("kamctl mi t_uac_dlg INFO $dlg(to_uri) . . 
\\\"From:'$var(testjon)'\"\\r\\nTo:$var(testjon2)\\r\\nCall-ID:$var(testjon3)\\r\\nAllow:$var(Allow)\\r\\nContact:$var(testjon4)\\r\\nEvent:$var(testjon8)\\r\\n\\\"\"",
 "$avp(test)");



And also running debug I see it as Event:p1="STOP"\r\n\""


Can you tell me how I can escape " so its actually within the SIP header itself?

Many thanks

Jon




From: sr-users 

 on behalf of Jonathan Hunter 

Sent: 25 November 2016 18:55
To: Kamailio SER - Users Mailing List; 
mico...@gmail.com
Subject: Re: [SR-Users] Send SIP Info within a dialog using 
$uac_req(method)="INFO"


Hi Daniel,


Great thanks very much, will give it a try.


Jon



From: Daniel-Constantin Mierla 
Sent: 22 November 2016 18:46
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using 
$uac_req(method)="INFO"


Hello,


got a bit of time to look at the code and discovered that there is a rpc 
command tm.t_uac_start added by ser guys that might get you moving forward. It 
is not waiting for the reply of the generated request and you can use it with 
json rpc exec function in the config, so it avoids using exec.


Can you give it a try?


Some documentation can be found in the comments of the function used by this 
command:

  - https://github.com/kamailio/kamailio/blob/master/modules/tm/rpc_uac.c#L399

Cheers,
Daniel


On 22/11/2016 18:35, Jonathan Hunter wrote:

Hi Daniel,


Thanks here you go;


[root@POC_ProxyA kamailio]# kamctl mi t_uac_dlg INFO sip:3003@193.144.1.112 . 
udp:10.70.1.136:5060
\"From:sip:1234@8.8.8.8"\r\nTo:sip:3003@193.144.1.112\r\nContact:sip:daemon@8.8.8.8\r\n\""
404 Invalid local socket
[root@POC_ProxyA kamailio]# VERBOSE=1 kamctl mi t_uac_dlg INFO 
sip:3003@193.144.1.112 . udp:10.70.1.136:5060
\"From:sip:1234@8.8.8.8"\r\nTo:sip:3003@193.144.1.112\r\nContact:sip:daemon@8.8.8.8\r\n\""
database engine 'MYSQL' loaded
Control engine 'FIFO' loaded
entering fifo_cmd t_uac_dlg INFO sip:3003@193.144.1.112 . udp:10.70.1.136:5060 
"From:sip:1234@8.8.8.8
To:sip:3003@193.144.1.112
Contact:sip:daemon@8.8.8.8
"
404 Invalid local socket
FIFO command was:
:t_uac_dlg:kamailio_receiver_23469
INFO
sip:3003@193.144.1.112
.
udp:10.70.1.136:5060
"From:sip:1234@8.8.8.8
To:sip:3003@193.144.1.112

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

2016-12-01 Thread Mikko Lehto

Daniel-Constantin Mierla :

> The specs require to be \r\n. Accepting only \n is and
> SER-time-propagated extension in Kamailio from the early days of the
> project when a lot of tests during the development was done by building
> messages inside a text file and injecting it into the network. When a
> response is built by kamailio, the needed headers from request that are
> not changed are just copied. Everything else will get the standard \r\n.
> 
> So this is due to that flexibility and I think we are fine with this
> behaviour given it happens only on very specific corner cases, mainly
> for the testing.

Sure, works for me.

Something like that was my guess as well since new headers
we're CRLF and other as they were in incoming request.

So "problem" was self caused when analyzing traces where I had  -L
(--no-crlf) flag passed to sipsak in some tests.

-- 
Mikko

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

2016-12-01 Thread Daniel-Constantin Mierla

Hello,


tm.t_uac_start is another rpc command than what was tried before, this
one doesn't do async operation.

Cheers,
Daniel

On 01/12/2016 13:28, Jonathan Hunter wrote:
>
> Hello,
>
>
> I am currently still using the exec module, so within the .cfg file,
> as when using jsonrpc-s its coming up with the async command issue
> again, I presume this will still be the case?
>
>
> Ok I will try with the combinations you mention.
>
>
> Many thanks
>
>
> Jon
>
>
>
> 
> *From:* Daniel-Constantin Mierla 
> *Sent:* 01 December 2016 12:24
> *To:* Jonathan Hunter; Kamailio SER - Users Mailing List
> *Subject:* Re: [SR-Users] Send SIP Info within a dialog using
> $uac_req(method)="INFO"
>  
>
> Hello,
>
>
> are you still trying with MI command via kamctl? Not with the
> jsonrpc-s module and tm.t_uac_start?
>
>
> When double quotes disappear is likely due to command line
> interpreter, so you need to put two of them for each one you have now,
> then ones than need to stay should be with more backslashes.
>
>
> Also, you can try to use single quotes to enclose the parameter values
> and let the double quotes in the content of the parameter.
>
>
> Cheers,
> Daniel
>
>
> On 30/11/2016 15:38, Jonathan Hunter wrote:
>> Hi,
>>
>> I am just testing with the mi t_uac_dlg command, and I am trying to
>> create an additional header, which is sent in the SIP INFO message
>> and actually contains double quotes.
>>
>> So in my kamailio.cfg script file I set the variable;
>>
>>
>> $var(testjon8) = "p1=\"STOP\"";
>>
>> xlog("L_INFO","We are going to try and use $var(testjon8)\n");
>>
>> And when seeing in the logs I see it states;
>>
>> We are going to try and use p1="STOP"
>>
>> And p1="STOP" is exactly what I want.
>>
>> However when I generate the SIP INFO message, and check on the wire
>> using wireshark I see;
>>
>> Event:p1=STOP
>>
>> So it doesnt have the double quotes I would like.
>>
>> How can I escape them so the t_uac_dlg command includes them?
>>
>> The portion where this header is generated in the command is;
>>
>>
>> exec_avp("kamctl mi t_uac_dlg INFO $dlg(to_uri) . .
>> \\\"From:'$var(testjon)'\"\\r\\nTo:$var(testjon2)\\r\\nCall-ID:$var(testjon3)\\r\\nAllow:$var(Allow)\\r\\nContact:$var(testjon4)\\r\\nEvent:$var(testjon8)\\r\\n\\\"\"",
>> "$avp(test)");
>>
>>
>>
>> And also running debug I see it as Event:p1="STOP"\r\n\""
>>
>>
>> Can you tell me how I can escape " so its actually within the SIP
>> header itself?
>>
>> Many thanks
>>
>> Jon
>>
>>
>>
>> 
>> *From:* sr-users  on behalf of
>> Jonathan Hunter 
>> *Sent:* 25 November 2016 18:55
>> *To:* Kamailio SER - Users Mailing List; mico...@gmail.com
>> *Subject:* Re: [SR-Users] Send SIP Info within a dialog using
>> $uac_req(method)="INFO"
>>  
>>
>> Hi Daniel,
>>
>>
>> Great thanks very much, will give it a try.
>>
>>
>> Jon
>>
>>
>>
>> 
>> *From:* Daniel-Constantin Mierla 
>> *Sent:* 22 November 2016 18:46
>> *To:* Jonathan Hunter; Kamailio SER - Users Mailing List
>> *Subject:* Re: [SR-Users] Send SIP Info within a dialog using
>> $uac_req(method)="INFO"
>>  
>>
>> Hello,
>>
>>
>> got a bit of time to look at the code and discovered that there is a
>> rpc command tm.t_uac_start added by ser guys that might get you
>> moving forward. It is not waiting for the reply of the generated
>> request and you can use it with json rpc exec function in the config,
>> so it avoids using exec.
>>
>>
>> Can you give it a try?
>>
>>
>> Some documentation can be found in the comments of the function used
>> by this command:
>>
>>   -
>> https://github.com/kamailio/kamailio/blob/master/modules/tm/rpc_uac.c#L399
>>
>> Cheers,
>> Daniel
>>
>>
>> On 22/11/2016 18:35, Jonathan Hunter wrote:
>>>
>>> Hi Daniel,
>>>
>>>
>>> Thanks here you go;
>>>
>>>
>>> [root@POC_ProxyA kamailio]# kamctl mi t_uac_dlg INFO
>>> sip:3003@193.144.1.112 . udp:10.70.1.136:5060  
>>>  
>>> \"From:sip:1234@8.8.8.8"\r\nTo:sip:3003@193.144.1.112\r\nContact:sip:daemon@8.8.8.8\r\n\""
>>> 404 Invalid local socket
>>> [root@POC_ProxyA kamailio]# VERBOSE=1 kamctl mi t_uac_dlg INFO
>>> sip:3003@193.144.1.112 . udp:10.70.1.136:5060  
>>>  
>>> \"From:sip:1234@8.8.8.8"\r\nTo:sip:3003@193.144.1.112\r\nContact:sip:daemon@8.8.8.8\r\n\""
>>> database engine 'MYSQL' loaded
>>> Control engine 'FIFO' loaded
>>> entering fifo_cmd t_uac_dlg INFO sip:3003@193.144.1.112 .
>>> udp:10.70.1.136:5060 "From:sip:1234@8.8.8.8
>>> To:sip:3003@193.144.1.112
>>> Contact:sip:daemon@8.8.8.8
>>> "
>>> 404 Invalid local socket
>>> FIFO command was:
>>> :t_uac_dlg:kamailio_receiver_23469
>>> INFO
>>> sip:3003@193.144.1.112
>>> .
>>> udp:10.70.1.136:5060
>>> "From:sip:1234@8.8.8.8
>>> To:sip:3003@193.144.1.112
>>>

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

2016-12-01 Thread Jonathan Hunter

Hello,


I am currently still using the exec module, so within the .cfg file, as when 
using jsonrpc-s its coming up with the async command issue again, I presume 
this will still be the case?


Ok I will try with the combinations you mention.


Many thanks


Jon



From: Daniel-Constantin Mierla 
Sent: 01 December 2016 12:24
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using 
$uac_req(method)="INFO"


Hello,


are you still trying with MI command via kamctl? Not with the jsonrpc-s module 
and tm.t_uac_start?


When double quotes disappear is likely due to command line interpreter, so you 
need to put two of them for each one you have now, then ones than need to stay 
should be with more backslashes.


Also, you can try to use single quotes to enclose the parameter values and let 
the double quotes in the content of the parameter.


Cheers,
Daniel

On 30/11/2016 15:38, Jonathan Hunter wrote:
Hi,

I am just testing with the mi t_uac_dlg command, and I am trying to create an 
additional header, which is sent in the SIP INFO message and actually contains 
double quotes.

So in my kamailio.cfg script file I set the variable;


$var(testjon8) = "p1=\"STOP\"";

xlog("L_INFO","We are going to try and use $var(testjon8)\n");

And when seeing in the logs I see it states;

We are going to try and use p1="STOP"

And p1="STOP" is exactly what I want.

However when I generate the SIP INFO message, and check on the wire using 
wireshark I see;

Event:p1=STOP

So it doesnt have the double quotes I would like.

How can I escape them so the t_uac_dlg command includes them?

The portion where this header is generated in the command is;


exec_avp("kamctl mi t_uac_dlg INFO $dlg(to_uri) . . 
\\\"From:'$var(testjon)'\"\\r\\nTo:$var(testjon2)\\r\\nCall-ID:$var(testjon3)\\r\\nAllow:$var(Allow)\\r\\nContact:$var(testjon4)\\r\\nEvent:$var(testjon8)\\r\\n\\\"\"",
 "$avp(test)");



And also running debug I see it as Event:p1="STOP"\r\n\""


Can you tell me how I can escape " so its actually within the SIP header itself?

Many thanks

Jon




From: sr-users 

 on behalf of Jonathan Hunter 

Sent: 25 November 2016 18:55
To: Kamailio SER - Users Mailing List; 
mico...@gmail.com
Subject: Re: [SR-Users] Send SIP Info within a dialog using 
$uac_req(method)="INFO"


Hi Daniel,


Great thanks very much, will give it a try.


Jon



From: Daniel-Constantin Mierla 
Sent: 22 November 2016 18:46
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using 
$uac_req(method)="INFO"


Hello,


got a bit of time to look at the code and discovered that there is a rpc 
command tm.t_uac_start added by ser guys that might get you moving forward. It 
is not waiting for the reply of the generated request and you can use it with 
json rpc exec function in the config, so it avoids using exec.


Can you give it a try?


Some documentation can be found in the comments of the function used by this 
command:

  - https://github.com/kamailio/kamailio/blob/master/modules/tm/rpc_uac.c#L399

Cheers,
Daniel


On 22/11/2016 18:35, Jonathan Hunter wrote:

Hi Daniel,


Thanks here you go;


[root@POC_ProxyA kamailio]# kamctl mi t_uac_dlg INFO sip:3003@193.144.1.112 . 
udp:10.70.1.136:5060
\"From:sip:1234@8.8.8.8"\r\nTo:sip:3003@193.144.1.112\r\nContact:sip:daemon@8.8.8.8\r\n\""
404 Invalid local socket
[root@POC_ProxyA kamailio]# VERBOSE=1 kamctl mi t_uac_dlg INFO 
sip:3003@193.144.1.112 . udp:10.70.1.136:5060
\"From:sip:1234@8.8.8.8"\r\nTo:sip:3003@193.144.1.112\r\nContact:sip:daemon@8.8.8.8\r\n\""
database engine 'MYSQL' loaded
Control engine 'FIFO' loaded
entering fifo_cmd t_uac_dlg INFO sip:3003@193.144.1.112 . udp:10.70.1.136:5060 
"From:sip:1234@8.8.8.8
To:sip:3003@193.144.1.112
Contact:sip:daemon@8.8.8.8
"
404 Invalid local socket
FIFO command was:
:t_uac_dlg:kamailio_receiver_23469
INFO
sip:3003@193.144.1.112
.
udp:10.70.1.136:5060
"From:sip:1234@8.8.8.8
To:sip:3003@193.144.1.112
Contact:sip:daemon@8.8.8.8
"


Thanks


Jon

Daniel-Constantin Mierla
http://twitter.com/#!/miconda - 
http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com


--
Daniel-Constantin Mierla
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - 
www.kamailioworld.com
___
SIP Express Router (SER) and Kamailio

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

2016-12-01 Thread Daniel-Constantin Mierla

Hello,


are you still trying with MI command via kamctl? Not with the jsonrpc-s
module and tm.t_uac_start?


When double quotes disappear is likely due to command line interpreter,
so you need to put two of them for each one you have now, then ones than
need to stay should be with more backslashes.


Also, you can try to use single quotes to enclose the parameter values
and let the double quotes in the content of the parameter.


Cheers,
Daniel


On 30/11/2016 15:38, Jonathan Hunter wrote:
> Hi,
>
> I am just testing with the mi t_uac_dlg command, and I am trying to
> create an additional header, which is sent in the SIP INFO message and
> actually contains double quotes.
>
> So in my kamailio.cfg script file I set the variable;
>
>
> $var(testjon8) = "p1=\"STOP\"";
>
> xlog("L_INFO","We are going to try and use $var(testjon8)\n");
>
> And when seeing in the logs I see it states;
>
> We are going to try and use p1="STOP"
>
> And p1="STOP" is exactly what I want.
>
> However when I generate the SIP INFO message, and check on the wire
> using wireshark I see;
>
> Event:p1=STOP
>
> So it doesnt have the double quotes I would like.
>
> How can I escape them so the t_uac_dlg command includes them?
>
> The portion where this header is generated in the command is;
>
>
> exec_avp("kamctl mi t_uac_dlg INFO $dlg(to_uri) . .
> \\\"From:'$var(testjon)'\"\\r\\nTo:$var(testjon2)\\r\\nCall-ID:$var(testjon3)\\r\\nAllow:$var(Allow)\\r\\nContact:$var(testjon4)\\r\\nEvent:$var(testjon8)\\r\\n\\\"\"",
> "$avp(test)");
>
>
>
> And also running debug I see it as Event:p1="STOP"\r\n\""
>
>
> Can you tell me how I can escape " so its actually within the SIP
> header itself?
>
> Many thanks
>
> Jon
>
>
>
> 
> *From:* sr-users  on behalf of
> Jonathan Hunter 
> *Sent:* 25 November 2016 18:55
> *To:* Kamailio SER - Users Mailing List; mico...@gmail.com
> *Subject:* Re: [SR-Users] Send SIP Info within a dialog using
> $uac_req(method)="INFO"
>  
>
> Hi Daniel,
>
>
> Great thanks very much, will give it a try.
>
>
> Jon
>
>
>
> 
> *From:* Daniel-Constantin Mierla 
> *Sent:* 22 November 2016 18:46
> *To:* Jonathan Hunter; Kamailio SER - Users Mailing List
> *Subject:* Re: [SR-Users] Send SIP Info within a dialog using
> $uac_req(method)="INFO"
>  
>
> Hello,
>
>
> got a bit of time to look at the code and discovered that there is a
> rpc command tm.t_uac_start added by ser guys that might get you moving
> forward. It is not waiting for the reply of the generated request and
> you can use it with json rpc exec function in the config, so it avoids
> using exec.
>
>
> Can you give it a try?
>
>
> Some documentation can be found in the comments of the function used
> by this command:
>
>   -
> https://github.com/kamailio/kamailio/blob/master/modules/tm/rpc_uac.c#L399
>
> Cheers,
> Daniel
>
>
> On 22/11/2016 18:35, Jonathan Hunter wrote:
>>
>> Hi Daniel,
>>
>>
>> Thanks here you go;
>>
>>
>> [root@POC_ProxyA kamailio]# kamctl mi t_uac_dlg INFO
>> sip:3003@193.144.1.112 . udp:10.70.1.136:5060  
>>  
>> \"From:sip:1234@8.8.8.8"\r\nTo:sip:3003@193.144.1.112\r\nContact:sip:daemon@8.8.8.8\r\n\""
>> 404 Invalid local socket
>> [root@POC_ProxyA kamailio]# VERBOSE=1 kamctl mi t_uac_dlg INFO
>> sip:3003@193.144.1.112 . udp:10.70.1.136:5060  
>>  
>> \"From:sip:1234@8.8.8.8"\r\nTo:sip:3003@193.144.1.112\r\nContact:sip:daemon@8.8.8.8\r\n\""
>> database engine 'MYSQL' loaded
>> Control engine 'FIFO' loaded
>> entering fifo_cmd t_uac_dlg INFO sip:3003@193.144.1.112 .
>> udp:10.70.1.136:5060 "From:sip:1234@8.8.8.8
>> To:sip:3003@193.144.1.112
>> Contact:sip:daemon@8.8.8.8
>> "
>> 404 Invalid local socket
>> FIFO command was:
>> :t_uac_dlg:kamailio_receiver_23469
>> INFO
>> sip:3003@193.144.1.112
>> .
>> udp:10.70.1.136:5060
>> "From:sip:1234@8.8.8.8
>> To:sip:3003@193.144.1.112
>> Contact:sip:daemon@8.8.8.8
>> "
>>
>>
>> Thanks
>>
>>
>> Jon
>>
> Daniel-Constantin Mierla
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
> Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com

-- 
Daniel-Constantin Mierla
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

2016-12-01 Thread Daniel-Constantin Mierla

Hello,

if you haven't changed the tm parameters that refer to reparsing
outgoing requests for building local hop-by-hop messages, then you
should not be affected by the issue reported by Helio Okuyama. The
function that needs to be patched should not used with default values of
tm parameters -- that's the reason I asked Helio to see if those
parameters were changed, to be sure it is no other case when the
function is used with default tm parameters.

Cheers,
Daniel


On 01/12/2016 11:31, Sergey Basov wrote:
> Hello.
>
> I make test, currently on kamailio 4.4.0, but as I see in git - tm
> module does not changes from that time.
> I have normal line termination.
> See a dump in attach.
> in that dump 10.56.41.33 and 10.56.42.33 is the my mhomed kamailio.
> --
> Best regards,
> Sergey Basov e-mail: sergey.v.ba...@gmail.com
>
> tel: (+38067) 403-62-54
>
>
> 2016-12-01 10:52 GMT+02:00 Daniel-Constantin Mierla :
>> Hello,
>>
>> have you set modparams for tm module related to reparsing the invite or on
>> dns failover?
>>
>> The build_local() should be used only in some specific cases and want to be
>> sure it doesn't get executed somehow when it shouldn't be.
>>
>> Cheers,
>> Daniel
>>
>>
>> On 30/11/2016 16:40, Helio Okuyama wrote:
>>
>> Local messages are malformed in Kamailio 4.4.X. For example after receiving
>> an error response (603) to an INVITE message, the ACK is generated with
>> header Max-Forwards concatenated to header CSeq and double CRLF, which is
>> wrong.
>>
>> Via: SIP/2.0/TLS
>> 173.16.10.61:5061;branch=z9hG4bKc782.5b960c7c48a4363a0126963daa797eb0.0;i=7
>> From: "22861";tag=snl_OIPEOzJUNy
>> Call-ID: 61b500a71b510a1Pj61qq1k9dPW
>> To: ;tag=435012226
>> CSeq: 2351 ACKMax-Forwards: 70
>>
>> User-Agent:...
>>
>>
>> The fix for that seems to be just the order of append_str in function
>> build_local() from tm\t_msgbuilder.c.
>>
>> append_str( p, method, method_len );
>> + append_str( p, CRLF, CRLF_LEN );
>> append_str( p, MAXFWD_HEADER, MAXFWD_HEADER_LEN );
>> - append_str( p, CRLF, CRLF_LEN );
>>
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>> --
>> Daniel-Constantin Mierla
>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>> Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

2016-12-01 Thread Daniel-Constantin Mierla



On 01/12/2016 02:05, Mikko Lehto wrote:
> Helio Okuyama  wrote:
>
>> Local messages are malformed in Kamailio 4.4.X. For example after receiving
>> an error response (603) to an INVITE message, the ACK is generated with
>> header Max-Forwards concatenated to header CSeq and double CRLF, which is
>> wrong.
> Funny thing, I just discovered something with line endings as well
> when replying locally from config file.
>
> Kamailio seems to reply with mixed line terminators when flag --no-crlf
> is used with sipsak.
The specs require to be \r\n. Accepting only \n is and
SER-time-propagated extension in Kamailio from the early days of the
project when a lot of tests during the development was done by building
messages inside a text file and injecting it into the network. When a
response is built by kamailio, the needed headers from request that are
not changed are just copied. Everything else will get the standard \r\n.

So this is due to that flexibility and I think we are fine with this
behaviour given it happens only on very specific corner cases, mainly
for the testing.

Cheers,
Daniel

>
> How to repeat:
>
> kamailio.cfg
> ---
> debug=2
> fork=yes
> log_stderror=no
> children=1
> disable_tcp=yes
> listen=udp:127.0.0.1:5060
> auto_aliases=no
> loadpath "modules/"
> loadmodule "sl.so"
> loadmodule "pv.so"
> loadmodule "textops.so"
> modparam("sl", "bind_tm", 0)
> request_route {
> set_reply_body($rb,"application/sdp");
> sl_send_reply(200,"OK");
> exit;
> }
> ---
>
> $ sipsak -H localhost -s sip:127.0.0.1:5060 -v -f 
> test/unit/60-message-sdp9.sip --no-crlf
>
> tcpdump shows following headers and line terminators:
> ---
> 200 OKCRLF
> Via...CRLF
> From...LF
> To...LF
> Call-ID...LF
> CSeq...LF
> Content-Type...CRLF
> Server...CRLF
> Content-Length...CRLF
> CRLF
> ---
>
> Maybe these two findings are related. I tested with master version.
>

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] help with string modification

2016-12-01 Thread Sergey Basov

Hi, All.

One more question related to remove_hf...

I have added route:
# Fix user-agent and server
route[RemoveHeader] {
remove_hf("server");
remove_hf("user-agent");
return;
}


I use it form
request_route {

route(RemoveHeader);
.
}

failure_route[--- all what i have ---] {

route(RemoveHeader);
.
}

branch_route[MANAGE_BRANCH]{

route(RemoveHeader);
.
}

onreply_route[MANAGE_REPLY] {

route(RemoveHeader);
.
}

failure_route[MANAGE_FAILURE] {

route(RemoveHeader);
.
}

Seems all is fine It removes headers in all packets except 200 OK on BYE
After debugging script I does not seen in which route this 200 Ok goes..
But if I adding next to
route[RELAY] {

if (is_method("BYE")) {
xlog("L_INFO","route RELAY method BYE \n");
if(!t_is_set("onreply_route"))
t_on_reply("MANAGE_REPLY_ON_BYE");
}
...
}

and adding route
onreply_route[MANAGE_REPLY_ON_BYE] {
route(RemoveHeader);
xlog("L_INFO","route MANAGE_REPLY_ON_BYE entered \n");
}

this 200 Ok successfully goes to MANAGE_REPLY_ON_BYE route and headers
are removed.

Is this configuration correct?
I can not find any info regarding parsing 200 OK on BYE in google.

Sorry for long question...

--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com

tel: (+38067) 403-62-54


2016-11-28 11:32 GMT+02:00 Daniel Tryba :
> On Fri, Nov 25, 2016 at 06:55:34PM +0200, Sergey Basov wrote:
>> Is it safe to use remove_hf("User-Agent") without check if this header
>> exist?
>> or better use if(is_present_hf("User-Agent")) { remove_hf("User-Agent"); } ?
>
> Just remove_hf is enough. is_present_hf/remove_hf might be more readable
> though.
>
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

2016-12-01 Thread Sergey Basov

Hello.

I make test, currently on kamailio 4.4.0, but as I see in git - tm
module does not changes from that time.
I have normal line termination.
See a dump in attach.
in that dump 10.56.41.33 and 10.56.42.33 is the my mhomed kamailio.
--
Best regards,
Sergey Basov e-mail: sergey.v.ba...@gmail.com

tel: (+38067) 403-62-54


2016-12-01 10:52 GMT+02:00 Daniel-Constantin Mierla :
> Hello,
>
> have you set modparams for tm module related to reparsing the invite or on
> dns failover?
>
> The build_local() should be used only in some specific cases and want to be
> sure it doesn't get executed somehow when it shouldn't be.
>
> Cheers,
> Daniel
>
>
> On 30/11/2016 16:40, Helio Okuyama wrote:
>
> Local messages are malformed in Kamailio 4.4.X. For example after receiving
> an error response (603) to an INVITE message, the ACK is generated with
> header Max-Forwards concatenated to header CSeq and double CRLF, which is
> wrong.
>
> Via: SIP/2.0/TLS
> 173.16.10.61:5061;branch=z9hG4bKc782.5b960c7c48a4363a0126963daa797eb0.0;i=7
> From: "22861";tag=snl_OIPEOzJUNy
> Call-ID: 61b500a71b510a1Pj61qq1k9dPW
> To: ;tag=435012226
> CSeq: 2351 ACKMax-Forwards: 70
>
> User-Agent:...
>
>
> The fix for that seems to be just the order of append_str in function
> build_local() from tm\t_msgbuilder.c.
>
> append_str( p, method, method_len );
> + append_str( p, CRLF, CRLF_LEN );
> append_str( p, MAXFWD_HEADER, MAXFWD_HEADER_LEN );
> - append_str( p, CRLF, CRLF_LEN );
>
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierla
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
> Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>


603-test.pcap
Description: application/vnd.tcpdump.pcap
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] TSILO question

2016-12-01 Thread Federico Cabiddu

Hi,
about your questions:

Q1: yes it's feasible as long as the two Registrars (Kamailio) have the
location information. Please see my reply on a thread on this topic:
http://lists.sip-router.org/pipermail/sr-users/2016-February/091612.html

Q2: given that TSILO depends on the users' location you have to put it in
the Registrar.

Best regards,

Federico

On Wed, Nov 30, 2016 at 5:32 AM, C. J Hsu (徐熙杰)  wrote:

> hi Federico
>
> i'm stuck at TSILO and wondering if you could give me some advises.
>
> Q1:
>
> in lab1, I'm having two Kamailios with proxy and registrar together, UA1
> and UA2.
> UAs go thru hardware load-balancing device (F5) to register themselves in
> Kamailio,
>
> I wonder, UA1 calling to UA2, invite suspended in Kamailio 1, waiting for
> UA2;
> and when UA2 come to register in Kamailio 2, TSILO in Kamailio 1 resumes
> the invite and sending it to Kamailio 2, is this a no problem scenario?
>
> Q2:
>
> if we decide to separate Proxy and Registrar in different Kamailio, when
> should I put TSILO in?
>
>
> RGDS
>
> C J
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] RTP Pyload

2016-12-01 Thread Mikko Lehto

amar Smart Telecom  wrote:

> We are seeing that some RTP Payload are with 14 bytes and some are with 15
> bytes.
> 
>  
> 
> 1.   14 byte is correct or 15 byte is correct?
> 
> 2.   Is TOC present in all payloads i.e. in all RTP messages?
> 
> Following example with 14 byte payload.
>

> The query is regarding, while using "Payload type: DynamicRTP-Type-111
> (111)"

Hi

Please explain how this relates to Kamailio, hopefully after that
there is less guesswork for potential advice.

Best regards

-- 
Mikko Lehto

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Real error?

2016-12-01 Thread Ivailo Dobrev

Yes, and it is very annoying one. On 2-3 restarts is happens. Not had 
enough time to troubleshoot it.


On 12/01/2016 06:27 AM, Olvera, Victor wrote:

Is this a real error?

9(1899) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): 
Error on finding local host address > Socket operation on non-socket



Great regards,


Victor Olvera
victor.olv...@verizonwireless.com 


mobile # 001-214-923-9405




___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] RTP Pyload

2016-12-01 Thread amar Smart Telecom

The query is regarding, while using "Payload type: DynamicRTP-Type-111
(111)"

 

Regrads.

 

From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
amar Smart Telecom
Sent: Thursday, December 1, 2016 2:46 PM
To: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] RTP Pyload

 

 

Dear all,

 

We are seeing that some RTP Payload are with 14 bytes and some are with 15
bytes.

 

1.   14 byte is correct or 15 byte is correct?

2.   Is TOC present in all payloads i.e. in all RTP messages?

Following example with 14 byte payload.

 

 

 

Regards,

Amar

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] http_async_client - queries

2016-12-01 Thread Giacomo Vacca

Hi Agalya,
can you please provide an example of the data format you'd like to use and
the related http_async parameters and request?
And possibly also an example of expected final content of the HTTP request?
We'll try to better understand what you want achieve.

Cheers,
Giacomo

On 30 November 2016 at 20:00, Ramachandran, Agalya (Contractor) <
agalya_ramachand...@comcast.com> wrote:

> Hi team,
>
>
>
> We are trying to use kamailio for our project purpose, which will be used
> as a proxy server.
>
> Am trying to use “http_async_client” module to send my rest queries
> asynchronously.
>
>
>
> I have few queries regarding the usage of http_async_query() and using PUT
> method.
>
> *http_append_header("Authorization: Bearer $var(auth)");*
>
> *http_append_header("Content-Type: application/json");*
>
> *http_set_method("PUT");*
>
> *http_async_query("http://sdk-evm-wcdc-c-001.rtc.sys.comcast.net/events/createxmpprooteventfortn
> ",
> "{'from_tn':'$fU','to_tn':'$tU','callid':'ci'}", "HTTP_REPLY");*
>
>
>
> Here am passing from, to, callid in post data field.
>
> Passing as ‘key’:’value’  is mandatory or I can pass only value- ?
>
>
>
> In the file, async_http.c – in async_send_query(), if I modify the post
> data to the format I need, I see the value is truncated up to three fields
> only.
>
> How can I achieve that my payload format whatever I form in
> async_send_query(),doesn’t get truncated and will be passed to the server-?
>
> Can you please explain how this works-?
>
>
>
> Also, I observed that kamailio is restricting the content-length of HTTP
> request to 256.
>
> Is this something modifiable-? If so please guide me how this can be
> achieved.
>
>
>
> Regards,
> Agalya
>
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] RTP Pyload

2016-12-01 Thread amar Smart Telecom

 

Dear all,

 

We are seeing that some RTP Payload are with 14 bytes and some are with 15
bytes.

 

1.   14 byte is correct or 15 byte is correct?

2.   Is TOC present in all payloads i.e. in all RTP messages?

Following example with 14 byte payload.

 

 

 

Regards,

Amar

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

2016-12-01 Thread Daniel-Constantin Mierla

Hello,

have you set modparams for tm module related to reparsing the invite or
on dns failover?

The build_local() should be used only in some specific cases and want to
be sure it doesn't get executed somehow when it shouldn't be.

Cheers,
Daniel


On 30/11/2016 16:40, Helio Okuyama wrote:
> Local messages are malformed in Kamailio 4.4.X. For example after
> receiving an error response (603) to an INVITE message, the ACK is
> generated with header Max-Forwards concatenated to header CSeq and
> double CRLF, which is wrong.
>
> Via: SIP/2.0/TLS
> 173.16.10.61:5061;branch=z9hG4bKc782.5b960c7c48a4363a0126963daa797eb0.0;i=7
> From: "22861" ;transport=tls>;tag=snl_OIPEOzJUNy
> Call-ID: 61b500a71b510a1Pj61qq1k9dPW
> To: ;tag=435012226
> CSeq: 2351 ACKMax-Forwards: 70
>
> User-Agent:...
>
>
> The fix for that seems to be just the order of append_str in function
> build_local() from tm\t_msgbuilder.c.
>
> append_str( p, method, method_len );
> +append_str( p, CRLF, CRLF_LEN );
> append_str( p, MAXFWD_HEADER, MAXFWD_HEADER_LEN );
> -append_str( p, CRLF, CRLF_LEN );
>
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] In dialog messages cannot be routed after re-registration with outbound and gruu

2016-12-01 Thread Robert

Hi,

I'm using outbound with gruu enabled and with edge proxy, registrar and auth
proxy all running as separate entities. My problem is once a dialog is
formed between two UAs, if one side re-registers and gets assigned a new
flow token, all subsequent in-dialog messages cannot be routed because the
flow token in the Route set is no longer valid. 

What is the proper way to update the binding?

I read in this  thread

  
that "using GRUU means that Outbound is also used, so the 
Contact has a +sip.instance and reg-id params which are inspected by 
the registrar to create/update/delete a binding". How is the binding updated
exactly?

Any help would be appreciated.



--
View this message in context: 
http://sip-router.1086192.n5.nabble.com/In-dialog-messages-cannot-be-routed-after-re-registration-with-outbound-and-gruu-tp153677.html
Sent from the Users mailing list archive at Nabble.com.

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Dual Stack Environments

Re: [SR-Users] [sr-dev] VERY IMPORTANT: deciding when to remove the MI code

Re: [SR-Users] Limiting Registration Contacts

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Re: [SR-Users] VERY IMPORTANT: deciding when to remove the MI code

[SR-Users] VERY IMPORTANT: deciding when to remove the MI code

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Re: [SR-Users] Send SIP Info within a dialog using $uac_req(method)="INFO"

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

Re: [SR-Users] help with string modification

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

Re: [SR-Users] TSILO question

Re: [SR-Users] RTP Pyload

Re: [SR-Users] Real error?

Re: [SR-Users] RTP Pyload

Re: [SR-Users] http_async_client - queries

Re: [SR-Users] RTP Pyload

Re: [SR-Users] Local messages are malformed in Kamailio 4.4.X

[SR-Users] In dialog messages cannot be routed after re-registration with outbound and gruu

23 matches

Site Navigation

Mail list logo

Footer information