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 < [email protected]> wrote: > Sasmita, > > Does you config LITERALLY say.. *listen=0.0.0.0:5506 > <http://0.0.0.0:5506/> AS 54.211.x.y:5506 *?? > > .. > > > > On Fri, Apr 29, 2016 at 3:30 PM, Sasmita Panda <[email protected]> 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 <[email protected] >> > 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 <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 >>> [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
