Thanks Scott for your response. May you tell me where exactly it tries to bind that other socket. I can modify my code and fix it., also submit it to the list.
Any idea may help me a lot to resolve this problem. Regards, Vikas On Fri, Jul 4, 2008 at 8:41 PM, Scott Lawrence <[EMAIL PROTECTED]> wrote: > > On Fri, 2008-07-04 at 20:14 +0530, VG wrote: > > Thanks Scott , > > > > Still bit stuck somewhere. > > when i start my sipx it binds port 5060 on both ip adress. > > I run following command: > > netstat -an --inet -p > > > > tcp 0 0 192.168.22.142:5060 0.0.0.0:* > > LISTEN 876/sipXproxy > > tcp 0 0 192.168.4.140:5060 0.0.0.0:* > > LISTEN 876/sipXproxy > > > > I just want to bind the 192.168.4.140:5060 not for second interface. > > eht1: 192.168.22.142:5060 should not be binded by the sipXproxy. > > > > How this can be possible > > It isn't in version 3.10 and earlier. > > In 4.0, the plan is to fix this - I believe it is fixed in the current > mainline code, but I don't know how extensively it has been tested yet. > The current mainline is not suitable for any production use. > > -- > Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED]<[EMAIL > PROTECTED]> > sipXecs project coordinator - SIPfoundry > http://www.sipfoundry.org/sipXecs > CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ > http://www.pingtel.com/ > >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
