Re: [OpenSIPS-Users] Can I use loop back when there is no network link ?

[Jeff Pyle]

Rodrigo,

I've run OpenSIPS on the loopback interface to talk to other SIP-speaking
entities on the same system.  I haven't had any problems.

If your co-workers' project has OpenSIPS and a softphone, with no network
connectivity, who are they going to call?



- Jeff



On Fri, Apr 29, 2016 at 2:37 PM, Rodrigo Pimenta Carvalho  wrote:

> Hi.
>
>
> Some co-workers are today creating a project that will use OpenSIPS and a
> softphone. All in a same hardware. That is, they want to put the softphone
> communicating with the SIP proxy without any network interface or link.
> That is, there will not be a network interface from where OpenSIPS could
> listen to UPD or TCP packets. In this case, they intend to use a kind of
> loop back. So, in the opensips.cfg file they intend to write "lo" in spite
> of "eth0" or "wlan0". But, doing it, the OpenSIPS doesn't works when it
> receives a SIP INVITE, for example.
>
>
> So, what is the best way to run OpenSIPS and let it listen to a kind of
> loop back interface?
>
>
> Any hint will be very helpful!
>
>
> Best regards.
>
>
> RODRIGO PIMENTA CARVALHO
> Inatel Competence Center
> Software
> Ph: +55 35 3471 9200 RAMAL 979
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Can I use loop back when there is no network link ?

[Rodrigo Pimenta Carvalho]

Hi.


Some co-workers are today creating a project that will use OpenSIPS and a 
softphone. All in a same hardware. That is, they want to put the softphone 
communicating with the SIP proxy without any network interface or link. That 
is, there will not be a network interface from where OpenSIPS could listen to 
UPD or TCP packets. In this case, they intend to use a kind of loop back. So, 
in the opensips.cfg file they intend to write "lo" in spite of "eth0" or 
"wlan0". But, doing it, the OpenSIPS doesn't works when it receives a SIP 
INVITE, for example.


So, what is the best way to run OpenSIPS and let it listen to a kind of loop 
back interface?


Any hint will be very helpful!


Best regards.


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Selective logging

[John Nash]

OK thank you.

On Fri, Apr 29, 2016 at 9:59 PM, Bogdan-Andrei Iancu 
wrote:

> You can force whatever log level you want via xlog :
> http://www.opensips.org/Documentation/Script-CoreFunctions-1-11#toc56
>
> Use L_ALERT to get them all the time :)
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 29.04.2016 19:26, John Nash wrote:
>
> OK.  Any way to use Xlog to print DBG messages even if script has debug
> level as ERR ?
>
> On Fri, Apr 29, 2016 at 9:29 PM, Bogdan-Andrei Iancu <
> bog...@opensips.org> wrote:
>
>> Hi Nash,
>>
>> You can do a small route in your script for logging to combine filtering
>> (maybe based on src address check or dialplan for usernames or acls, etc)
>> and xlog() :
>>
>> route[my_xlog]
>> {
>> if ( check_source_address("10") )
>> xlog("DBG: $si: $param(1) \n");
>> }
>>
>> And call it as:
>>
>> route(my_xlog,"this is just a simple log");
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 29.04.2016 14:22, John Nash wrote:
>>
>> Is there any way to log messages (Custom messages and SIP trace) from
>> script for a given parameter say IP or ruri.
>>
>> A crude way can be to store say user in local cache and match with the
>> user in script and log else pass but ..
>>
>> 1- I am not sure if any other smart way to do it
>> 2- How can I dunp SIP messages
>>
>>
>>
>>
>> ___
>> Users mailing 
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Selective logging

[Bogdan-Andrei Iancu]

You can force whatever log level you want via xlog :
http://www.opensips.org/Documentation/Script-CoreFunctions-1-11#toc56

Use L_ALERT to get them all the time :)

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 29.04.2016 19:26, John Nash wrote:
OK.  Any way to use Xlog to print DBG messages even if script has 
debug level as ERR ?


On Fri, Apr 29, 2016 at 9:29 PM, Bogdan-Andrei Iancu 
> wrote:


Hi Nash,

You can do a small route in your script for logging to combine
filtering (maybe based on src address check or dialplan for
usernames or acls, etc) and xlog() :

route[my_xlog]
{
if ( check_source_address("10") )
xlog("DBG: $si: $param(1) \n");
}

And call it as:

route(my_xlog,"this is just a simple log");

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 29.04.2016 14:22, John Nash wrote:

Is there any way to log messages (Custom messages and SIP trace)
from script for a given parameter say IP or ruri.

A crude way can be to store say user in local cache and match
with the user in script and log else pass but ..

1- I am not sure if any other smart way to do it
2- How can I dunp SIP messages



___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Selective logging

[Bogdan-Andrei Iancu]

Hi Nash,

You can do a small route in your script for logging to combine filtering 
(maybe based on src address check or dialplan for usernames or acls, 
etc) and xlog() :


route[my_xlog]
{
if ( check_source_address("10") )
xlog("DBG: $si: $param(1) \n");
}

And call it as:

route(my_xlog,"this is just a simple log");

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 29.04.2016 14:22, John Nash wrote:
Is there any way to log messages (Custom messages and SIP trace) from 
script for a given parameter say IP or ruri.


A crude way can be to store say user in local cache and match with the 
user in script and log else pass but ..


1- I am not sure if any other smart way to do it
2- How can I dunp SIP messages



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Regarding siptrace module .

[Ali Ariyayi]

please please do not send any mail for me.
please please do not send 
do you understand ? 

On Friday, April 29, 2016 7:40 PM, Sasmita Panda  wrote:
 

 Yes . From last 8 year we are using opensips . And its working like this . 
I am sorry but this is true .If your are saying this is not right . The what is 
the right way , so that we can use multiple interfaces . 
Let me know the right way so that I can go forward and correct it . 
Thanks & RegardsSasmita PandaNetwork Testing and Software Engineer3CLogic , 
ph:07827611765
On Fri, Apr 29, 2016 at 8:24 PM, Benjamin Cropley  
wrote:

Sasmita,
Does you config LITERALLY say.. listen=0.0.0.0:5506 AS 54.211.x.y:5506 ??
..


On Fri, Apr 29, 2016 at 3:30 PM, Sasmita Panda  wrote:

Then what IP will I set there . We are running like this and there is no 
problem we are facing yet .
I cant put the public ip over there . If I will put the private ip then While 
forwarding HEP packets to any other IP it wont work .
There is an option I will set only the port=5506 and so that it will work on 
all the interfaces (public and private ) .
But giving the port , I am facing another problem . If there is more than one 
port then how will I give multiple ports ? 
Thanks & RegardsSasmita PandaNetwork Testing and Software Engineer3CLogic , 
ph:07827611765
On Fri, Apr 29, 2016 at 7:20 PM, Bogdan-Andrei Iancu  
wrote:

  Hi Sasmita,
 
 OpenSIPS does not support 0.0.0.0 IP. You need to have an explicit IP there.
 
 Regards,
  Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com On 29.04.2016 11:46, Sasmita Panda wrote:
  
 Hi All , 
       I am trying to integrate HOMER with opensips . I am using opensips as my 
capture agent and forwarding the HEP packets to the capture server which is 
kamailio . 
        My opensips is running on AWS EMI . Where there is a public and a 
private IP of the machine . So we used to writein the bellow format in the 
opensips config . 
  "listen=0.0.0.0:5506 AS 54.211.x.y:5506 "
  
         Second part is the public ip , and that get used for publishing any 
message out side . the first part is for internal use . With this if I am 
trying to forward the HEP packet through siptrace module , I had configured 
like bellow . 
   #load siptrcae module for trace node --- modparam("siptrace", 
"duplicate_uri", "sip:107.170.x.y:9060") modparam("siptrace", 
"duplicate_with_hep", 1) modparam("siptrace", "trace_to_database", 0) 
modparam("siptrace", "trace_flag", 22) modparam("siptrace", "trace_on", 1) 
#HEPv2 == timestamp will be included to HEP header modparam("siptrace", 
"hep_version", 2)           In "107.170.x.y:9060" my kamailio is running . But 
when I am trying to forward the packets its giving error . 
  "ERROR:siptrace:pipport2su: host <0.0.0.0> is not an IP"  .        
            If I am changing my opensips config to "listen=54.211.x.y:5506 AS 
54.211.x.y:5506 " then its running fine . 
  
        How will I get read of this error without changing my listen IP and 
port line ? Is there anything I can do in the siptrace module to use the public 
ip only rather than using " 0.0.0.0 " ? 
  
Thanks & Regards Sasmita Panda Network Testing and Software Engineer 
3CLogic , ph:07827611765 
  
 ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
 
 
 


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


  ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Regarding siptrace module .

[Sasmita Panda]

Yes . From last 8 year we are using opensips . And its working like this .

I am sorry but this is true .If your are saying this is not right . The
what is the right way , so that we can use multiple interfaces .

Let me know the right way so that I can go forward and correct it .

*Thanks & Regards*
*Sasmita Panda*
*Network Testing and Software Engineer*
*3CLogic , ph:07827611765*

On Fri, Apr 29, 2016 at 8:24 PM, Benjamin Cropley <
benjamin.crop...@gmail.com> wrote:

> Sasmita,
>
> Does you config LITERALLY say.. *listen=0.0.0.0:5506
>  AS 54.211.x.y:5506 *??
>
> ..
>
>
>
> On Fri, Apr 29, 2016 at 3:30 PM, Sasmita Panda  wrote:
>
>> Then what IP will I set there . We are running like this and there is no
>> problem we are facing yet .
>>
>> I cant put the public ip over there . If I will put the private ip then
>> While forwarding HEP packets to any other IP it wont work .
>>
>> There is an option I will set only the port=5506 and so that it will work
>> on all the interfaces (public and private ) .
>>
>> But giving the port , I am facing another problem . If there is more than
>> one port then how will I give multiple ports ?
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>> On Fri, Apr 29, 2016 at 7:20 PM, Bogdan-Andrei Iancu > > wrote:
>>
>>> Hi Sasmita,
>>>
>>> OpenSIPS does not support 0.0.0.0 IP. You need to have an explicit IP
>>> there.
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>>
>>> On 29.04.2016 11:46, Sasmita Panda wrote:
>>>
>>> Hi All ,
>>>
>>>  I am trying to integrate HOMER with opensips . I am using opensips
>>> as my capture agent and forwarding the HEP packets to the capture server
>>> which is kamailio .
>>>
>>>   My opensips is running on AWS EMI . Where there is a public and a
>>> private IP of the machine . So we used to writein the bellow format in the
>>> opensips config .
>>>
>>>
>>> *"listen=0.0.0.0:5506  AS 54.211.x.y:5506 " *
>>>
>>>Second part is the public ip , and that get used for publishing
>>> any message out side . the first part is for internal use .
>>> With this if I am trying to forward the HEP packet through siptrace
>>> module , I had configured like bellow .
>>>
>>> #load siptrcae module for trace node ---
>>> modparam("siptrace", "duplicate_uri", "sip:107.170.x.y:9060")
>>> modparam("siptrace", "duplicate_with_hep", 1)
>>> modparam("siptrace", "trace_to_database", 0)
>>> modparam("siptrace", "trace_flag", 22)
>>> modparam("siptrace", "trace_on", 1)
>>> #HEPv2 == timestamp will be included to HEP header
>>> modparam("siptrace", "hep_version", 2)
>>>
>>>In "107.170.x.y:9060" my kamailio is running . But when I am
>>> trying to forward the packets its giving error .
>>>
>>> *"ERROR:siptrace:pipport2su: host <0.0.0.0> is not an IP"  . *
>>>
>>>   If I am changing my opensips config to *"listen=**54.211.x.y:5506
>>> AS **54.211.x.y:5506 " *then its running fine .
>>>
>>>
>>>   How will I get read of this error without changing my listen IP
>>> and port line ?
>>> Is there anything I can do in the siptrace module to use the public ip
>>> only rather than using " *0.0.0.0* " ?
>>>
>>>
>>> *Thanks & Regards*
>>> *Sasmita Panda*
>>> *Network Testing and Software Engineer*
>>> *3CLogic , ph:07827611765*
>>>
>>>
>>> ___
>>> Users mailing 
>>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Regarding siptrace module .

[Benjamin Cropley]

Sasmita,

Does you config LITERALLY say.. *listen=0.0.0.0:5506
 AS 54.211.x.y:5506 *??

..



On Fri, Apr 29, 2016 at 3:30 PM, Sasmita Panda  wrote:

> Then what IP will I set there . We are running like this and there is no
> problem we are facing yet .
>
> I cant put the public ip over there . If I will put the private ip then
> While forwarding HEP packets to any other IP it wont work .
>
> There is an option I will set only the port=5506 and so that it will work
> on all the interfaces (public and private ) .
>
> But giving the port , I am facing another problem . If there is more than
> one port then how will I give multiple ports ?
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
> On Fri, Apr 29, 2016 at 7:20 PM, Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Sasmita,
>>
>> OpenSIPS does not support 0.0.0.0 IP. You need to have an explicit IP
>> there.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 29.04.2016 11:46, Sasmita Panda wrote:
>>
>> Hi All ,
>>
>>  I am trying to integrate HOMER with opensips . I am using opensips
>> as my capture agent and forwarding the HEP packets to the capture server
>> which is kamailio .
>>
>>   My opensips is running on AWS EMI . Where there is a public and a
>> private IP of the machine . So we used to writein the bellow format in the
>> opensips config .
>>
>>
>> *"listen=0.0.0.0:5506  AS 54.211.x.y:5506 " *
>>
>>Second part is the public ip , and that get used for publishing
>> any message out side . the first part is for internal use .
>> With this if I am trying to forward the HEP packet through siptrace
>> module , I had configured like bellow .
>>
>> #load siptrcae module for trace node ---
>> modparam("siptrace", "duplicate_uri", "sip:107.170.x.y:9060")
>> modparam("siptrace", "duplicate_with_hep", 1)
>> modparam("siptrace", "trace_to_database", 0)
>> modparam("siptrace", "trace_flag", 22)
>> modparam("siptrace", "trace_on", 1)
>> #HEPv2 == timestamp will be included to HEP header
>> modparam("siptrace", "hep_version", 2)
>>
>>In "107.170.x.y:9060" my kamailio is running . But when I am
>> trying to forward the packets its giving error .
>>
>> *"ERROR:siptrace:pipport2su: host <0.0.0.0> is not an IP"  . *
>>
>>   If I am changing my opensips config to *"listen=**54.211.x.y:5506
>> AS **54.211.x.y:5506 " *then its running fine .
>>
>>
>>   How will I get read of this error without changing my listen IP and
>> port line ?
>> Is there anything I can do in the siptrace module to use the public ip
>> only rather than using " *0.0.0.0* " ?
>>
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>>
>> ___
>> Users mailing 
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Regarding siptrace module .

[Sasmita Panda]

Then what IP will I set there . We are running like this and there is no
problem we are facing yet .

I cant put the public ip over there . If I will put the private ip then
While forwarding HEP packets to any other IP it wont work .

There is an option I will set only the port=5506 and so that it will work
on all the interfaces (public and private ) .

But giving the port , I am facing another problem . If there is more than
one port then how will I give multiple ports ?

*Thanks & Regards*
*Sasmita Panda*
*Network Testing and Software Engineer*
*3CLogic , ph:07827611765*

On Fri, Apr 29, 2016 at 7:20 PM, Bogdan-Andrei Iancu 
wrote:

> Hi Sasmita,
>
> OpenSIPS does not support 0.0.0.0 IP. You need to have an explicit IP
> there.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 29.04.2016 11:46, Sasmita Panda wrote:
>
> Hi All ,
>
>  I am trying to integrate HOMER with opensips . I am using opensips as
> my capture agent and forwarding the HEP packets to the capture server which
> is kamailio .
>
>   My opensips is running on AWS EMI . Where there is a public and a
> private IP of the machine . So we used to writein the bellow format in the
> opensips config .
>
>
> *"listen=0.0.0.0:5506  AS 54.211.x.y:5506 " *
>
>Second part is the public ip , and that get used for publishing any
> message out side . the first part is for internal use .
> With this if I am trying to forward the HEP packet through siptrace module
> , I had configured like bellow .
>
> #load siptrcae module for trace node ---
> modparam("siptrace", "duplicate_uri", "sip:107.170.x.y:9060")
> modparam("siptrace", "duplicate_with_hep", 1)
> modparam("siptrace", "trace_to_database", 0)
> modparam("siptrace", "trace_flag", 22)
> modparam("siptrace", "trace_on", 1)
> #HEPv2 == timestamp will be included to HEP header
> modparam("siptrace", "hep_version", 2)
>
>In "107.170.x.y:9060" my kamailio is running . But when I am trying
> to forward the packets its giving error .
>
> *"ERROR:siptrace:pipport2su: host <0.0.0.0> is not an IP"  . *
>
>   If I am changing my opensips config to *"listen=**54.211.x.y:5506
> AS **54.211.x.y:5506 " *then its running fine .
>
>
>   How will I get read of this error without changing my listen IP and
> port line ?
> Is there anything I can do in the siptrace module to use the public ip
> only rather than using " *0.0.0.0* " ?
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Re-Invite routed to private IP

[Julian Santer]

Ok. I read the OpenSips doc of force_rport again:
Force_rport() adds the rport parameter to the first Via header. Thus, OpenSIPS will add the received IP port to the top most via header in the SIP 
message, even if the client does not indicate support for rport. This enables subsequent SIP messages to return to the proper port later on in a SIP 
transaction.


I misunderstand th "received IP port" maybe ;-)

But we didn't have this problems before changing the platform.

The Re-Invite enters here, and as I saw in syslog, the topology_hiding matches 
and also the uac_test is be done:

if (has_totag())
{
if (topology_hiding_match())
{
if (nat_uac_test("127"))
{
xlog("L_INFO", "Topology hided, Contact fixed - LF_BASE");
fix_nated_contact();
}

t_relay();
exit;
}

Am 29.04.2016 um 15:56 schrieb Johan De Clercq:

I don;t think so : force_rport just adds the port on which you receive to the 
first via header.

2016-04-29 15:36 GMT+02:00 Julian Santer >:

We are using 2.1.2
So we made a "huge" version update and also changed the kind of working

Am 29.04.2016 um 14:27 schrieb Johan De Clercq:

What version do you use in your new install ?

2016-04-29 13:12 GMT+02:00 Julian Santer 
>>:

 Hi Johan,

 we changed our platform 2 weeks ago from 1 OpenSips Proxy 1.6.4 to 
3 OpenSips instances with topology hiding.
 Since we didn't have this problems earlier, I think it worked with 
the old platform.
 As we call force_rport() in the main_route, the private IP in the 
VIA header should be ignored, right?
 At the moment we call force_rport() in all our instances.
 I think, we should call force_rport() only on the edge server 
where we make the nat_handling, right?

 Kind regards,
 Julian Santer
 Raiffeisen OnLIne


 Am 29.04.2016 um 10:10 schrieb Johan De Clercq:

 Indeed.


 2016-04-29 9:49 GMT+02:00 Julian Santer 
>
   >
  >>
  
>

 :

   Hi guys,

   we are using OpenSips 2.1.2 with topology_hiding.
   Now we got trouble with Re-Invites, which are routed to 
the private IP from the "from".
   The topology_hiding matches, but the Re-Invite is sent to 
the private IP from the "from".
   Have we to call lookup again on the 
registrar/core, when we got a Re-Invite?
   You can find the trace under 
http://siptrace.rolbox.net/siptrace.html

   Kind regards,
   Julian Santer
   Raiffeisen OnLine


   ___
   Users mailing list
Users@lists.opensips.org 
>
 

Re: [OpenSIPS-Users] Regarding siptrace module .

[Bogdan-Andrei Iancu]

Hi Sasmita,

OpenSIPS does not support 0.0.0.0 IP. You need to have an explicit IP there.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 29.04.2016 11:46, Sasmita Panda wrote:

Hi All ,

 I am trying to integrate HOMER with opensips . I am using 
opensips as my capture agent and forwarding the HEP packets to the 
capture server which is kamailio .


  My opensips is running on AWS EMI . Where there is a public and 
a private IP of the machine . So we used to writein the bellow format 
in the opensips config .


*"listen=0.0.0.0:5506  AS 54.211.x.y:5506 "
*

   Second part is the public ip , and that get used for publishing 
any message out side . the first part is for internal use .
With this if I am trying to forward the HEP packet through siptrace 
module , I had configured like bellow .


#load siptrcae module for trace node ---
modparam("siptrace", "duplicate_uri", "sip:107.170.x.y:9060")
modparam("siptrace", "duplicate_with_hep", 1)
modparam("siptrace", "trace_to_database", 0)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "trace_on", 1)
#HEPv2 == timestamp will be included to HEP header
modparam("siptrace", "hep_version", 2)
   In "107.170.x.y:9060" my kamailio is running . But when I am 
trying to forward the packets its giving error .


*"ERROR:siptrace:pipport2su: host <0.0.0.0> is not an IP"  . *

  If I am changing my opensips config to 
*"listen=**54.211.x.y:5506 AS **54.211.x.y:5506 " *then its running fine .



  How will I get read of this error without changing my listen IP 
and port line ?
Is there anything I can do in the siptrace module to use the public ip 
only rather than using " *0.0.0.0* " ?



*/Thanks & Regards/*
/Sasmita Panda/
/Network Testing and Software Engineer/
/3CLogic , ph:07827611765/


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Re-Invite routed to private IP

[Johan De Clercq]

I don;t think so : force_rport just adds the port on which you receive to
the first via header.

2016-04-29 15:36 GMT+02:00 Julian Santer :

> We are using 2.1.2
> So we made a "huge" version update and also changed the kind of working
>
> Am 29.04.2016 um 14:27 schrieb Johan De Clercq:
>
>> What version do you use in your new install ?
>>
>> 2016-04-29 13:12 GMT+02:00 Julian Santer > >:
>>
>> Hi Johan,
>>
>> we changed our platform 2 weeks ago from 1 OpenSips Proxy 1.6.4 to 3
>> OpenSips instances with topology hiding.
>> Since we didn't have this problems earlier, I think it worked with
>> the old platform.
>> As we call force_rport() in the main_route, the private IP in the VIA
>> header should be ignored, right?
>> At the moment we call force_rport() in all our instances.
>> I think, we should call force_rport() only on the edge server where
>> we make the nat_handling, right?
>>
>> Kind regards,
>> Julian Santer
>> Raiffeisen OnLIne
>>
>>
>> Am 29.04.2016 um 10:10 schrieb Johan De Clercq:
>>
>> Indeed.
>>
>>
>> 2016-04-29 9:49 GMT+02:00 Julian Santer <
>> julian.san...@rolmail.net 
>>  julian.san...@rolmail.net>>>:
>>
>>  Hi Johan,
>>
>>  as the asterisk is not administrated by us, I have to ask
>> the customer.
>>  As I understand you think the problem should be the private
>> IP in the VIA header
>>  and this should be fixed with STUN, right?
>>
>>  Kind regards,
>>  Julian Santer
>>  Raiffeisen OnLine
>>
>>  Am 29.04.2016 um 09:17 schrieb Johan De Clercq:
>>
>>  do you use stun on the phones ?
>>
>>  2016-04-29 9:14 GMT+02:00 Julian Santer <
>> julian.san...@rolmail.net 
>>  julian.san...@rolmail.net>>
>>   julian.san...@rolmail.net> > >
>>   Hi guys,
>>
>>   we are using OpenSips 2.1.2 with topology_hiding.
>>   Now we got trouble with Re-Invites, which are
>> routed to the private IP from the "from".
>>   The topology_hiding matches, but the Re-Invite is
>> sent to the private IP from the "from".
>>   Have we to call lookup again on the registrar/core,
>> when we got a Re-Invite?
>>   You can find the trace under
>> http://siptrace.rolbox.net/siptrace.html
>>
>>   Kind regards,
>>   Julian Santer
>>   Raiffeisen OnLine
>>
>>
>>   ___
>>   Users mailing list
>> Users@lists.opensips.org 
>> > >>
>>   users-zwoeplungu3gxa1m0aa...@public.gmane.orgps.org>
>>  Users-ZwoEplunGu1UUpeUK0L>/p...@public.gmane.orgsips.org
>> >>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>>
>>
>>
>>  ___
>>  Users mailing list
>> Users@lists.opensips.org 
>>  Users-ZwoEplunGu1UUpeUK0L/p...@public.gmane.orgsips.org>>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>>
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org 
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Re-Invite routed to private IP

[Julian Santer]

We are using 2.1.2
So we made a "huge" version update and also changed the kind of working

Am 29.04.2016 um 14:27 schrieb Johan De Clercq:

What version do you use in your new install ?

2016-04-29 13:12 GMT+02:00 Julian Santer >:

Hi Johan,

we changed our platform 2 weeks ago from 1 OpenSips Proxy 1.6.4 to 3 
OpenSips instances with topology hiding.
Since we didn't have this problems earlier, I think it worked with the old 
platform.
As we call force_rport() in the main_route, the private IP in the VIA 
header should be ignored, right?
At the moment we call force_rport() in all our instances.
I think, we should call force_rport() only on the edge server where we make 
the nat_handling, right?

Kind regards,
Julian Santer
Raiffeisen OnLIne


Am 29.04.2016 um 10:10 schrieb Johan De Clercq:

Indeed.


2016-04-29 9:49 GMT+02:00 Julian Santer 
>>:

 Hi Johan,

 as the asterisk is not administrated by us, I have to ask the 
customer.
 As I understand you think the problem should be the private IP in 
the VIA header
 and this should be fixed with STUN, right?

 Kind regards,
 Julian Santer
 Raiffeisen OnLine

 Am 29.04.2016 um 09:17 schrieb Johan De Clercq:

 do you use stun on the phones ?

 2016-04-29 9:14 GMT+02:00 Julian Santer 
>
  
>
 
/p...@public.gmane.orgsips.org
>>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users







 ___
 Users mailing list
Users@lists.opensips.org 
>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users







___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users








___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Re-Invite routed to private IP

[Johan De Clercq]

What version do you use in your new install ?

2016-04-29 13:12 GMT+02:00 Julian Santer :

> Hi Johan,
>
> we changed our platform 2 weeks ago from 1 OpenSips Proxy 1.6.4 to 3
> OpenSips instances with topology hiding.
> Since we didn't have this problems earlier, I think it worked with the old
> platform.
> As we call force_rport() in the main_route, the private IP in the VIA
> header should be ignored, right?
> At the moment we call force_rport() in all our instances.
> I think, we should call force_rport() only on the edge server where we
> make the nat_handling, right?
>
> Kind regards,
> Julian Santer
> Raiffeisen OnLIne
>
>
> Am 29.04.2016 um 10:10 schrieb Johan De Clercq:
>
>> Indeed.
>>
>>
>> 2016-04-29 9:49 GMT+02:00 Julian Santer > >:
>>
>> Hi Johan,
>>
>> as the asterisk is not administrated by us, I have to ask the
>> customer.
>> As I understand you think the problem should be the private IP in the
>> VIA header
>> and this should be fixed with STUN, right?
>>
>> Kind regards,
>> Julian Santer
>> Raiffeisen OnLine
>>
>> Am 29.04.2016 um 09:17 schrieb Johan De Clercq:
>>
>> do you use stun on the phones ?
>>
>> 2016-04-29 9:14 GMT+02:00 Julian Santer <
>> julian.san...@rolmail.net 
>>  julian.san...@rolmail.net>>>:
>>
>>  Hi guys,
>>
>>  we are using OpenSips 2.1.2 with topology_hiding.
>>  Now we got trouble with Re-Invites, which are routed to the
>> private IP from the "from".
>>  The topology_hiding matches, but the Re-Invite is sent to
>> the private IP from the "from".
>>  Have we to call lookup again on the registrar/core, when we
>> got a Re-Invite?
>>  You can find the trace under
>> http://siptrace.rolbox.net/siptrace.html
>>
>>  Kind regards,
>>  Julian Santer
>>  Raiffeisen OnLine
>>
>>
>>  ___
>>  Users mailing list
>> Users@lists.opensips.org 
>>  Users-ZwoEplunGu1UUpeUK0L/p...@public.gmane.orgsips.org>>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>>
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org 
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Selective logging

[John Nash]

Is there any way to log messages (Custom messages and SIP trace) from
script for a given parameter say IP or ruri.

A crude way can be to store say user in local cache and match with the user
in script and log else pass but ..

1- I am not sure if any other smart way to do it
2- How can I dunp SIP messages
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Re-Invite routed to private IP

[Julian Santer]

Hi Johan,

we changed our platform 2 weeks ago from 1 OpenSips Proxy 1.6.4 to 3 OpenSips 
instances with topology hiding.
Since we didn't have this problems earlier, I think it worked with the old 
platform.
As we call force_rport() in the main_route, the private IP in the VIA header 
should be ignored, right?
At the moment we call force_rport() in all our instances.
I think, we should call force_rport() only on the edge server where we make the 
nat_handling, right?

Kind regards,
Julian Santer
Raiffeisen OnLIne


Am 29.04.2016 um 10:10 schrieb Johan De Clercq:

Indeed.


2016-04-29 9:49 GMT+02:00 Julian Santer >:

Hi Johan,

as the asterisk is not administrated by us, I have to ask the customer.
As I understand you think the problem should be the private IP in the VIA 
header
and this should be fixed with STUN, right?

Kind regards,
Julian Santer
Raiffeisen OnLine

Am 29.04.2016 um 09:17 schrieb Johan De Clercq:

do you use stun on the phones ?

2016-04-29 9:14 GMT+02:00 Julian Santer 
>>:

 Hi guys,

 we are using OpenSips 2.1.2 with topology_hiding.
 Now we got trouble with Re-Invites, which are routed to the private IP from 
the "from".
 The topology_hiding matches, but the Re-Invite is sent to the private IP 
from the "from".
 Have we to call lookup again on the registrar/core, when we got a 
Re-Invite?
 You can find the trace under 
http://siptrace.rolbox.net/siptrace.html

 Kind regards,
 Julian Santer
 Raiffeisen OnLine


 ___
 Users mailing list
Users@lists.opensips.org 
>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users







___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users








___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Regarding siptrace module .

[Sasmita Panda]

Hi All ,

 I am trying to integrate HOMER with opensips . I am using opensips as
my capture agent and forwarding the HEP packets to the capture server which
is kamailio .

  My opensips is running on AWS EMI . Where there is a public and a
private IP of the machine . So we used to writein the bellow format in the
opensips config .


*"listen=0.0.0.0:5506  AS 54.211.x.y:5506 "*

   Second part is the public ip , and that get used for publishing any
message out side . the first part is for internal use .
With this if I am trying to forward the HEP packet through siptrace module
, I had configured like bellow .

#load siptrcae module for trace node ---
modparam("siptrace", "duplicate_uri", "sip:107.170.x.y:9060")
modparam("siptrace", "duplicate_with_hep", 1)
modparam("siptrace", "trace_to_database", 0)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "trace_on", 1)
#HEPv2 == timestamp will be included to HEP header
modparam("siptrace", "hep_version", 2)

   In "107.170.x.y:9060" my kamailio is running . But when I am trying
to forward the packets its giving error .

*"ERROR:siptrace:pipport2su: host <0.0.0.0> is not an IP"  . *

  If I am changing my opensips config to *"listen=**54.211.x.y:5506
AS **54.211.x.y:5506 " *then its running fine .


  How will I get read of this error without changing my listen IP and
port line ?
Is there anything I can do in the siptrace module to use the public ip only
rather than using " *0.0.0.0* " ?


*Thanks & Regards*
*Sasmita Panda*
*Network Testing and Software Engineer*
*3CLogic , ph:07827611765*
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Re-Invite routed to private IP

[Johan De Clercq]

Indeed.


2016-04-29 9:49 GMT+02:00 Julian Santer :

> Hi Johan,
>
> as the asterisk is not administrated by us, I have to ask the customer.
> As I understand you think the problem should be the private IP in the VIA
> header
> and this should be fixed with STUN, right?
>
> Kind regards,
> Julian Santer
> Raiffeisen OnLine
>
> Am 29.04.2016 um 09:17 schrieb Johan De Clercq:
>
>> do you use stun on the phones ?
>>
>> 2016-04-29 9:14 GMT+02:00 Julian Santer > >:
>>
>> Hi guys,
>>
>> we are using OpenSips 2.1.2 with topology_hiding.
>> Now we got trouble with Re-Invites, which are routed to the private
>> IP from the "from".
>> The topology_hiding matches, but the Re-Invite is sent to the private
>> IP from the "from".
>> Have we to call lookup again on the registrar/core, when we got a
>> Re-Invite?
>> You can find the trace under http://siptrace.rolbox.net/siptrace.html
>>
>> Kind regards,
>> Julian Santer
>> Raiffeisen OnLine
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org 
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Re-Invite routed to private IP

[Julian Santer]

Hi Johan,

as the asterisk is not administrated by us, I have to ask the customer.
As I understand you think the problem should be the private IP in the VIA header
and this should be fixed with STUN, right?

Kind regards,
Julian Santer
Raiffeisen OnLine

Am 29.04.2016 um 09:17 schrieb Johan De Clercq:

do you use stun on the phones ?

2016-04-29 9:14 GMT+02:00 Julian Santer >:

Hi guys,

we are using OpenSips 2.1.2 with topology_hiding.
Now we got trouble with Re-Invites, which are routed to the private IP from the 
"from".
The topology_hiding matches, but the Re-Invite is sent to the private IP from the 
"from".
Have we to call lookup again on the registrar/core, when we got a Re-Invite?
You can find the trace under http://siptrace.rolbox.net/siptrace.html

Kind regards,
Julian Santer
Raiffeisen OnLine


___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users








___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Re-Invite routed to private IP

[Johan De Clercq]

do you use stun on the phones ?

2016-04-29 9:14 GMT+02:00 Julian Santer :

> Hi guys,
>
> we are using OpenSips 2.1.2 with topology_hiding.
> Now we got trouble with Re-Invites, which are routed to the private IP
> from the "from".
> The topology_hiding matches, but the Re-Invite is sent to the private IP
> from the "from".
> Have we to call lookup again on the registrar/core, when we got a
> Re-Invite?
> You can find the trace under http://siptrace.rolbox.net/siptrace.html
>
> Kind regards,
> Julian Santer
> Raiffeisen OnLine
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Re-Invite routed to private IP

[Julian Santer]

Hi guys,

we are using OpenSips 2.1.2 with topology_hiding.
Now we got trouble with Re-Invites, which are routed to the private IP from the 
"from".
The topology_hiding matches, but the Re-Invite is sent to the private IP from the 
"from".
Have we to call lookup again on the registrar/core, when we got a Re-Invite?
You can find the trace under http://siptrace.rolbox.net/siptrace.html

Kind regards,
Julian Santer
Raiffeisen OnLine


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users