search

mfurqan777 / boghe

Automatically exported from code.google.com/p/boghe
0 stars 0 forks source link

Issue with secondary IP addresses on a single interface #119

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

What is the expected output? What do you see instead?

Contact and Via headers should contain the IP address of the interface in which 
they exit.  The SIP messages is created with an IP address of a secondary 
interface and also has the same in the Via and Contact headers.  Since this is 
private IP space the messages are never returned to the client.

What version of the product are you using? On what operating system?

Boghe IMS Client v2.0.85.672
Microsoft Windows XP [Version 5.1.2600]

Please provide any additional information below.

Windows IP Configuration

Ethernet adapter Wireless Network Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6200
 AGN
        Physical Address. . . . . . . . . : 00-27-10-D6-91-A0
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : No
        IP Address. . . . . . . . . . . . : 135.244.44.105
        Subnet Mask . . . . . . . . . . . : 0.0.0.0
        IP Address. . . . . . . . . . . . : 192.168.0.111
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : 2416:1::d5b9:4c4f:ce91:ff2d
        IP Address. . . . . . . . . . . . : 2416:1::1195:8a20:f468:2106
        IP Address. . . . . . . . . . . . : 2416:1::24c7:b8a5:c867:6b40
        IP Address. . . . . . . . . . . . : 2416:1::227:10ff:fed6:91a0
        IP Address. . . . . . . . . . . . : fe80::227:10ff:fed6:91a0%4
        Default Gateway . . . . . . . . . : 135.244.44.105
                                            fe80::21b:d5ff:fe5b:b890%4
        DHCP Server . . . . . . . . . . . : 192.168.0.1
        DNS Servers . . . . . . . . . . . : 135.1.1.111
                                            135.1.1.110
                                            192.168.1.5
                                            192.168.1.10
                                            fec0:0:0:ffff::1%3
                                            fec0:0:0:ffff::2%3
                                            fec0:0:0:ffff::3%3
        Primary WINS Server . . . . . . . : 135.3.38.42
        Secondary WINS Server . . . . . . : 135.3.38.43
        Lease Obtained. . . . . . . . . . : Thursday, January 19, 2012 10:59:17
AM
        Lease Expires . . . . . . . . . . : Friday, January 20, 2012 10:59:17 AM

____________________________________________

REGISTER sip:wonderland.alcatel-lucent.com SIP/2.0
Via: SIP/2.0/UDP 192.168.0.111:2628;branch=z9hG4bK251551750;rport
From: <sip:28563890@wonderland.alcatel-lucent.com>;tag=251532962
To: <sip:28563890@wonderland.alcatel-lucent.com>
Contact: 
<sip:28563890@192.168.0.111:2628;transport=udp>;expires=600000;+g.oma.sip-im;lan
guage="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio;+g.3gpp.icsi-ref="
urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp.cs-voice
Call-ID: 657f1647-0270-5104-f8a1-898e40333328
CSeq: 25558 REGISTER
Content-Length: 0
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe/v2.0.85.672
P-Preferred-Identity: <sip:28563890@wonderland.alcatel-lucent.com>
Supported: path

Original issue reported on code.google.com by tstro...@gmail.com on 19 Jan 2012 at 4:57

GoogleCodeExporter commented 9 years ago 
The local IP address (Network Interface) depends on the proxy server. The best 
local IP is determined by this function: 
http://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyNET/sr
c/tnet_utils.c#517 which use WinSock2 function "GetBestInterfaceEx()". This 
means that according to the SIP stack, the best local IP address to use to 
reach the proxy is "192.168.0.111".
For now there is no user interface to force the stack to use arbitrary IP 
address but you can do it by changing the "configuration.xml" file (starting 
revision 89). This file should be under "C:\Users\<your user 
name>\AppData\Roaming\Doubango\Boghe IMS Client" if you are using Vista or 7.

<XmlSection name="NETWORK">
    .....
    <entry key="LOCAL_IP" value="135.244.44.105" />
    .....
</XmlSection>

Original comment by boss...@yahoo.fr on 23 Jan 2012 at 1:55

GoogleCodeExporter commented 9 years ago 
Thanks.. Any ideas on when this will be moved and released to the Beta release 
which is posted for download?  I have no ability to build the subversions.

Original comment by tstro...@gmail.com on 23 Jan 2012 at 2:07

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 29 Mar 2012 at 4:01