Hi Arjun The route table is to let windows tcp/ip know how to reach that destination network of 192.x.x.x. If the destination address was in the same subnet as the 10.x.x.x interface (as determined by the subnet mask) then that interface would be used. But since it's on a different network to both interfaces a default gateway must be used to route the packet. Windows only knows of one gateway which is the one configured on the other interface. You could set the default gateway on the 10.x.x.x interface instead and it will use that one. Or set a static route as i suggested before. Regards Omar On 08/07/2012, at 4:28 PM, Arjun Kamath <junnaonly at gmail.com> wrote: > Hi Omar, > > For a little background, what I would actually like is for the tool to let the user choose from the various NICs available on the machine, with a drop down menu and for the tool to use only that NIC to send and receive all (SIP, SDP, UDP, RTP) messages. With this in mind, I felt that bound_addr and public_addr would do the job for me. > > Is modifying the route table the only way? I felt that this was more of a hack than a permanent solution. I would have to change the route settings on every test machine and other applications would be unnecessarily affected as well right? > > Regards, > Arjun > > > Message: 4 > Date: Sat, 7 Jul 2012 01:12:43 +1000 > From: Omar Hussein <omarh2812@xxxxxxxxx> > To: pjsip list <pjsip at lists.pjsip.org> > Cc: "pjsip at lists.pjsip.org" <pjsip at lists.pjsip.org> > Subject: Re: Wrong NIC despite bound_addr > Message-ID: <7FDA71F0-5359-4497-872F-48D979069698 at gmail.com> > Content-Type: text/plain; charset="us-ascii" > > Hi > > Since your destination is on different subnet packet must go to default gateway. Maybe since default gateway is only configured on 131.x.x.x interface windows is using that one. > > If you want to send the packet to another gateway on the other subnet you can add a static route by using the route add command in a cmd prompt. > > Regards > Omar > > > > On 07/07/2012, at 12:41 AM, Arjun Kamath <junnaonly at gmail.com> wrote: > > > Also, in case it wasn't clear. I am not receiving any replies whatsoever on wireshark. I keep sending this mesage > > > > Source: 10.52.230.74 > > Destination: 192.168.212.24 > > Protocol:SIP > > Length:585 > > Info: Request: REGISTER sip:ericssonlte.com > > > > > > On Fri, Jul 6, 2012 at 5:38 PM, Arjun Kamath <junnaonly at gmail.com> wrote: > > Hi, > > > > I am developing my tool in Visual Studio 2008 using pjsip 2.0 without any video. > > > > My machine has 2 NICs as follows: > > > > Windows IP Configuration > > > > Ethernet adapter Local Area Connection 2: > > > > Connection-specific DNS Suffix . : > > IP Address. . . . . . . . . . . . : 10.52.230.74 > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Default Gateway . . . . . . . . . : > > > > Ethernet adapter Local Area Connection: > > > > Connection-specific DNS Suffix . : > > IP Address. . . . . . . . . . . . : 131.160.81.63 > > Subnet Mask . . . . . . . . . . . : 255.255.252.0 > > Default Gateway . . . . . . . . . : 131.160.80.1 > > > > I would like my VoIP application to communicate to the Proxy over 10.52.230.74. I have set each of the following to 10.52.230.74 > > > > app_config.udp_config.public_addr > > app_config.udp_config.bound_addr > > app_config.rtp_config.public_addr > > app_config.rtp_config.bound_addr > > > > What is strange is that on the Wireshark trace, the packet source is shown as 10.52.230.74 but it is sent over the 131.160.81.63 interface(I have to activate the sniffer on the 131.160.81.63 to see any SIP messages) There are no SIP messages sent over 10.52.230.74 interface. > > > > I have tried to compare my tool with pjsua_app and things look the same. > > > > Any advice? > > > > Regards, > > Arjun > > > > > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120708/20ef4d82/attachment.html>
