3G/4G Connection Unstable or Failed to Register

[russellhung]

1. Brekeke Product Name and Version:

Brekeke SIP Server
3.4.6.3/411

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:

Using Linphone SIP Cline as well as ABTO SIP Client

5. Your problem:

The connections were not stable when the devices (iPhone, iPad, Android Phone) were under 3G/4G environment:

1.) between iOS devices, the IM messages cannot be delivered
2.) The Android phone cannot even register to the accounts.

If the devices were all in wifi environment, all of the functions worked (audio phone, video phone, IM messages).

What kind of setup I need to do?

[russellhung]

Hi,

Still cannot figure out why.. I monitored the connections by looking at the printouts on the Android Monitor, the reason is "register timeout", but the android phone has 4G network connections, it can access to other websites on Android browsers. Does the server block 4G connections? It doesn't make sense to me.

Please see the following printouts:

Request msg REGISTER/cseq=64035 (tdta0x7a411b50) to UDP my.ip.address:5060:
REGISTER sip:my.server.com SIP/2.0
Via: SIP/2.0/UDP 101.13.137.235:37327;rport;branch=z9hG4bKabh75GrSIyFbAN8LP.OEUFIxef93dtdDU4
Route: <sip:my.server.com;transport=udp;lr>
Max-Forwards: 70
From: <sip:202@my.server.com>;tag=VDWeg8DXWyYKJ1mKRWoqoNED4Drpg0N2
To: <sip:202@my.server.com>
Call-ID: gyYvOc-aDwaEvumYEJ8dWY3M8YG6e7-8
CSeq: 64035 REGISTER
User-Agent: ABTOLLC
Contact: <sip:202@101.13.137.235:37327>
Expires: 300
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Authorization: Digest username="202", realm="my.server.com, nonce="fd5aba50f0630c555a0c81039741e09602aac172", uri="sip:my.server.com", response="3f976d96ec479e216493e7a1fcc2a5f2", algorithm=MD5
Content-Length: 0


--end msg--

.....


W/native: 22:51:09.865 absua_acc.c ...SIP registration failed, status=408 (Request Timeout)

.....

E/SipService: Profile state UP : status_text=Request Timeout status_code=408 expires=-1

....

[russellhung]

Hi,

In an effort to figure out what's going on, I'd observed something that confused me. Hopefully, there could be someone who is familiar with the situation and, please, could shed some light for me.

On the client side (Android Phone under 4G environment): we got 408 Request Timeout error

On the SIP server side (these are the weird parts):

If we:

1. checked the error log, it had "Authorization failed" with error code 407 and the failed account (From URI) always 100@my.server.com while the login account was actually not "100" (account 100 doesn't event exist). We are certain that the original login account and password were correct because we were able to log in under wifi environment.

2. checked the "Registered Clients", the account was already registered.

Hence, the client side and server side has different reasons of errors. Even on server side, it has discrepancies between error logs and client registration records.

[taitan]

You can ignore "407" in the error log. It will happen if you use SIP authentication in the SIP Server. SIP client will retry REGISTER with the credential after 407. That's why you found the account record in the [Registered Clients] page.

For 408, it seems REGISTER packet or its response was lost in the middle of the network connection path.
That's why the client treats it as "Timeout" So it seems your 4G network is unstable.

If you try 4G, go to a place where you can catch better 4G signal.

Also I recommend that you use the latest version of Brekeke SIP Server because it seems you are still using version 3.4.

[russellhung]

It seems that after we upgraded to the latest version (3.6.3.0/454) the 4G registration is more stable now. I think we need to keep our server up-to-date from now on.

Thanks a lot,

[Harold]

Since you are using iOS and Android, PushNotification will help.
With PushNotification, softphone can be launched automatically without periodical registration.
http://wiki.brekeke.com/wiki/PushNotification


> 100@my.server.com while the login account was actually not "100" (account 100 doesn't event exist).

Can you check the remote IP address of "100" in the error log?
If it is not your IP address (or your customer's IP address), someone tried to hack your SIP Server.
Check this. http://wiki.brekeke.com/wiki/Avoid-attacks

[russellhung]

Hi,

Thanks a lot. I think those are hacker's calls because their user agents are all "friendly-scanner". I will follow the document to block those calls.

[Harold]

These hacking attempts are trying to compromise network resources and secure information such as password.

Refer this topic.
http://www.brekeke-sip.com/bbs/viewtopic.php?t=7419