Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

Hi,

In my app, after I bind a UDP socket and call ISOCKET_Readable() on the socket, the phone keeps changing its local IP address every 5 minutes if no network traffic. Why??? :confused: The network is VZW, and phone is LG VX6000.

Is this behavior of the network, phone, BREW or my app? Any information regarding the phone's IP address is welcome!

-Yang

Has anyone seen this before? or just something wrong with my code which triggers the IP changes? :(
Please help!
-yang

Has anyone seen this before? or just something wrong with my code which triggers the IP changes? :(
Please help!
-yang

have not seen this, may be something wrong w/ your code.
On VZW I've had handsets connected on the same IP until I told them to die on things from the Nokia to the VX6000

have not seen this, may be something wrong w/ your code.
On VZW I've had handsets connected on the same IP until I told them to die on things from the Nokia to the VX6000

Under no network traffic, my handset ip changs every 5 minutes. This happens when I create a UDP server socket on the handset by binding a socket on a port, and call ISOCKET_readable() to start waiting for incoming request.
Do you see no handset IP change under the same circumstance? do I create the server socket in right way? How did you do it?
Thanks for any further information,
-Yang

Under no network traffic, my handset ip changs every 5 minutes. This happens when I create a UDP server socket on the handset by binding a socket on a port, and call ISOCKET_readable() to start waiting for incoming request.
Do you see no handset IP change under the same circumstance? do I create the server socket in right way? How did you do it?
Thanks for any further information,
-Yang

I assume you are using a 1xRTT session. If you are using QNC then this sounds like a linger timer kicking in.

I assume you are using a 1xRTT session. If you are using QNC then this sounds like a linger timer kicking in.

From my knowledge, it might be due to operator access architecture. The concept of changing IP's while connected to a RAS(remote access System) is a known issue.
This is something that must IP based application has to take into consideration.

From my knowledge, it might be due to operator access architecture. The concept of changing IP's while connected to a RAS(remote access System) is a known issue.
This is something that must IP based application has to take into consideration.

Thanks for the replies. Yes, the network is VZW 1xRTT and the phone is LG VX6000. I just found a previous post reporting the same issue.
Is there any solution for the issue? I don't want to ping the network every 5 minutes to keep PPP from releasing IP. The reason is every network traffic would make PPP active for the duration of data transmission PLUS 30 seconds lingering time. During the time period, incoming voice call is blocked. Simple calculation reveals that about 10% of time a phone can not receive an incoming call. The problem is very serious. :eek:
Any idea about how to let the phone keep its IP? if we have to ping the network every 5 minutes, is it allowed by operators and TRUE BREW to reduce the lingering time?
Please help!
-yang

Thanks for the replies. Yes, the network is VZW 1xRTT and the phone is LG VX6000. I just found a previous post reporting the same issue.
Is there any solution for the issue? I don't want to ping the network every 5 minutes to keep PPP from releasing IP. The reason is every network traffic would make PPP active for the duration of data transmission PLUS 30 seconds lingering time. During the time period, incoming voice call is blocked. Simple calculation reveals that about 10% of time a phone can not receive an incoming call. The problem is very serious. :eek:
Any idea about how to let the phone keep its IP? if we have to ping the network every 5 minutes, is it allowed by operators and TRUE BREW to reduce the lingering time?
Please help!
-yang

I keep a constant connectiong w/ the desired server, and send pings up to the servers app genereated, and have the server send a pong back, but never vice versa.
This works fine. Keeps network alive and allows us to determine if a user should shut down they're network connection if for somereason lag is to bad.

I keep a constant connectiong w/ the desired server, and send pings up to the servers app genereated, and have the server send a pong back, but never vice versa.
This works fine. Keeps network alive and allows us to determine if a user should shut down they're network connection if for somereason lag is to bad.

with 1x, your IP address should not be changing unles you are loosing network coverage and having to re-establish the connection. The use of a ping to keep the network up is a really bad idea. What is the signal strength like in your area? Can you test in a different geographical location?

with 1x, your IP address should not be changing unles you are loosing network coverage and having to re-establish the connection. The use of a ping to keep the network up is a really bad idea. What is the signal strength like in your area? Can you test in a different geographical location?

1xRTT network signal strength is always good in my location. The phone doesn't either loose coverage or try to re-establish the connection.
The problem happens every 5 minutes makes me think it is not coverage problem. In my case, I have a local UDP server socket running on the phone and waiting for incoming request.
If you observe differently, what is your settings?
Please help me to find out whether it is a network or BREW characteristics, or just my app.
-yang

1xRTT network signal strength is always good in my location. The phone doesn't either loose coverage or try to re-establish the connection.
The problem happens every 5 minutes makes me think it is not coverage problem. In my case, I have a local UDP server socket running on the phone and waiting for incoming request.
If you observe differently, what is your settings?
Please help me to find out whether it is a network or BREW characteristics, or just my app.
-yang

It sounds to me as VzW has the idle timer set around 5 minutes. Basically, the PDSN providing you wireless service monitors packet activity. After a designated time, if a subscriber has no activity the subscriber is considered dormant and resources are released. There is nothing you can do about the settings on this device.

It sounds to me as VzW has the idle timer set around 5 minutes. Basically, the PDSN providing you wireless service monitors packet activity. After a designated time, if a subscriber has no activity the subscriber is considered dormant and resources are released. There is nothing you can do about the settings on this device.