[Resolved: Host name verification now required] mediatrix 2102 ATA registration problem

[Kwyjor]

I'm afraid my Freephoneline is also down at the moment. I am at a loss to explain why. I don't know exactly when it might have gone down. I have changed nothing in my network settings or on my ATA box. My SIP status at https://www.freephoneline.ca/showSipSettings was (initially) "disconnected".

MizuDroid on my smartphone works perfectly – with the same settings as my ATA box – and I am able to place outgoing calls, so it does not seem to be a network or routing issue on my end, or a problem with my account. (Yes, I am aware that trying to register two devices simultaneously is likely to cause problems. This is the first time I have tried to use MizuDroid in quite some time and I did not try to use it until I noticed my ATA box was not working.)

You may recall that my ATA box is a singularly unfriendly Mediatrix 2102. The only information it coughs up is "L1 registration failed, will retry in 2 minutes."

So I am pleased to see that I am perhaps not the only one having problems. I might guess that something changed on Fongo's end that is supported by MizuDroid but not supported by the Mediatrix. But what?

(I might have also guessed that Freephoneline deliberately blacklisted my Mediatrix box for some reason, but they wouldn't do that with no warning, would they?)

[Liptonbrisk]

So I am pleased to see that I am perhaps not the only one having problems.

Except vostro isn't having problems right now. vostro's ATAs are registered after following my instructions. So, I've created your own thread.

hi, thank a trillion for the detailed guide especially for the port setting. now it’s working again even without reboot rogers cable modem. it’s indeed strange that i never change any parameters in past years but it’s working quite well.

(I might have also guessed that Freephoneline deliberately blacklisted my Mediatrix box for some reason, but they wouldn't do that with no warning, would they?)

I doubt it.

[Kwyjor]

Fair enough... Please excuse me for replying in an inappropriate thread. I will review the instructions.

In the meantime, I note that changing my settings yields no result.

Registrar Host: voip4.freephoneline.ca
Registrar Port: 6060
Proxy Host: voip4.freephoneline.ca
Proxy Port: 6060

[Liptonbrisk]

I know that this has changed:

"Porta [the switch/server vendor] recommended to Fibernetics [CLEC/network used by Fongo/Freephoneline] to enable Host Name Verification on Sip Registrations. This was enabled. Marketing sent an email out last month to notify anyone who was IP registered to change to host name on their sip registration."

That means people can't use IP addresses for SIP servers, but you're not.

Have you disabled SIP ALG in your Bell Giga Hub?

Open your web browser, and login at 192.168.2.1 with your administration password.
Navigate to "Advanced tools & settings"-->"Networking"
Disable "SIP ALG".

Then power cycle (power off and on) Mediatrix 2102. Any difference?

[Kwyjor]

So, out of curiosity, what happens if you do validate realm this time?

I still get "L1 registration failed, will retry in 2 minutes."

ETA: I should specify that using "validate realm" last time yielded "L1 client authentication failed" as well as "L1 registration failed, authentication failure."

[Liptonbrisk]

So, out of curiosity, what happens if you do validate realm this time?

I still get "L1 registration failed, will retry in 2 minutes."

1) What brand and model modem are you using?

2) What brand and model router are you using?

Let's get SIP ALG disabled in everything.

[Liptonbrisk]

ETA: I should specify that using "validate realm" last time yielded "L1 client authentication failed" as well as "L1 registration failed, authentication failure."

Okay, but disabling that fixed the problem last time.

1) What brand and model modem are you using?

2) What brand and model router are you using?

It's possible that this is affecting you:

"Porta [the switch/server vendor] recommended to Fibernetics [CLEC/network used by Fongo/Freephoneline] to enable Host Name Verification on Sip Registrations. This was enabled. Marketing sent an email out last month to notify anyone who was IP registered to change to host name on their sip registration."

This is an example of a problem where guidelines aren't followed:

"From: “Name REDACTED" <sip:1450XXXXXXX@192.168.0.124>

To: <sip:1450XXXXXXX@192.168.0.124>"

That might be a SIP ALG problem. Someone's private LAN IP is replacing the proxy server name, and that leads to registration failure.
Normally, you would see "From: “Name REDACTED" <sip:1450XXXXXXX@voip.freephoneline.ca>


Without being able to get a log file of what's going on, figuring this out is probably going to be tricky.

[Kwyjor]

I notice that chagning my username in the "User Agent Authentication" does not seem to yield any change in the error message, so that's alarming.

I have a Bell Giga Hub (firmware 1.16.5). My Mediatrix plugs into it directly, so there is no router. (It is, to be sure, the same modem I have been using for several months.)

[Liptonbrisk]

I have a Bell Giga Hub (firmware 1.16.5). My Mediatrix plugs into it directly, so there is no router.

Okay, that's a modem/router combo. It does contain a router.

Disable SIP ALG in it.

Open your web browser, and login at 192.168.2.1 with your administration password.
Navigate to "Advanced tools & settings"-->"Networking"
Disable "SIP ALG".

[Kwyjor]

Open your web browser, and login at 192.168.2.1 with your administration password.
Navigate to "Advanced tools & settings"-->"Networking"
Disable "SIP ALG".

It is already disabled.

ETA: For good measure.

[Liptonbrisk]

"Porta [the switch/server vendor] recommended to Fibernetics [CLEC/network used by Fongo/Freephoneline] to enable Host Name Verification on Sip Registrations. This was enabled. Marketing sent an email out last month to notify anyone who was IP registered to change to host name on their sip registration."

I'm going to suppose that this is causing the problem.

I'm still here. Trying to figure out something . . .

I think domain needs to be specified and that realm needs to be validated.

Still checking . . .

[Liptonbrisk]

Okay, I'm guessing somewhat on the steps, but try this:

1) Go to SIP Configuration (SIP -> Configuration Tab):

Find the "SIP Configuration" box.

a) Registrar Host: type voip4.freephoneline.ca
b) Registrar Port: type 6060
c) Proxy Host: type voip4.freephoneline.ca
d) Proxy Port: type 6060
e) SIP Domain: type voip4.freephoneline.ca

f) SIP Port: Delete the current value (ex, 5060), and type a random number between 30000 and 60000. For example, try 33331 instead of 5060.

Just pick a port number in that range.
If you already have a random number in that range, simply enter a new one in that range.
By using a high random port you help to thwart SIP scanners/hackers.

Do not use the same SIP Port number for any other service on the ATA. Pick a different SIP Port in the same range for other service providers.
I never use UDP 5060 for the local SIP Port.

Also, this step can help to resolve a corrupted NAT association that may have developed between the router and the ATA.

2) Configure Authentication (SIP -> Authentication Tab):

a) Click the "Authentication" sub-tab.
b) Realm--> type voip4.freephoneline.ca
c) Validate Realm-->make sure this is Enabled (checked or selected).

3) Save Changes:

Click the "Submit" or "Save" or "Apply" button, usually at the bottom of the page. Save on each page you modified if necessary.

4) Reboot the Mediatrix Device:

Use the "Reboot" tab/button in the web interface if it exists, or unplug the power cord, wait 5 seconds, and plug it back in.

[Kwyjor]

Egads, it's working! I'll just take a moment to try to nail down the precise problem.

[Liptonbrisk]

"Porta [the switch/server vendor] recommended to Fibernetics [CLEC/network used by Fongo/Freephoneline] to enable Host Name Verification on Sip Registrations. This was enabled. Marketing sent an email out last month to notify anyone who was IP registered to change to host name on their sip registration."

I'm going to suppose that this is causing the problem.

I'm still here. Trying to figure out something . . .

I think domain needs to be specified and that realm needs to be validated.

Still checking . . .

The change request for host name verification by Freephoneline's server vendor (Porta) is the probable reason your registration started failing, especially since you were previously relying on a configuration where realm validation was off.

This means your Mediatrix 2102 now needs to send its registration requests in a way that properly uses and verifies against the hostname (voip.freephoneline.ca, voip2.freephoneline.ca, or voip4.freephoneline.ca).

[Liptonbrisk]

Egads, it's working! I'll just take a moment to try to nail down the precise problem.

Okay, good.

I'm pretty sure that specifying realm (voip4.freephoneline.ca, for example) and enabling Validate Realm are now required.

Possibly SIP domain is a requirement as well for your ATA (in conjunction with realm validation), but I'm almost positive the problem was due to Porta (server vendor) requesting host name verification and having Fibernetics enable it.

Changing the local SIP port can fix a stale or corrupted NAT association that developed between your Bell Hub (router) and the ATA. If that (changing local SIP Port) fixes a registration issue for you in the future, the problem is due to UDP timeouts (refer to point D from viewtopic.php?p=78976#p78976).

[Liptonbrisk]

Open your web browser, and login at 192.168.2.1 with your administration password.
Navigate to "Advanced tools & settings"-->"Networking"
Disable "SIP ALG".

It is already disabled.

ETA: For good measure.

Good. Keep that off. And if you ever switch ISPs, make sure that you try to disable SIP ALG in whatever modem/router combo they give you. If you ever buy your own router, also try to disable SIP ALG in it as well.

[Kwyjor]

I'm pretty sure that specifying realm (voip4.freephoneline.ca, for example) and enabling Validate Realm are now required.

Actually, it seems not! It works fine with all the old settings. It appears the solitary necessary change was switching the SIP Domain from "freephoneline.ca" to "voip.freephoneline.ca", which I suppose fits with this news from Porta. It also fits with MizuDroid, which does not seem to have a separate setting for that particular line.

But I will certainly keep those other options in mind if it goes offline again.

Thank you very much for your patience. I hope this experience serves to benefit others. Apologies again for replying unnecessarily to that other thread.

[Liptonbrisk]

Actually, it seems not! It works fine with all the old settings. It appears the solitary necessary change was switching the SIP Domain from "freephoneline.ca" to "voip.freephoneline.ca", which I suppose fits with this news from Porta.

They are validating host name, so specifying the full domain makes sense.

I wouldn't disable realm validation if it's working. The benefit is preventing the ATA from accidentally sending credentials (even the hashed response) to an unintended or potentially malicious server. I appreciate that’s unlikely to occur, but, again, I wouldn’t disable it if it’s working.

Anyway, I'm glad your ATA is registering again.

Good evening

[Liptonbrisk]

Thank you very much for your patience. I hope this experience serves to benefit others.

You're welcome!

Apologies again for replying unnecessarily to that other thread.

No problem. It's not a big deal.

Take care

[Liptonbrisk]

ETA: For good measure.
[/url]

I forgot to mention (actually, I was so tired last night that I just wanted to go to log out of these forums and sleep) that I would also turn off UPnP and DLNA for security reasons.

Both Universal Plug and Play (UPnP) and Digital Living Network Alliance (DLNA) can pose potential security risks, although UPnP is generally considered the more significant threat.


UPnP is Universal Plug and Play. The design of UPnP typically assumes that any device on the local network is trustworthy and lacks authentication or authorization mechanisms. Automatic Port Forwarding is a potential security risk. UPnP allows devices on your network to automatically request your router to open ports to the internet. While convenient for applications, such as games or P2P services, enabling UPnP means holes can be opened in your firewall without your knowledge or approval. Attackers can scan the internet for routers with UPnP enabled. If found, they can potentially send UPnP requests to routers (sometimes by impersonating game consoles and other devices) and command them to open ports, creating unwanted access into networks (including your LAN).

I suggest disabling UPnP on your router unless Freephoneline and anything else you’re using doesn’t work without UPnP enabled.

DLNA (Digital Living Network Alliance) is designed for discovering and sharing media (music, videos, pictures) between devices within your local network. It doesn't inherently involve opening ports to the wider internet as UPnP often does. So DNLA is typically less risky than UPnP. Regardless, If you’re not running a DLNA server, disable DNLA.