[OpenSIPS-Users] Regarding siptrace module .

[Bogdan-Andrei Iancu]

The SIP protocol is not really designed to work with 0.0.0.0 - which is 
an IP that makes sense only when listening, but not when reading and 
sending data.

By pure luck (in combination with the "as" statement) it works for the 
SIP traffic. But when it gets into siptrace and wans to pack it for HEP, 
HEP says 0.0.0.0 is not an valid IP .

Once again, why don;t you explicitly listen on the private IPs (with an 
"as" statement) to avoid the 0.0.0.0

Regards,

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

On 29.04.2016 17:30, 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 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> 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 <http://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 at lists.opensips.org <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160429/b630bd7d/attachment.htm>