1. Brekeke Product Name and Version:
Brekeke SIP Server, 3.6.3.0/454
2. Java version:
1.7.0_121
3. OS type and the version:
AWS Linux 3.14.35-28.38.amzn1.x86_64
4. UA (phone), gateway or other hardware/software involved:
ABTOLLC
Android Phone (Android 5.1)
5. Your problem:
Android Phone (Android 5.1) in 4G (wifi had no problem at all).
The app's registration always failed (408 timeout)
But when I check the server's "Registered Clients", it had the exact same user registered several times, depending on how many time it failed. If it failed 20 times, there were 20 same registered user with different port like the following:
Contact URI (Source IP Address)
-------------------------------------
sip:203@101.13.64.43:5149
(101.13.64.43:5149)
sip:203@101.13.64.43:5150
(101.13.64.43:5150)
sip:203@101.13.64.43:5150
(101.13.64.43:5151)
.....
The 4G network connection is good. I know that because I am able to log in to the SIP server using that Android phone.
What could be the problem?
Thanks.
Brekeke SIP Server, 3.6.3.0/454
2. Java version:
1.7.0_121
3. OS type and the version:
AWS Linux 3.14.35-28.38.amzn1.x86_64
4. UA (phone), gateway or other hardware/software involved:
ABTOLLC
Android Phone (Android 5.1)
5. Your problem:
Android Phone (Android 5.1) in 4G (wifi had no problem at all).
The app's registration always failed (408 timeout)
But when I check the server's "Registered Clients", it had the exact same user registered several times, depending on how many time it failed. If it failed 20 times, there were 20 same registered user with different port like the following:
Contact URI (Source IP Address)
-------------------------------------
sip:203@101.13.64.43:5149
(101.13.64.43:5149)
sip:203@101.13.64.43:5150
(101.13.64.43:5150)
sip:203@101.13.64.43:5150
(101.13.64.43:5151)
.....
The 4G network connection is good. I know that because I am able to log in to the SIP server using that Android phone.
What could be the problem?
Thanks.