FPL: mysterious calls for a couple weeks now! and no outgoing / incoming calls!

[M.W.]

Hi, I have Obi202, configured for freephoneline.ca (SP1).

It was working fine until a couple weeks ago when I tried to test voip.ms on my phone.
So basically, I registered a voip.ms account, configured to my smart phone's voip app.   The mysterious calls started after I did a test call from my voip.ms account on my smart phone to my FPL number (configured on Obi202), (or the reverse, after I used my FPL # to call my voip.ms number on my phone). 

Now, I keep receiving mysterious calls in my obi202, caller id sometimes is 100, sometimes is 901 etc.
at the beginning, my FPL on obi202 still works.  So my wife was annoyed, she unplugged all phones off the wall, then couple days later, FPL on my obi202 stopped working.  the Eeror is 400:

   Call Ended (400 Bad Request(Bad Content-Length (larger than datagram)))

  Tried to change the dial plan, reset the phone, nothing works.

On FPL, it shows registered.  The strange thing is, while my Obi202 is reboot, I refreshed FPL webpage, ti still shows registered.

Can anyone please help me?

I have attached the phone log here.

[gsmlnx]

Have you enabled this option

SPn Service - SIP Credentials::X_EnforceRequestUserID = checked ;prohibit anonymous SIP.

From the thread http://www.obitalk.com/forum/index.php?topic=9581.0 Obi202 best practices for security settings

[Mango]

In addition to gsmlnx's suggestion, you should also set X_UserAgentPort to a high/random number between 20000 and 65535.

You are receiving these calls from SIP scanners because your firewall is insecure.  Using a high port number will not make things more secure, but it will make it less likely that the scanners will find you.

[M.W.]

Thank all, I have changed both  X_EnforceRequestUserID and X_UserAgentPort, I don't get any more random calls anymore.  But this problem still exists:

Call Ended (400 Bad Request(Bad Content-Length (larger than datagram)))

Any clue?

thanks

[Mango]

Be sure your device is configured as per the official guide: http://forum.fongo.com/viewtopic.php?f=15&t=16090

I have never seen that error before.

[M.W.]

Be sure your device is configured as per the official guide: http://forum.fongo.com/viewtopic.php?f=15&t=16090

I have never seen that error before.

Thank you, I have followed the pdf mentioned in the above link, still get the same 400 error.

This problem happened after I changed my router to Netgear R7000, but it worked at least a week after I switched the router, so the router probably is not the cause of the problem.

Thanks

[gsmlnx]

The only reference on this site to the 400 error message is in this thread about dial plans http://www.obitalk.com/forum/index.php?topic=5743.0

The solution there was to turn off the router's SIP ALG as mentioned in reply 8 of that thread.

[M.W.]

Thank you gsmlnx!  disable sip alg fixed my problem!

The only reference on this site to the 400 error message is in this thread about dial plans http://www.obitalk.com/forum/index.php?topic=5743.0

The solution there was to turn off the router's SIP ALG as mentioned in reply 8 of that thread.

[SoundLine]

I use the R7000 all the time when setting up VIOP accounts for clients. We always upgrade the router to Tomato Shibby firmware. IT's quick and easy to install and it is easier to turn off things like SIP/ALG and h323. Both of which can cause issues with proper registration. It is also super easy to reserve bandwidth and set QoS rules just for phone service. This will ensure that you never have a user on your network eating you bandwidth and causeing your phone to breakup.