date:20171103

Re: [SR-Users] Invalid JSON when dumping htable with JSONRPC-S

2017-11-03 Thread Daniel-Constantin Mierla

Hello,

indeed, the format was wrong, I just pushed a patch for it in master and
branch 5.0:

  -
https://github.com/kamailio/kamailio/commit/0956257ae6fdc0a801ce109017089ac18018e63b

Cheers,
Daniel

On 03.11.17 17:01, Marrold wrote:
> Hi All,
>
> I am currently trying to retrieve the contents of a htable using the
> JSONRPC-S module over HTTP, however I have observed if a slot contains
> multiple values, the JSON returned has duplicate keys which could be
> considered invalid. 
>
> Here are the relevant lines from kamailio.cfg -
>
> event_route[xhttp:request] {
>     if ($hu =~ "^/carrier") {
>         jsonrpc_exec('{"jsonrpc": "2.0", "method": "htable.dump",
> "params" : {"htable": "carrier"}, "id": 1}');
>         xhttp_reply("200", "OK", "text/html", "$jsonrpl(body)");
>     }
> }
>
> And the output, showing a slot with two items-
>
>
> {
> "entry": 5,
> "size": 2,
> "slot": {
> "item": {
> "name": "carrierA",
> "value": "90",
> "type": "str"
> },
> "item": {
> "name": "carrierB",
> "value": "190",
> "type": "str"
> }
> }
> }
>
> And the same from `kamcmd -s unix:/tmp/kamailio_ctl htable.dump carrier` -
>
> {
> entry: 5
> size: 2
> slot: {
> item: {
> name: carrierA
> value: 90
> type: str
> }
> item: {
> name: carrierB
> value: 190
> type: str
> }
> }
> }
>
> Would it be possible to change it to something like the following -
>
> {
>     "entry": 5,
>     "size": 2,
>     "slot": [
>         {
>             "name": "carrierA",
>             "value": "90",
>             "type": "str"
>         },
>         {
>             "name": "carrierB",
>             "value": "190",
>             "type": "str"
>         }
>     ]
> }
>
> Any other suggestions or work arounds would be appreciated, 
>
> Thanks
> Matthew
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com
Kamailio World Conference - www.kamailioworld.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Contacts in 302

2017-11-03 Thread John Petrini

If you're trying to modify the contact on your branch I believe you need to
do that in a branch route. For example in branch_route[EVAPIRESPONSE] you
could modify the contact header and. Just make sure to set the branch route
in route[EVAPIRESPONSE].

Then instead of using a var you could use an avp. avp's work as a stack so
a single avp could hold all of your contacts. In your branch route you
could then do something like:

remove_hf('Contact');
append_hf('Contact: $avp(contact)');
pv_unset ("$avp(contact)"); # This will pop the first contact off the avp
so the next time you call this avp you'll get the second contact

I hope that's helpful and gives you some ideas.

On Fri, Nov 3, 2017 at 12:00 PM, Diego Nadares  wrote:

> Hi john, thanks for your answer. I'm using this in route[EVAPIRESPONSE]
> because of async request with evapi.
>
> I tried what you said too with no success.
>
> #$var(first) = 0;
>
> #while ($var(i) < $var(contacts_len)){
>
> #   jansson_get("contacts[$var(i)]", "$var(evmsg)",
> "$var(contact)");
>
> #   if ($var(first) == 0){
>
> #   $ru = $var(contact);
>
> #   $var(first) = 1;
>
> #   }
>
> #   append_branch($var(contact), "0.5");
>
> #   $var(i) = $var(i) + 1;
>
> #}
>
> remove_hf('Contact');
>
> append_hf('Contact: <@188.111.111.113>');
>
> send_reply("302", "Moved Temporarily");
>
> exit;
>
>
> The result is ONLY the original uri in the contact. *Contact:
> <@188.111.111.112 <@188.111.111.112>>*
>
> Diego
>
>
>
> 2017-11-02 22:22 GMT-03:00 John Petrini :
>
>> remove_hf('Contact') and then append_hf($var(contact)) should work. What
>> was the problem you were having? Were you using it in a branch route?
>>
>>
>> John
>>
>> John Petrini | Platforms Engineer
>>
>> jpetr...@coredial.com
>>
>> 215.297.440 <215-297-4400>0
>>
>> 751 Arbor Way, Hillcrest I, Suite 150
>> Blue Bell, PA 19422
>>
>> www.coredial.com 
>> 
>> 
>>  
>>
>> The information transmitted is intended only for the person or entity to
>> which it is addressed and may contain confidential and/or privileged
>> material. Any review, retransmission, dissemination or other use of, or
>> taking of any action in reliance upon, this information by persons or
>> entities other than the intended recipient is prohibited. If you received
>> this in error, please contact the sender and delete the material from any
>> computer.
>>
>> On Thu, Nov 2, 2017 at 6:40 PM, Diego Nadares  wrote:
>>
>>> Hi again,
>>>
>>> I found a work around . Modifying $ru changes de first contact uri.
>>>
>>>  if($var(routing)=~"redirect"){
>>> jansson_get("contacts_len", "$var(evmsg)",
>>> "$var(contacts_len)");
>>> xlog("L_INFO", "Contacts len $var(contacts_len)");
>>> $var(i) = 0;
>>>
>>> *$var(first) = 0;*
>>> while ($var(i) < $var(contacts_len)){
>>> jansson_get("contacts[$var(i)]", "$var(evmsg)",
>>> "$var(contact)");
>>> if ($var(first) == 0){
>>>* $ru = $var(contact);*
>>>   *  $var(first) = 1;*
>>> }
>>> #Appending anyway because of the q param
>>> append_branch($var(contact), "0.5");
>>> $var(i) = $var(i) + 1;
>>> }
>>> send_reply("302", "Moved Temporarily");
>>> exit;
>>> }
>>>
>>> Contact: *<@188.111.111.112 >*, <
>>> sip:@188.111.111.112>;q=0.5, ;q=0.5
>>>
>>>
>>> I think this is not the better way. Any suggestion will be very
>>> appreciated.
>>>
>>> Thanks again.
>>>
>>> Diego
>>>
>>>
>>> 2017-11-02 18:11 GMT-03:00 Diego Nadares :
>>>
 Hi Guys,

 I'm generating a 302 reply from kamailio. In this 302 I append new
 branches with new
 contacts.

 if($var(routing)=~"redirect"){
 jansson_get("contacts_len", "$var(evmsg)",
 "$var(contacts_len)");
 xlog("L_INFO", "Contacts len $var(contacts_len)");
 $var(i) = 0;
 while ($var(i) < $var(contacts_len)){
 jansson_get("contacts[$var(i)]",
 "$var(evmsg)", "$var(contact)");
 append_branch($var(contact), "0.5");
 $var(i) = $var(i) + 1;
 }

Re: [SR-Users] Contacts in 302

2017-11-03 Thread Diego Nadares

Hi john, thanks for your answer. I'm using this in route[EVAPIRESPONSE]
because of async request with evapi.

I tried what you said too with no success.

#$var(first) = 0;

#while ($var(i) < $var(contacts_len)){

#   jansson_get("contacts[$var(i)]", "$var(evmsg)",
"$var(contact)");

#   if ($var(first) == 0){

#   $ru = $var(contact);

#   $var(first) = 1;

#   }

#   append_branch($var(contact), "0.5");

#   $var(i) = $var(i) + 1;

#}

remove_hf('Contact');

append_hf('Contact: <@188.111.111.113>');

send_reply("302", "Moved Temporarily");

exit;


The result is ONLY the original uri in the contact. *Contact:
<@188.111.111.112 <@188.111.111.112>>*

Diego



2017-11-02 22:22 GMT-03:00 John Petrini :

> remove_hf('Contact') and then append_hf($var(contact)) should work. What
> was the problem you were having? Were you using it in a branch route?
>
>
> John
>
> John Petrini | Platforms Engineer
>
> jpetr...@coredial.com
>
> 215.297.440 <215-297-4400>0
>
> 751 Arbor Way, Hillcrest I, Suite 150
> Blue Bell, PA 19422
>
> www.coredial.com 
> 
> 
>  
>
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited. If you received
> this in error, please contact the sender and delete the material from any
> computer.
>
> On Thu, Nov 2, 2017 at 6:40 PM, Diego Nadares  wrote:
>
>> Hi again,
>>
>> I found a work around . Modifying $ru changes de first contact uri.
>>
>>  if($var(routing)=~"redirect"){
>> jansson_get("contacts_len", "$var(evmsg)",
>> "$var(contacts_len)");
>> xlog("L_INFO", "Contacts len $var(contacts_len)");
>> $var(i) = 0;
>>
>> *$var(first) = 0;*
>> while ($var(i) < $var(contacts_len)){
>> jansson_get("contacts[$var(i)]", "$var(evmsg)",
>> "$var(contact)");
>> if ($var(first) == 0){
>>* $ru = $var(contact);*
>>   *  $var(first) = 1;*
>> }
>> #Appending anyway because of the q param
>> append_branch($var(contact), "0.5");
>> $var(i) = $var(i) + 1;
>> }
>> send_reply("302", "Moved Temporarily");
>> exit;
>> }
>>
>> Contact: *<@188.111.111.112 >*, <
>> sip:@188.111.111.112>;q=0.5, ;q=0.5
>>
>>
>> I think this is not the better way. Any suggestion will be very
>> appreciated.
>>
>> Thanks again.
>>
>> Diego
>>
>>
>> 2017-11-02 18:11 GMT-03:00 Diego Nadares :
>>
>>> Hi Guys,
>>>
>>> I'm generating a 302 reply from kamailio. In this 302 I append new
>>> branches with new
>>> contacts.
>>>
>>> if($var(routing)=~"redirect"){
>>> jansson_get("contacts_len", "$var(evmsg)",
>>> "$var(contacts_len)");
>>> xlog("L_INFO", "Contacts len $var(contacts_len)");
>>> $var(i) = 0;
>>> while ($var(i) < $var(contacts_len)){
>>> jansson_get("contacts[$var(i)]", "$var(evmsg)",
>>> "$var(contact)");
>>> append_branch($var(contact), "0.5");
>>> $var(i) = $var(i) + 1;
>>> }
>>> send_reply("302", "Moved Temporarily");
>>> exit;
>>> }
>>>
>>> The problem i'm facing is that I can't delete the original contact  
>>> *>> >*
>>>
>>> The resulting conctact:
>>>
>>> Contact: *>> >*, ;q=0.5,
>>> ;q=0.5
>>>
>>> I all ready tried with remove_hf('Contact') and adding the new ones
>>> after that but it doesn't worke either.
>>>
>>> The problem is that one gw takes the first contact over and over again
>>> and never the other two.
>>>
>>> Thanks in advance.
>>>
>>> Diego.
>>>
>>>
>>>
>>>
>>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>>

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Alex Balashov

Because it determines the proper route based on the method described in the 
'mhomed' section of the docs.

Your choices are either to let Kamailio do that, or set mhomed=0 and choose the 
egress interface manually based on your own criteria. You can do this by 
setting $fs prior to t_relay(), e.g.

$fs = 'udp:x.x.x.x:5060';

Bear in mind that this combination of transport, listener and port must 
correspond exactly to one of the listeners.

It sounds like that's what you need to do. 

-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Oz Mortimer

Why would it choose a different IP from the one it received on? How do I make 
it use the correct ip?



> On 3 Nov 2017, at 15:06, Alex Balashov  wrote:
> 
> That's probably because the mhomed test, as described in the docs, determines 
> that this should be the outbound interface. 
> 
> On November 3, 2017 10:51:06 AM EDT, Oz Mortimer  wrote:
>> Ok,
>> 
>> So sort of progress..
>> 
>> With mhomed=0 the calls arrive at the media server from the IP the call
>> was sent to,
>> With mhomed=1 the calls arrive at the media server from the first
>> registered IP address regardless of which IP the call was sent to.
>> 
>> So mhomed is doing the reverse of what I would expect…
>> 
>> 
>>> On 3 Nov 2017, at 14:43, Alex Balashov 
>> wrote:
>>> 
>>> I would not be concerned about superficial errors.
>>> 
>>> I am more concerned that the system is attempting to "resolve" an IP
>> address. This would only happen if its format is not deemed to be that
>> if an IP address. 
>>> 
>>> On November 3, 2017 10:38:41 AM EDT, Oz Mortimer
>>  wrote:
 nb. I only get 
>> fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
 
 When mhomed=1
 
 
 
> On 3 Nov 2017, at 14:21, Alex Balashov 
 wrote:
> 
> Are you sure the IP is correct? 
> 
> On November 3, 2017 10:20:17 AM EDT, Oz Mortimer
  wrote:
>> Ok - did that and got the same error, though this time I looked at
 what
>> it was;
>> Im /var/log/messages I see - 
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> 
>> Although the IP address’ are correct...
>> 
>> 
>>> On 3 Nov 2017, at 14:06, Alex Balashov
>> 
>> wrote:
>>> 
>>> On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
>>> 
 I have listen commented out - which means it listens on all IPs
 (doesn’t it?) - do I need to set them explicitly?
>>> 
>>> Try setting them explicitly, so that you can route them
>> explicitly.
>>> 
 I did add mhomed=1 on this setup - but the calls went a bit
>> crazy
 (I
 didn’t manage to capture quite what was happening).
>>> 
>>> Unfortunately, without knowing the specific facts, it's hard to
>>> speculate.
>>> 
>>> -- 
>>> Alex Balashov | Principal | Evariste Systems LLC
>>> 
>>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
>>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>> 
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> 
>> 
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity. 
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
>

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Alex Balashov

Also, to correct a previous statement: it does seem that Kamailio attempts to 
resolve the reverse DNS entries of its listeners on boot. That can be disabled 
via DNS core configuration parameters. It can also be ignored as it's of no 
concern to this scenario. 

On November 3, 2017 11:06:57 AM EDT, Alex Balashov  
wrote:
>That's probably because the mhomed test, as described in the docs,
>determines that this should be the outbound interface. 
>
>On November 3, 2017 10:51:06 AM EDT, Oz Mortimer 
>wrote:
>>Ok,
>>
>>So sort of progress..
>>
>>With mhomed=0 the calls arrive at the media server from the IP the
>call
>>was sent to,
>>With mhomed=1 the calls arrive at the media server from the first
>>registered IP address regardless of which IP the call was sent to.
>>
>>So mhomed is doing the reverse of what I would expect…
>>
>>
>>> On 3 Nov 2017, at 14:43, Alex Balashov 
>>wrote:
>>> 
>>> I would not be concerned about superficial errors.
>>> 
>>> I am more concerned that the system is attempting to "resolve" an IP
>>address. This would only happen if its format is not deemed to be that
>>if an IP address. 
>>> 
>>> On November 3, 2017 10:38:41 AM EDT, Oz Mortimer
>> wrote:
 nb. I only get 
>> fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
 
 When mhomed=1
 
 
 
> On 3 Nov 2017, at 14:21, Alex Balashov 
 wrote:
> 
> Are you sure the IP is correct? 
> 
> On November 3, 2017 10:20:17 AM EDT, Oz Mortimer
  wrote:
>> Ok - did that and got the same error, though this time I looked
>at
 what
>> it was;
>> Im /var/log/messages I see - 
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> 
>> Although the IP address’ are correct...
>> 
>> 
>>> On 3 Nov 2017, at 14:06, Alex Balashov
>>
>> wrote:
>>> 
>>> On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
>>> 
 I have listen commented out - which means it listens on all IPs
 (doesn’t it?) - do I need to set them explicitly?
>>> 
>>> Try setting them explicitly, so that you can route them
>>explicitly.
>>> 
 I did add mhomed=1 on this setup - but the calls went a bit
>>crazy
 (I
 didn’t manage to capture quite what was happening).
>>> 
>>> Unfortunately, without knowing the specific facts, it's hard to
>>> speculate.
>>> 
>>> -- 
>>> Alex Balashov | Principal | Evariste Systems LLC
>>> 
>>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
>>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>> 
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> 
>> 
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity. 
> 
>

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Alex Balashov

That's probably because the mhomed test, as described in the docs, determines 
that this should be the outbound interface. 

On November 3, 2017 10:51:06 AM EDT, Oz Mortimer  wrote:
>Ok,
>
>So sort of progress..
>
>With mhomed=0 the calls arrive at the media server from the IP the call
>was sent to,
>With mhomed=1 the calls arrive at the media server from the first
>registered IP address regardless of which IP the call was sent to.
>
>So mhomed is doing the reverse of what I would expect…
>
>
>> On 3 Nov 2017, at 14:43, Alex Balashov 
>wrote:
>> 
>> I would not be concerned about superficial errors.
>> 
>> I am more concerned that the system is attempting to "resolve" an IP
>address. This would only happen if its format is not deemed to be that
>if an IP address. 
>> 
>> On November 3, 2017 10:38:41 AM EDT, Oz Mortimer
> wrote:
>>> nb. I only get 
> fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
>>> 
>>> When mhomed=1
>>> 
>>> 
>>> 
 On 3 Nov 2017, at 14:21, Alex Balashov 
>>> wrote:
 
 Are you sure the IP is correct? 
 
 On November 3, 2017 10:20:17 AM EDT, Oz Mortimer
>>>  wrote:
> Ok - did that and got the same error, though this time I looked at
>>> what
> it was;
> Im /var/log/messages I see - 
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
> xxx.xxx.xxx.xxx
> 
> Although the IP address’ are correct...
> 
> 
>> On 3 Nov 2017, at 14:06, Alex Balashov
>
> wrote:
>> 
>> On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
>> 
>>> I have listen commented out - which means it listens on all IPs
>>> (doesn’t it?) - do I need to set them explicitly?
>> 
>> Try setting them explicitly, so that you can route them
>explicitly.
>> 
>>> I did add mhomed=1 on this setup - but the calls went a bit
>crazy
>>> (I
>>> didn’t manage to capture quite what was happening).
>> 
>> Unfortunately, without knowing the specific facts, it's hard to
>> speculate.
>> 
>> -- 
>> Alex Balashov | Principal | Evariste Systems LLC
>> 
>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>> 
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
 
 
 -- Alex
 
 --
 Sent via mobile, please forgive typos and brevity. 
 
 ___
 Kamailio (SER) - Users Mailing List
 sr-users@lists.kamailio.org
 https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>> 
>>> 
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> 
>> 
>> -- Alex
>> 
>> --
>> Sent via mobile, please forgive typos and brevity. 
>> 
>>

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Oz Mortimer

Ok,

So sort of progress..

With mhomed=0 the calls arrive at the media server from the IP the call was 
sent to,
With mhomed=1 the calls arrive at the media server from the first registered IP 
address regardless of which IP the call was sent to.

So mhomed is doing the reverse of what I would expect…


> On 3 Nov 2017, at 14:43, Alex Balashov  wrote:
> 
> I would not be concerned about superficial errors.
> 
> I am more concerned that the system is attempting to "resolve" an IP address. 
> This would only happen if its format is not deemed to be that if an IP 
> address. 
> 
> On November 3, 2017 10:38:41 AM EDT, Oz Mortimer  wrote:
>> nb. I only get 
 fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
>> 
>> When mhomed=1
>> 
>> 
>> 
>>> On 3 Nov 2017, at 14:21, Alex Balashov 
>> wrote:
>>> 
>>> Are you sure the IP is correct? 
>>> 
>>> On November 3, 2017 10:20:17 AM EDT, Oz Mortimer
>>  wrote:
 Ok - did that and got the same error, though this time I looked at
>> what
 it was;
 Im /var/log/messages I see - 
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
 [socket_info.c:1392]: fix_hostname(): could not rev. resolve
 xxx.xxx.xxx.xxx
 
 Although the IP address’ are correct...
 
 
> On 3 Nov 2017, at 14:06, Alex Balashov 
 wrote:
> 
> On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
> 
>> I have listen commented out - which means it listens on all IPs
>> (doesn’t it?) - do I need to set them explicitly?
> 
> Try setting them explicitly, so that you can route them explicitly.
> 
>> I did add mhomed=1 on this setup - but the calls went a bit crazy
>> (I
>> didn’t manage to capture quite what was happening).
> 
> Unfortunately, without knowing the specific facts, it's hard to
> speculate.
> 
> -- 
> Alex Balashov | Principal | Evariste Systems LLC
> 
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
 
 
 ___
 Kamailio (SER) - Users Mailing List
 sr-users@lists.kamailio.org
 https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>> 
>>> 
>>> -- Alex
>>> 
>>> --
>>> Sent via mobile, please forgive typos and brevity. 
>>> 
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> 
>> 
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity. 
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Alex Balashov

I would not be concerned about superficial errors.

I am more concerned that the system is attempting to "resolve" an IP address. 
This would only happen if its format is not deemed to be that if an IP address. 

On November 3, 2017 10:38:41 AM EDT, Oz Mortimer  wrote:
>nb. I only get 
>>>  fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>
>When mhomed=1
>
>
>
>> On 3 Nov 2017, at 14:21, Alex Balashov 
>wrote:
>> 
>> Are you sure the IP is correct? 
>> 
>> On November 3, 2017 10:20:17 AM EDT, Oz Mortimer
> wrote:
>>> Ok - did that and got the same error, though this time I looked at
>what
>>> it was;
>>> Im /var/log/messages I see - 
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>>> xxx.xxx.xxx.xxx
>>> 
>>> Although the IP address’ are correct...
>>> 
>>> 
 On 3 Nov 2017, at 14:06, Alex Balashov 
>>> wrote:
 
 On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
 
> I have listen commented out - which means it listens on all IPs
> (doesn’t it?) - do I need to set them explicitly?
 
 Try setting them explicitly, so that you can route them explicitly.
 
> I did add mhomed=1 on this setup - but the calls went a bit crazy
>(I
> didn’t manage to capture quite what was happening).
 
 Unfortunately, without knowing the specific facts, it's hard to
 speculate.
 
 -- 
 Alex Balashov | Principal | Evariste Systems LLC
 
 Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
 Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
 
 ___
 Kamailio (SER) - Users Mailing List
 sr-users@lists.kamailio.org
 https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>> 
>>> 
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> 
>> 
>> -- Alex
>> 
>> --
>> Sent via mobile, please forgive typos and brevity. 
>> 
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>___
>Kamailio (SER) - Users Mailing List
>sr-users@lists.kamailio.org
>https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Oz Mortimer

nb. I only get 
>>  fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx

When mhomed=1



> On 3 Nov 2017, at 14:21, Alex Balashov  wrote:
> 
> Are you sure the IP is correct? 
> 
> On November 3, 2017 10:20:17 AM EDT, Oz Mortimer  wrote:
>> Ok - did that and got the same error, though this time I looked at what
>> it was;
>> Im /var/log/messages I see - 
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> 
>> Although the IP address’ are correct...
>> 
>> 
>>> On 3 Nov 2017, at 14:06, Alex Balashov 
>> wrote:
>>> 
>>> On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
>>> 
 I have listen commented out - which means it listens on all IPs
 (doesn’t it?) - do I need to set them explicitly?
>>> 
>>> Try setting them explicitly, so that you can route them explicitly.
>>> 
 I did add mhomed=1 on this setup - but the calls went a bit crazy (I
 didn’t manage to capture quite what was happening).
>>> 
>>> Unfortunately, without knowing the specific facts, it's hard to
>>> speculate.
>>> 
>>> -- 
>>> Alex Balashov | Principal | Evariste Systems LLC
>>> 
>>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
>>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>> 
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> 
>> 
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity. 
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Oz Mortimer

Yeah 100%

So, I figured it might be something with DNS so I set auto_aliases=no but then 
get the following.

Nov  3 14:32:19 IS-56434 kamailio: INFO:  [tcp_main.c:4745]: init_tcp(): 
using epoll_lt as the io watch method (auto detected)
Nov  3 14:32:19 IS-56434 /usr/sbin/kamailio[13015]: WARNING: tm [tm.c:845]: 
mod_init(): WARNING: mod_init: reparse_on_dns_failover is enabled on a 
multihomed host -- check the readme of tm module!
Nov  3 14:32:19 IS-56434 /usr/sbin/kamailio[13015]: INFO: rr 
[../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob
Nov  3 14:32:19 IS-56434 /usr/sbin/kamailio[13015]: INFO: rr [rr_mod.c:160]: 
mod_init(): outbound module not available

Its worth noting all of the IPs are on the same adapter, i.e. eth0, eth0:0, 
eth0:1 and so on..



> On 3 Nov 2017, at 14:21, Alex Balashov  wrote:
> 
> Are you sure the IP is correct? 
> 
> On November 3, 2017 10:20:17 AM EDT, Oz Mortimer  wrote:
>> Ok - did that and got the same error, though this time I looked at what
>> it was;
>> Im /var/log/messages I see - 
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve
>> xxx.xxx.xxx.xxx
>> 
>> Although the IP address’ are correct...
>> 
>> 
>>> On 3 Nov 2017, at 14:06, Alex Balashov 
>> wrote:
>>> 
>>> On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
>>> 
 I have listen commented out - which means it listens on all IPs
 (doesn’t it?) - do I need to set them explicitly?
>>> 
>>> Try setting them explicitly, so that you can route them explicitly.
>>> 
 I did add mhomed=1 on this setup - but the calls went a bit crazy (I
 didn’t manage to capture quite what was happening).
>>> 
>>> Unfortunately, without knowing the specific facts, it's hard to
>>> speculate.
>>> 
>>> -- 
>>> Alex Balashov | Principal | Evariste Systems LLC
>>> 
>>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
>>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>> 
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> 
>> 
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> -- Alex
> 
> --
> Sent via mobile, please forgive typos and brevity. 
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] onreply_route block not processing replies

2017-11-03 Thread José Seabra

Hi Daniel,
That warning was written, it was my mistake, i didn't have noticed the
warning msg because of lot activity on logging regarding to number of calls
being processed.

Sorry for the noise :)

Thank you.

Best regards

2017-11-03 14:24 GMT+00:00 Daniel-Constantin Mierla :

> Hello,
>
> in such case there should be a warning log messages printed at startup if
> the ifdefs number is different than endif ... if it was not written, then I
> have to check why ...
> Cheers,
> Daniel
>
>
> On 03.11.17 14:54, José Seabra wrote:
>
> Hi there,
> I found the root cause of the problem reported on my last email.
>
> The reason for this problem, was that i had a wrong on #!endif tag, i
> wrote  #!enif instead of  #!endif and the kamailio during the restart
> didn't give an error, because i have anothers #!ifdef/#!endif tag.
>
> Regards
>
> 2017-11-03 11:21 GMT+00:00 José Seabra :
>
>> Hi there,
>> I'm facing an issue regarding with replies coming to kamailio that aren't
>> processes inside of onreply_route block.
>>
>> Anyone here can help me understand why these replies (1XX) aren't
>> entering on onreply_route bock? is there any situation already identified
>> on Kamailio that can originate this behavior?
>>
>> The Kamailio version used is 5.0.1.
>>
>> Thank you
>> Regards
>>
>> --
>> José Seabra
>>
>
>
>
> --
> Cumprimentos
> José Seabra
>
>
> ___
> Kamailio (SER) - Users Mailing 
> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com
> Kamailio World Conference - www.kamailioworld.com
>
>


-- 
Cumprimentos
José Seabra
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] onreply_route block not processing replies

2017-11-03 Thread Daniel-Constantin Mierla

Hello,

in such case there should be a warning log messages printed at startup
if the ifdefs number is different than endif ... if it was not written,
then I have to check why ...

Cheers,
Daniel

On 03.11.17 14:54, José Seabra wrote:
> Hi there,
> I found the root cause of the problem reported on my last email.
>
> The reason for this problem, was that i had a wrong on #!endif tag, i
> wrote  #!enif instead of  #!endif and the kamailio during the restart
> didn't give an error, because i have anothers #!ifdef/#!endif tag.
>
> Regards
>
> 2017-11-03 11:21 GMT+00:00 José Seabra  >:
>
> Hi there,
> I'm facing an issue regarding with replies coming to kamailio that
> aren't processes inside of onreply_route block.
>
> Anyone here can help me understand why these replies (1XX) aren't
> entering on onreply_route bock? is there any situation already
> identified on Kamailio that can originate this behavior?
>
> The Kamailio version used is 5.0.1.
>
> Thank you
> Regards
>
> -- 
> José Seabra
>
>
>
>
> -- 
> Cumprimentos
> José Seabra
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com
Kamailio World Conference - www.kamailioworld.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Alex Balashov

Are you sure the IP is correct? 

On November 3, 2017 10:20:17 AM EDT, Oz Mortimer  wrote:
>Ok - did that and got the same error, though this time I looked at what
>it was;
>Im /var/log/messages I see - 
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>Nov  3 14:13:28 IS-56434 kamailio: WARNING: 
>[socket_info.c:1392]: fix_hostname(): could not rev. resolve
>xxx.xxx.xxx.xxx
>
>Although the IP address’ are correct...
>
>
>> On 3 Nov 2017, at 14:06, Alex Balashov 
>wrote:
>> 
>> On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
>> 
>>> I have listen commented out - which means it listens on all IPs
>>> (doesn’t it?) - do I need to set them explicitly?
>> 
>> Try setting them explicitly, so that you can route them explicitly.
>> 
>>> I did add mhomed=1 on this setup - but the calls went a bit crazy (I
>>> didn’t manage to capture quite what was happening).
>> 
>> Unfortunately, without knowing the specific facts, it's hard to
>> speculate.
>> 
>> -- 
>> Alex Balashov | Principal | Evariste Systems LLC
>> 
>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>> 
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>___
>Kamailio (SER) - Users Mailing List
>sr-users@lists.kamailio.org
>https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Oz Mortimer

Ok - did that and got the same error, though this time I looked at what it was;
Im /var/log/messages I see - 
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx
Nov  3 14:13:28 IS-56434 kamailio: WARNING:  [socket_info.c:1392]: 
fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx

Although the IP address’ are correct...

> On 3 Nov 2017, at 14:06, Alex Balashov  wrote:
> 
> On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:
> 
>> I have listen commented out - which means it listens on all IPs
>> (doesn’t it?) - do I need to set them explicitly?
> 
> Try setting them explicitly, so that you can route them explicitly.
> 
>> I did add mhomed=1 on this setup - but the calls went a bit crazy (I
>> didn’t manage to capture quite what was happening).
> 
> Unfortunately, without knowing the specific facts, it's hard to
> speculate.
> 
> -- 
> Alex Balashov | Principal | Evariste Systems LLC
> 
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Alex Balashov

On Fri, Nov 03, 2017 at 02:04:37PM +, Oz Mortimer wrote:

> I have listen commented out - which means it listens on all IPs
> (doesn’t it?) - do I need to set them explicitly?

Try setting them explicitly, so that you can route them explicitly.

> I did add mhomed=1 on this setup - but the calls went a bit crazy (I
> didn’t manage to capture quite what was happening).

Unfortunately, without knowing the specific facts, it's hard to
speculate.

-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Oz Mortimer

I have listen commented out - which means it listens on all IPs (doesn’t it?) - 
do I need to set them explicitly?
I did add mhomed=1 on this setup - but the calls went a bit crazy (I didn’t 
manage to capture quite what was happening).

Thoughts?


> On 3 Nov 2017, at 13:59, Alex Balashov  wrote:
> 
> Hi,
> 
> 1. Do you have a listener (listen=) for all necessary IPs and transports?
> 
> 2. Outbound interface selection is done either via the 'mhomed' option, 
> 
> https://www.kamailio.org/wiki/cookbooks/5.0.x/core#mhomed
> 
> or, if it's not doing what you want, by manually steering it via $fs:
> 
> https://www.kamailio.org/wiki/cookbooks/5.0.x/pseudovariables#fs_-_forced_socket
> 
> -- Alex
> 
> -- 
> Alex Balashov | Principal | Evariste Systems LLC
> 
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
> 
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple IPs

2017-11-03 Thread Alex Balashov

Hi,

1. Do you have a listener (listen=) for all necessary IPs and transports?

2. Outbound interface selection is done either via the 'mhomed' option, 

https://www.kamailio.org/wiki/cookbooks/5.0.x/core#mhomed

or, if it's not doing what you want, by manually steering it via $fs:

https://www.kamailio.org/wiki/cookbooks/5.0.x/pseudovariables#fs_-_forced_socket

-- Alex

-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Multiple IPs

2017-11-03 Thread Oz Mortimer

Hi all,

I have Kamailio set as an SBC with freeswitch behind - that all works fine.
Freeswitch can send calls out VIA Kamailio to external IP address’, but if I 
try sending a call to another IP hosted by Kamailio the seems to go nowhere…

Supplier -> Kamailio  -> Customer1 -> Kamailio -> Customer2

The Kamailio server has multiple assigned IPs, which are used to multi-tennant 
- but I cant for the like of me to get Tennant to tenant calls to work (via 
freeswitch) 


Any pointers?


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] onreply_route block not processing replies

2017-11-03 Thread José Seabra

Hi there,
I found the root cause of the problem reported on my last email.

The reason for this problem, was that i had a wrong on #!endif tag, i
wrote  #!enif instead of  #!endif and the kamailio during the restart
didn't give an error, because i have anothers #!ifdef/#!endif tag.

Regards

2017-11-03 11:21 GMT+00:00 José Seabra :

> Hi there,
> I'm facing an issue regarding with replies coming to kamailio that aren't
> processes inside of onreply_route block.
>
> Anyone here can help me understand why these replies (1XX) aren't entering
> on onreply_route bock? is there any situation already identified on
> Kamailio that can originate this behavior?
>
> The Kamailio version used is 5.0.1.
>
> Thank you
> Regards
>
> --
> José Seabra
>



-- 
Cumprimentos
José Seabra
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Branching Kamailio v5.1

2017-11-03 Thread Daniel-Constantin Mierla

Hello,

I am planning to create the got branch 5.1 (to be used for v5.1.x
series) by end of next week (likely on Friday, Nov 10, 2017). After
that, the master will be open for new features and fixes will need to be
backported to 5.1.

Should anyone want a different schedule, reply to the mailing lists and
propose your plans.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com
Kamailio World Conference - www.kamailioworld.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] http_async_client problem with tls_ca_path

2017-11-03 Thread gmele

Ok, thx!

BTW, do you know if it is possible to build the http_async_client rpm on the
openSUSE download server?

The http_client is present, but not the http_async one


Regards


Giovanni



--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] http_async_client problem with tls_ca_path

2017-11-03 Thread Giacomo Vacca

OK Giovanni,
this is likely to be an issue with the way CURLOPT_CAPATH is set. I'll
submit a fix as soon as possible.

Giacomo

On 3 November 2017 at 09:49, gmele  wrote:

> Hello Giacomo,
>
> currently, I don't see these CURL warnings. Here are the logs I get using
> the verbose mode of Curl.
>
> When it works:
>
> Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL] About to connect()
> to pusher-service port 8443 (#1)
> Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL]   Trying
> 192.168.0.50...
> Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL] Connected to
> pusher-service (192.168.0.50) port 8443 (#1)
> *Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL]   CAfile:
> /etc/pki/tls/certs/ca-bundle.crt#012  CApath: /etc/kamailio/ssl/ca/*
> Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL] SSL connection
> using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
>
>
> When it doesn't work:
>
> Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL] About to connect()
> to pusher-service port 8443 (#0)
> Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL]   Trying
> 192.168.0.50...
> Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL] Connected to
> pusher-service (192.168.0.50) port 8443 (#0)
> *Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL] Initializing NSS
> with certpath: sql:/etc/pki/nssdb*
> Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
> http_async_client [http_multi.c:238]: debug_cb(): [cURL] Closing connection
> 0
> Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: ERROR:
> http_async_client [http_multi.c:570]: check_multi_info(): handle 0x1cf1b00
> returned error 77:
>
>
> Regards
>
> Giovanni
>
>
>
> --
> Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] onreply_route block not processing replies

2017-11-03 Thread José Seabra

Hi there,
I'm facing an issue regarding with replies coming to kamailio that aren't
processes inside of onreply_route block.

Anyone here can help me understand why these replies (1XX) aren't entering
on onreply_route bock? is there any situation already identified on
Kamailio that can originate this behavior?

The Kamailio version used is 5.0.1.

Thank you
Regards

-- 
José Seabra
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] http_async_client problem with tls_ca_path

2017-11-03 Thread gmele

Hello Giacomo,

currently, I don't see these CURL warnings. Here are the logs I get using
the verbose mode of Curl.

When it works:

Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL] About to connect()
to pusher-service port 8443 (#1)
Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL]   Trying
192.168.0.50...
Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL] Connected to
pusher-service (192.168.0.50) port 8443 (#1)
*Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL]   CAfile:
/etc/pki/tls/certs/ca-bundle.crt#012  CApath: /etc/kamailio/ssl/ca/*
Nov  3 08:41:46 d-wn-sipregistrar-003 kamailio-registrar[18948]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL] SSL connection
using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384


When it doesn't work:

Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL] About to connect()
to pusher-service port 8443 (#0)
Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL]   Trying
192.168.0.50...
Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL] Connected to
pusher-service (192.168.0.50) port 8443 (#0)
*Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL] Initializing NSS
with certpath: sql:/etc/pki/nssdb*
Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: INFO:
http_async_client [http_multi.c:238]: debug_cb(): [cURL] Closing connection
0
Nov  3 08:43:44 d-wn-sipregistrar-003 kamailio-registrar[18949]: ERROR:
http_async_client [http_multi.c:570]: check_multi_info(): handle 0x1cf1b00
returned error 77:


Regards

Giovanni



--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] WebRTC error code 488 in iOS application

2017-11-03 Thread Denys Pozniak

Hello!

Maybe it will be useful for somebody, I applied next configuration and iOS
starts working.


modparam("rtpengine", "write_sdp_pv", "$avp(sdp)")

rtpengine_manage("trust-address replace-origin replace-session-connection
rtcp-mux-offer rtcp-mux-accept media-handover ICE=force RTP/SAVPF");
set_body("$avp(sdp)", "application/sdp");

$avp(sdp) = $(avp(sdp){re.subst,/t=0 0/t=0 0\r\na=group:BUNDLE audio/g});
$avp(sdp) =
$(avp(sdp){re.subst,/a=setup:actpass/a=setup:actpass\r\na=mid:audio/g});
set_body("$avp(sdp)", "application/sdp");

BR,
Denys




On 31 October 2017 at 16:57, Denys Pozniak 
wrote:

> Hello!
>
> Probably this case is not connected Kamailio directly, but it can be
> somebody will point me in the correct direction :)
>
> We have VoIP solution: FreeSWITCH -> Kamailio + Rtpengine -> WebRTC Chrome.
> Everything works Ok except iOS application based on React Native WebRTC (
> https://github.com/oney/react-native-webrtc) + JsSIP.
> It answers error 488 on incoming INVITE (wSDP):
>
> INVITE SDP to iOS:
>
> *..*
> *v=0*
> *o=FreeSWITCH 1508701860 1508701861 IN IP4 52.52.52.52*
> *s=FreeSWITCH*
> *c=IN IP4 52.52.52.52*
> *t=0 0*
> *m=audio 30028 RTP/SAVPF 0 8 102*
> *a=rtpmap:0 PCMU/8000*
> *a=rtpmap:8 PCMA/8000*
> *a=rtpmap:102 opus/48000/2*
> *a=fmtp:102 useinbandfec=1; maxaveragebitrate=14400; maxplaybackrate=8000;
> ptime=20; minptime=10; maxptime=40*
> *a=ptime:20*
> *a=sendrecv*
> *a=rtcp:30028*
> *a=rtcp-mux*
> *a=setup:actpass*
> *a=fingerprint:sha-1
> 97:1A:E9:FE:D6:65:98:E6:88:EE:D5:9F:20:A3:19:F8:86:E7:E0:E3*
> *a=ice-ufrag:9QBO8qg2*
> *a=ice-pwd:PPGPo35xGBAs6RnTdMYVM9I8fx*
> *a=candidate:KXENzrffZpQvwxdV 1 UDP 2130706431 52.52.52.52 30028 typ host*
>
>
> iOS console log:
>
>
> *11:55:23.670 browser.js:133 JsSIP:WebSocketInterface send() +10ms*
> *11:55:23.670 browser.js:133 JsSIP:RTCSession session progress +5ms*
> *11:55:23.671 browser.js:133 JsSIP:RTCSession emit "progress" +1ms*
> *11:55:23.671 webrtc.js:108 WebRTC.on progress:  local*
> *11:55:23.679 browser.js:133 JsSIP:RTCSession emit "peerconnection" +8ms*
> *11:55:23.680 webrtc.js:89 WebRTC.on peerconnection*
> *11:55:23.680 browser.js:133 JsSIP:RTCSession emit "sdp" +1ms*
> *11:55:23.689 browser.js:133 JsSIP:Transport send() +20ms**11:55:23.689
> browser.js:133 JsSIP:Transport sending message:*
> *SIP/2.0 488 Not Acceptable Here*
> *11:55:23.701 debug.js:115 JsSIP:ERROR:RTCSession emit
> "peerconnection:setremotedescriptionfailed" [error:Error: Failed to set
> remote offer sdp: Failed to create channels.*
>
>
>
> I found similar issue on thier git https://github.com/oney/
> react-native-webrtc/issues/293 and main solution is to struct SDP in way
> like:
>
>
>
> *a=group:BUNDLE audiom=audio PORT RTP/SAVPF N M Ka=mid:audio*
>
>
> How to modify SDP on Kamailio side (after Rtpengine modification) like
> below?
>
>
> *v=0*
> *o=FreeSWITCH 1508701860 1508701861 IN IP4 52.52.52.52*
> *s=FreeSWITCH*
> *c=IN IP4 52.52.52.52*
> *t=0 0*
> *a=group:BUNDLE audio*
> *m=audio 30028 RTP/SAVPF 0 8 102*
> *a=rtpmap:0 PCMU/8000*
> *a=rtpmap:8 PCMA/8000*
> *a=rtpmap:102 opus/48000/2*
> *a=fmtp:102 useinbandfec=1; maxaveragebitrate=14400; maxplaybackrate=8000;
> ptime=20; minptime=10; maxptime=40*
> *a=ptime:20*
> *a=sendrecv*
> *a=rtcp:30028*
> *a=rtcp-mux*
> *a=setup:actpass*
> *a=mid:audio*
> *a=fingerprint:sha-1
> 97:1A:E9:FE:D6:65:98:E6:88:EE:D5:9F:20:A3:19:F8:86:E7:E0:E3*
> *a=ice-ufrag:9QBO8qg2*
> *a=ice-pwd:PPGPo35xGBAs6RnTdMYVM9I8fx*
> *a=candidate:KXENzrffZpQvwxdV 1 UDP 2130706431 52.52.52.52 30028 typ host*
>
>
>
> BR,
> Denys
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] no event received for call disconnection

2017-11-03 Thread Daniel-Constantin Mierla

Hello,

can you try with latest master? I just pushed a patch that should handle
this case. Let me know if works or not.

Cheers,
Daniel


On 01.11.17 11:57, Aleksandar Sosic wrote:
> Thank you Daniel!
> --
> Aleksandar Sosic
> mail: alex.so...@timenet.it
> skype: alex.sosic
> cell: +385 91 2505 146
>
>
> On Wed, Nov 1, 2017 at 10:39 AM, Daniel-Constantin Mierla
>  wrote:
>> Hello,
>>
>> ok, now the cfg execution flow is easier to understand. The evapi
>> receiver was not designed to write back directly, I will try to find a
>> solution for this case.
>>
>> Cheers,
>> Daniel
>>
>> On 31.10.17 15:03, Aleksandar Sosic wrote:
>>> Hi Daniel,
>>>
>>> so the kamailio.conf sections that matters are here:
>>> https://gist.github.com/alexsosic/5a33d314d2db1832fd04166fe6615227
>>>
>>> Thanks for your time!
>>> --
>>> Aleksandar Sosic
>>> mail: alex.so...@timenet.it
>>> skype: alex.sosic
>>> cell: +385 91 2505 146
>>>
>>>
>>> On Tue, Oct 31, 2017 at 12:51 PM, Daniel-Constantin Mierla
>>>  wrote:
 It is a bit hard to guess the logic you have there, but seems like
 cgrates sends a disconnect request via event api, which via some actions
 triggers a dialog end, which then wants to send back an event to cgrates
 that call is ending? Like a loop back communication with evapi receiver ...

 Maybe you can share the config file (or the relevant parts).

 Cheers,
 Daniel

 On 31.10.17 12:18, Aleksandar Sosic wrote:
> 17(114) NOTICE: evapi [evapi_dispatch.c:339]: evapi_recv_client(): {0}
> [127.0.0.1:41154] - received
> [99:{"Event":"CGR_SESSION_DISCONNECT","HashEntry":"715","HashId":"1885","Reason":"-INSUFFICIENT_FUNDS"},]
> (103) (0)
>
> It seems like an evapi recieved command.
> That triggers that route.
>
> After that I do have this errors in kamailio logs:
> 17(114) ERROR:  [core/parser/parse_from.c:107]:
> parse_from_uri(): failed to parse From uri
> 17(114) ERROR: pv [pv_core.c:414]: pv_get_xto_attr(): cannot parse From 
> URI
> 17(114) ERROR:  [core/parser/parse_to.c:81]: parse_to_uri():
> failed to parse To uri
> 17(114) ERROR: pv [pv_core.c:408]: pv_get_xto_attr(): cannot parse To URI
> --
> Aleksandar Sosic
> mail: alex.so...@timenet.it
> skype: alex.sosic
> cell: +385 91 2505 146
>
>
> On Tue, Oct 31, 2017 at 12:04 PM, Daniel-Constantin Mierla
>  wrote:
>> Hello,
>>
>> when is the route[CGR_SESSION_DISCONNECT] executed? In other words,
>> where do you have route(CGR_SESSION_DISCONNECT) in your config or is
>> there any modparam with CGR_SESSION_DISCONNECT in it?
>>
>> Cheers,
>> Daniel
>>
>>
>> On 31.10.17 11:45, Aleksandar Sosic wrote:
>>> Hi Daniel,
>>>
>>> It's done by this cgrates route:
>>> ```
>>> # CGRateS request for session disconnect
>>> route[CGR_SESSION_DISCONNECT] {
>>>   json_get_field("$evapi(msg)", "HashEntry", "$var(HashEntry)");
>>>   json_get_field("$evapi(msg)", "HashId", "$var(HashId)");
>>>   json_get_field("$evapi(msg)", "Reason", "$var(Reason)");
>>>   jsonrpc_exec('{"jsonrpc":"2.0","id":1,
>>> "method":"dlg.end_dlg","params":[$(var(HashEntry){s.rm,"}),$(var(HashId){s.rm,"})]}');
>>> }
>>> ```
>>>
>>> It executes a dlg.end_dlg via jsonrpc.
>>> --
>>> Aleksandar Sosic
>>> mail: alex.so...@timenet.it
>>> skype: alex.sosic
>>> cell: +385 91 2505 146
>>>
>>>
>>> On Mon, Oct 30, 2017 at 5:57 PM, Daniel-Constantin Mierla
>>>  wrote:
 Hello,


 On 30.10.17 17:29, Aleksandar Sosic wrote:
> Hi Everyone,
>
> we're trying to implement cgrates in our kamailio nodes.
> Everything is working fine except for the fact that kamailio is not
> signaling the call end to cgrates for prepaid users... The versions,
> logs and confs are:
>
> ```
> # kamailio -v
> version: kamailio 5.0.3 (x86_64/linux)
> flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS,
> DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
> Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX,
> FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR,
> USE_DST_BLACKLIST, HAVE_RESOLV_RES
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: unknown
> compiled with gcc 5.3.1
> ```
>
> ```
> # cgr-engine --version
> CGRateS 0.9.1~rc8 git+15a0793 (2017-10-23T12:15:40+02:00)
> ```
>
> The kamailio conf regarding our problem is:
> ```
> #

Re: [SR-Users] User Registration with location awareness

2017-11-03 Thread Alex Balashov

Hello Daisy,

One option is to use usrloc with db_mode 3, which will allow you to share the 
location table between two registrars using a shared database table. It would 
then be possible to do registrar lookup() on one server and determine, by way 
of the 'socket' attribute, that the registration is in fact homed on the other 
server. You could then route the call through that server laterally, e.g. using 
special logic where incoming invites from the other proxy are trusted and 
subjected to a further lookup() on the receiving registrar.

There are, of course, a variety of other options as well, including using 
dmq_usrloc or distribution registration location hints using a DMQ-shared 
'htable'. 

-- Alex

-- Alex

--
Sent via mobile, please forgive typos and brevity. 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Tcp socket error with active/active kamailio schema

2017-11-03 Thread Donat Zenichev

Hi guys.

I'm trying to realize active/active schema with kamailio.
Topology is as following:
active/active kamailio -> routing server (asterisk)

Kamailio servers work as registrar/location servers and sbc.
Asterisk server performs routing functions for calls.

We use sip / sips / ws / wss for signaling.

Schema built on aws platform and both kamailio have virtual ip address.
So when first kamailio crashes, second one assigns ip address of first
kamailio. And vice-versa.

Both kamailio listens on both shared addresses all the time (with help of
sysctl non lolcal bind function).

Problem occurs when first kamailio goes down and second kamailio gets ip
address of first one. Asterisk tries to send in-dialog requests (for
dialogs that were established on first kamailio), request goes to second
kamailio and asterisk gets a socket error.

And this is proper behaviour I think, because first kamailio established
tcp connection with asterisk from certain port, that is not listened on
second kamailio.

So that, I think that the solution is to use force_send_socket function,
but I'm not confident about it.
If anyone has ideas, please send your advices.
Thanks in advance.






-- 
-- 
BR, Donat Zenichev
Wnet VoIP team
Tel:  +380(44) 5-900-808
http://wnet.ua


Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] User Registration with location awareness

2017-11-03 Thread Daisy Stevens

Hi Guys

Please forgive me if I seem to asking stupid questions but I am a complete 
dummy at the moment regarding this software.

I would love to be able to set up two kamailio servers with the idea of 
expansion in the future to handle SIP registrations, however having a two 
server model how would I get the calls to route to another user that is 
registered on the other kamailio box?

Kind Regards

Daisy

-- 





CONFIDENTIAL EMAIL FROM NETCALL TELECOM LIMITED

This email, and any attachments, is intended only for the above addressee. 
It may contain private and/or confidential information. If you have 
received this email in error you are on notice of its status, please 
immediately notify the sender by return email then delete this message and 
any attachments. If you are not the addressee, except to notify the sender, 
you must not use, disclose, copy or distribute this email and/or its 
attachments. Netcall Telecom accepts no responsibility for any changes made 
to this message after it has been sent by the original author. Opinions or 
views expressed in this email may be those of the individual sender and not 
Netcall Telecom. Nothing in this email shall bind Netcall Telecom in any 
contract or obligation

Netcall Telecom Ltd Registered in England 2831215. Registered Office : 3rd 
Floor, Hamilton House, 111 Marlowes, Hemel Hempstead, Herts, HP1 1BB
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] msilo Content-Type for picture and video?

2017-11-03 Thread sscc

Hello kamailio folks 

i am successfully storing and dumping messages for off line users using
msilo content type text/plain. 


i want to store off-line messages for pictures and videos.

my particular queries are

1) is msilo store picture and videos?  (i have observed blob in silo
database table which is used for pictures.
2) in case it does what will be declared in content type hdr parameter?

any help in this regard will highly be appreciated.

regards,

sscc



--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Invalid JSON when dumping htable with JSONRPC-S

Re: [SR-Users] Contacts in 302

Re: [SR-Users] Contacts in 302

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] onreply_route block not processing replies

Re: [SR-Users] onreply_route block not processing replies

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

Re: [SR-Users] Multiple IPs

[SR-Users] Multiple IPs

Re: [SR-Users] onreply_route block not processing replies

[SR-Users] Branching Kamailio v5.1

Re: [SR-Users] http_async_client problem with tls_ca_path

Re: [SR-Users] http_async_client problem with tls_ca_path

[SR-Users] onreply_route block not processing replies

Re: [SR-Users] http_async_client problem with tls_ca_path

Re: [SR-Users] WebRTC error code 488 in iOS application

Re: [SR-Users] no event received for call disconnection

Re: [SR-Users] User Registration with location awareness

[SR-Users] Tcp socket error with active/active kamailio schema

[SR-Users] User Registration with location awareness

[SR-Users] msilo Content-Type for picture and video?

31 matches

Site Navigation

Mail list logo

Footer information