408 Request timeout with 1.1.7 but working fine with 0.15.0

[Jean-François Comeau]

Hello,

I'm having 408 request timeout error with version 1.1.7 (118) but when using version 0.15.0 (27) with the exact same settings everything works flawlessly (aside the fact that the older version is less stable).

I've attached the log file written after the 408.

Thanks in advance for your kind help,

JF

[Alexey Kuznetsov]

Hi,

The error 408 Request Timeout means that the app didn’t receive a reply from the server.

1. There’s a network problem between the app and the server.
2. The app sends requests to the wrong server.
3. The server just ignores the requests.

Does the account ever show the Available status? If not, it seems very much like 1. Please check if something (a local firewall?) is blocking all network traffic for the app or if UDP protocol is blocked.

If the account goes Available, it’s probably 2. or 3. Please check that the IP address the requests are sent to (in the log “.TX … to UDP ...") is the server address you expect. If you can contact somebody on the server side, please check if the requests reach the server, and if so, if the server sends replies.

Alexey

[Jean-François Comeau]

Thank you for your reply.

As mentioned everything works fine with an earlier version of Telephone...

The best hypothesis so far is that it has something to do with "pjsip Content-Length padding" as pointed out in this post.

What should I do since I'm not able to build the project from Github? Any plan on including a "fix" in a subsequent release?

Kind regards,

JF

[Alexey Kuznetsov]

Hello Jean-François,

The error 408 Request Timeout can be received for many network-related issue. The newly discovered problem is a pretty specific one. Also, it is not yet known if the proposed fix doesn’t break anything else. The best way to really fix this is to report this problem back to PJSIP developers, who have much more information on the internals of their library.

But before this is fixed in PJSIP, you can find the root of the problem - the router modifying SIP packets. This “feature” should be disabled and it is also what SIP providers want anyway. If you have access to your router, please try to search for the option called SIP ALG in its settings and disable it.

Alexey

[Jean-François Comeau]

Disabling "SIP ALG" on my router did make it work again! :)

Thank you for your kind help.

Cheers,

JF