> > > Hi Omar, > > I hope you don't mind the repeated mails :) > > Firstly, I shall try on a multi-homed Vista machine and see how it behaves. > > Secondly, did you have a look at the picasa pic I sent? With the kapanga > client allowing the user to select the interface? How do you think Kapanga > handles it internally? > > Thanks again, > Arjun > > > > ------------------------------ > > > > Message: 2 > > Date: Tue, 10 Jul 2012 06:49:44 +1000 > > From: Omar Hussein <omarh2812@xxxxxxxxx> > > To: pjsip list <pjsip at lists.pjsip.org> > > Subject: Re: Wrong NIC despite bound_addr (Omar Hussein) (Omar > > Hussein) > > Message-ID: <FA2F8E77-D105-49D8-B1F5-B42F55B74D4C at gmail.com> > > Content-Type: text/plain; charset="us-ascii" > > > > Hi Arjun > > > > That's a nice link. But i think that even with vista you will not be able > > to reach the 192 target address with your current configuration from that > > interface unless you configure a gateway on that interface or put a route > > entry specifying a gateway to reach that network. With vista it looks > like > > it will stop sending on the other interface. > > > > Regards > > Omar > > > > > > Sent from my iPhone > > > > On 10/07/2012, at 12:13 AM, Arjun Kamath <junnaonly at gmail.com> wrote: > > > > > Hi Omar, > > > > > > Thanks for the clear answer. But if that is the case, how are other > VoIP > > clients like Kapanga able to give the user control over selecting the > > interface? I have attached a screenshot, where there is a dropdown menu > > letting the user choose the NIC (either 0 or 1) that he wants. > > > > > > > > > https://picasaweb.google.com/101582892235327293990/KapangaNICSelect#5763154867739970322 > > > > > > If I had to guess, I would say that Kapanga internally changes the > route > > table. But I don't want to assume so much. > > > > > > I also found this very informative guide that explains difference > > between XP and Vista handling. I am currently testing on an XP machine. > > From this it looks like using a Vista would solve my problem. > > > > > > > > > http://blogs.technet.com/b/networking/archive/2009/04/25/source-ip-address-selection-on-a-multi-homed-windows-computer.aspx > > > > > > Regards, > > > Arjun > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Sun, 8 Jul 2012 09:28:57 +0300 > > > From: Arjun Kamath <junnaonly@xxxxxxxxx> > > > To: pjsip at lists.pjsip.org > > > Subject: Re: Wrong NIC despite bound_addr (Omar Hussein) > > > Message-ID: > > > < > > CADzHbEXtQktzTzEEu-Wdin09gfCDS6T+MW9hVKEu+q2j-MRrTQ at mail.gmail.com> > > > Content-Type: text/plain; charset="iso-8859-1" > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > -------------- next part -------------- > > > An HTML attachment was scrubbed... > > > URL: < > > > http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120708/52becf5b/attachment-0001.html > > > > > > > > > ------------------------------ > > > > > > Message: 2 > > > Date: Sun, 8 Jul 2012 22:27:35 +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 (Omar Hussein) > > > Message-ID: <D450BEEF-9D7E-4666-9C85-4E3F1719EFC4 at gmail.com> > > > Content-Type: text/plain; charset="us-ascii" > > > > > > 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 > > > > > > _______________________________________________ > > > 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/20120710/8fe4feff/attachment-0001.html > > > > > > > ------------------------------ > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120711/f3dc748f/attachment-0001.html > > > > ------------------------------ > > Message: 3 > Date: Wed, 11 Jul 2012 09:28:56 +1000 > From: Omar Hussein <omarh2812@xxxxxxxxx> > To: pjsip list <pjsip at lists.pjsip.org> > Subject: Re: Wrong NIC despite bound_addr (Omar Hussein) (Omar > Hussein) (Omar Hussein) > Message-ID: > <CAAB_GXjw1WU5AWy8GsALgBcTxFYsAF0GMS-3_2PEgFDP= > zSPCA at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Arjun, > > I am not familiar with the kapanga client. Are you saying that you > have tried this client with your ip configuration and found it to work? > I would say that the kapanda client will not work unless the underlying > network configuration is correct. i.e. gateway configured and is able to > route to the destination network. In your case even if the outgoing packet > will use the correct NIC this NIC does not have a default gateway > configured so there is no way for the packet to reach that destination > network (unless you add a static route). It must go via a router. > > Regards, > Omar > > Hi Omar, Just to verify what you said, I tried to use Kapanga and as you had predicted it didn't do what I thought it would do. Though I configured it to use the 10.52... interface, it still sent the packets on the 131.. interface. As for my client, I added a route to the 192.168 destination and the client is behaving properly. Thanks for the patience and support :) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120719/5bf63638/attachment-0001.html>
