mediatrix 2102 ATA configuration problem

[yan]

Hi, anyone could suggest required settings or submit a sample configuration file
for the mediatrix 2102 ATA device ?
I tried to transcribe the same settings as I have on my linksys PAP2T ATA but
I cannot make it work

thank you

[Kwyjor]

I wasn't sure if I should start a new thread instead of bumping this one from twelve years ago, but I decided to go with bumping.

I have successfully connected to Freephoneline using MizuDroid on my smartphone, so evidently there's nothing wrong with my router or ISP. I was previously using my Mediatrix 2012 with a different VoIP provider, so there's probably nothing wrong with the hardware either. This suggests a configuration problem.

MizuDroid wouldn't connect until I set the registration timer correctly, as in the sticky thread. My Mediatrix might have the same problem (or it might be something else entirely). Unfortunately, I can't seem to find anything in the browser-based config page that lets me set that option. I found the "Unit Manager Network 3.2" application for download as in https://www.voiptalk.org/products/mtrixsetup but can't even get it to start at the moment, and I have no idea if it allows setting the registration timer either.

Before I tear my hair out any further, perhaps someone here has a solution?

[Liptonbrisk]

I've never used or even heard of this device before today (I wasn't a mod until 2017).

Are you unable to access it via its LAN IP?

1. Dial *#*0
2. Enter the IP address you hear into a web browser. Alternatively, try 192.168.10.1
3. Supposedly, "admin" is the default username and "1234" (without the quotation marks) is the password.
a. Another possibility might be "public" and blank (nothing) for the password.

The google search entry for https://voipfan.net/unlock/mediatrix.php suggests some of these devices were sold locked. The instructions for unlocking it require you to register at the site, which I'm too busy to do so at the moment (and would generally prefer not to, but I might change my mind later using a disposable email address I don't care about).


Reference manual is located at https://archive.org/details/manualzilla ... 1/mode/2up
Refer to page 177

Searching around images online, I see the pic below for a different Mediatrix model. If you eventually find the same (or similar) menu, I would try 600 seconds for default registration refresh time and 3600 seconds for both expiration values.


VoIP unlock key credentials that you need to adhere to are located at https://support.freephoneline.ca/hc/art ... redentials.

[Kwyjor]

Thank you for that thorough investigation. I was concerned I was missing something brazenly obvious.

I should have been prepared with some screenshots of the web interface I am seeing. That was shortsighted of me.

I've never used or even heard of this device before today (I wasn't a mod until 2017).

Yes, as per the manual, this unit dates back to ten years earlier than that.

ETA: Found a very dodgy-looking download for a "Mediatrix Configuration Tool" at https://mediatrix-configuration-tool.so ... /download/ . Unfortunately it seems to use an old version of Java and trying to run it brigs up an error about C:\WINDOWS\SYSTEM32\atiu9pag.dll and a dialog with nonfuctional buttons. It might have tried to download the wrong version of Java.

The manual repeatedly refers to using SNMP, which is apparently a standard service. I am trying to install PRTG Network Monitor which appears to be a recommended tool for this sort of thing, but it also appears that SNMP management is directly available in Windows?

ETA2: A look at https://web.archive.org/web/20130403003 ... umentation suggests I will need the Mediatrix "Mibs", but the download is behind a Javascript thing and has not been cached by archive.org. The current website is not at all helpful.

ETA3: Found my 10-year-old download of "mediatrix_umnv3_2r33_72.zip". Unlke the download of "mediatrix_umnv3_2r32_69.zip" that I found before, this one starts up nicely without cryptically asking for a password, for whatever reason. Unfortunately, attempting to detect a unit at the appropriate IP address yields nothing.

There is yet another version stashed away at https://documentation.media5corp.com/di ... N+Versions and https://documentation.media5corp.com/di ... er+Network .

[Liptonbrisk]

I should have been prepared with some screenshots of the web interface I am seeing. That was shortsighted of me.

I suggest switching to voip2.freephoneline.ca instead. voip2.freephoneline.ca tends to be more reliable over the past few years.
Alternatively, use voip4.freephoneline.ca:6060 (UDP port 6060) to help avoid potential SIP ALG issues.

Anyway, proxy server choice is unlikely to be the issue.

Unfortunately it seems to use an old version of Java

The download site indicates x86; so it's a 32-bit app.

It requires 32-bit Java. Visit https://www.java.com/en/download/manual.jsp. Choose "Windows Offline" and not the 64-bit version. Install 32-bit Java.

32-bit Java apps, such as the Freephoneline desktop application (which is being discontinued), do not work with 64-bit Java.

Running MediatrixConfigApp.jar located in C:\Program Files (x86)\TalkSwitch\Mediatrix Configuration Tool (where C: represents the installation drive) will, afterwards, work.

However, I don't believe that app will be sufficient to help you as it appears to be specific to configuring your device with another provider named Talkswitch (pictures in the app manual suggest not all possible settings are provided to the user). Certainly, checking whether the settings you need are available doesn't hurt though. Talkswitch no longer exists since it was acquired by Fortinet in 2011.

[Liptonbrisk]

The google search entry for https://voipfan.net/unlock/mediatrix.php suggests some of these devices were sold locked. The instructions for unlocking it require you to register at the site, which I'm too busy to do so at the moment (and would generally prefer not to, but I might change my mind later using a disposable email address I don't care about).

Okay, I did take a look at the above link after creating an account. I would suggest that you do the same.

Apparently, Mediatrix 2102s were sold locked from Lingo, Yak WorldCity, and Broadvox. The firmware they originally shipped with, consequently, didn't provide access to all settings.

Unlocking requires downloading configuration files, which are available at voipfan, and sip firmware (no longer available from Mediatrix's website, since it doesn't exist, which could be a roadblock) and uploading it to the device. hfs is located at https://github.com/rejetto/hfs/releases.

The description suggests that if the Mediatrix 2102 is unlocked it should have a more colourful interface (as opposed to a greyish one). Yours already seems "colourful", so perhaps you're in luck (I have no idea).

Once the Mediatrix 2102 is unlocked, do the following:

1. Dial *#*0
2. Enter the IP address you hear into a web browser, followed by ":8080"
ex. 192.168.10.1:8080
3. Username is "root", and password is "5678" (without the quotation marks)

I would try that right now, since your Mediatrix 2102 may already be unlocked.

According to the site, that's the way to get access to all settings. Also, http://greenvegiez.blogspot.com/2013/03 ... fault.html confirms the login details using "root" for username.

If all settings are not accessible due to the ATA being locked (having been sold originally by a service provider) or from not having the right firmware installed, then I would expect that you're going to be out of luck with Freephoneline.

[Liptonbrisk]

The download site indicates x86; so it's a 32-bit app.

It requires 32-bit Java. Visit https://www.java.com/en/download/manual.jsp. Choose "Windows Offline" and not the 64-bit version. Install 32-bit Java.

32-bit Java apps, such as the Freephoneline desktop application (which is being discontinued), do not work with 64-bit Java.

Running MediatrixConfigApp.jar located in C:\Program Files (x86)\TalkSwitch\Mediatrix Configuration Tool (where C: represents the installation drive letter) will, afterwards, work.

However, I don't believe that app will be sufficient to help you as it appears to be specific to configuring your device with another provider named Talkswitch (the app manual suggests not all possible settings are provided to the user). Certainly, checking whether the settings you need are available doesn't hurt though. Talkswitch no longer exists since it was acquired by Fortinet in 2011.

First, try to use a web browser while logging in with “root”.

But what happens if you use that java app and login using

devicelanIP:8080
"root" and "5678" ?

[Kwyjor]

The download site indicates x86; so it's a 32-bit app.

It requires 32-bit Java. Visit https://www.java.com/en/download/manual.jsp. Choose "Windows Offline" and not the 64-bit version. Install 32-bit Java.

Installing the latest 32-bit version of Java indeed allows the Mediatrix Configuration Tool to launch without complaining about atiu9pag.dll. Unfortunately the dialog still does find my Mediatrix unit on the network.

Once the Mediatrix 2102 is unlocked, do the following:

1. Dial *#*0
2. Enter the IP address you hear into a web browser, followed by ":8080"
ex. 192.168.10.1:8080
3. Username is "root", and password is "5678" (without the quotation marks)

I would try that right now, since your Mediatrix 2102 may already be unlocked.

Logging in as "root" on 192.168.10.1 is how I obtained the screenshots above. (I am specifically connecting a computer to the Ethernet port on the back of the Mediatrix unit, since trying to access it via its assigned IP address – 192.168.2.14 – from another computer plugged into my router shows no signs of life.)

I note that the web interface does provide a means for uploading a configuration file, but this is not particularly helpful as of course I do not have a configuration file, nor does it appear that I can find a suitable one for download.

[Liptonbrisk]

Unfortunately the dialog still does find my Mediatrix unit on the network.

I suspect you meant "does not".

I am specifically connecting a computer to the Ethernet port on the back of the Mediatrix unit, since trying to access it via its assigned IP address – 192.168.2.14

This may be due to the Mediatrix using a different subnet and not having DHCP set for its WAN connection type.

The first step is to ensure the Mediatrix 2102 is set to be automatically configured by DHCP (refer to page 30 from https://archive.org/details/manualzilla ... ew=theater), if you want to access it on your LAN. Set WAN connection type to "DHCP". Start on page 29 from that link. After you get everything setup properly first, you can change WAN connection to PPPoE (get your Bell PPPoE username and PPPoE password from Bell and enter it in the Mediatrix 2012 UI).

When installed for normal SIP/VoIP usage (to the back of your Bell Hub), do you hear a LAN IP address when dialing *#*0
? The second step is to ensure the Mediatrix 2102 is being assigned a local IP address on your LAN by whatever router you're using (presumably, your Bell Hub, which is a modem/router combo). That appears to be happening with 192.168.2.14.


Afterwards, dial *#*0 and access the ATA using the IP address you hear, followed by ":8080". Try the "root" username with "5678" for the password.
If that doesn't work, try the same IP without ":8080", and use ""admin" with a password of "1234".

And if the Mediatrix 2102 isn't obtaining internet (WAN) access, obviously it can't connect to FPL.

By the way the proxy port with voip.freephoneline.ca and voip2.freephoneline.ca should be set to 5060 (UDP). I'm not sure if Mediatrix 2102 absolutely requires the register host to be defined since the proxy and registration server are the same with FPL. Regardless the port is UDP 5060.

Logging in as "root" on 192.168.10.1 is how I obtained the screenshots above.

Okay, then it seems possible to me that your Mediatrix 2102 is unlocked already.

[Kwyjor]

When installed for normal SIP/VoIP usage (to the back of your modem/router combo or modem), do you hear a LAN IP address when dialing *#*0
?

Yes, it does. As per my first post I was using this device without difficulty with my previous VoIP provider.

On that note , another look at the Management -> Configuration File tab reveals that the unit does indeed appear to be locked to my previous VoIP provider's configuration file server host. There's something obvious I probably should have checked.

I suppose I should try the unlock instructions at https://voipfan.net/unlock/mediatrix.php and perhaps that will enable the Unit Manager Network tool.

[Liptonbrisk]

Yes, it does. As per my first post I was using this device without difficulty with my previous VoIP provider.

Yes, I read that. However, that doesn't imply that you could configure the ATA locally using the Bell Hub's assigned LAN IP address for the Mediatrix 2102 at that point. If you couldn't before, then it still makes sense that you can't modify it while trying to access its assigned LAN IP from the Bell Hub.

The ATA's WAN access would need to be set to DHCP so that it's on the same subnet as the Bell Hub's DHCP server, if configurable LAN access is an option (it may not be) other than the default the device was assigned. Ensure that WAN access is not set to "Static". SInce you mention the device is locked to your previous service provider, making changes to the WAN access setting may not make a difference anyway.

On that note , another look at the Management -> Configuration File tab reveals that the unit does indeed appear to be locked to my previous VoIP provider's configuration file server host. There's something obvious I probably should have checked.

If that configuration link isn't deleted somehow, when rebooting, the ATA can automatically reconnect to the server. When rebooting and/or performing a factory reset, I recommend disconnecting the ATA from the internet. If you see a configuration URL, ensure that it's deleted.

Also, I recommend contacting your previous provider to see if they will assist removing the ATA from their configuration server. If they won't and if they were using modified firmware, you may be out of luck.

I suppose I should try the unlock instructions at https://voipfan.net/unlock/mediatrix.php and perhaps that will enable the Unit Manager Network tool.

Except I can't find the firmware file that site is referencing

[Kwyjor]

Okay! Clearly a factory reset is the obvious first thing I should have done.

Simply holding the reset button and reconnecting the power as per https://voipfan.net/unlock/mediatrix.php has enabled me to access the web interface at 192.168.2.14:8080 (as root/5678) from another computer plugged into my router, and has cleared any sign of my old VoIP provider from the web interface. And I can now start the Mediatrix Configuration Tool and access the unit through the Unit Manager Network. Progress!

Unfortunately the Mediatrix Configuration Tool offers no means of accessing the Registration Expiration, and neither does the Unit Manager Network program - at least not directly.

The Unit Manager Network tool does let me transfer a Configuration File to and from the unit, which thankfully is completely in ASCII text. I can open it in Notepad and find the "sipRegistrationProposedExpirationValue" discussed on page 177 of the aforementioned https://archive.org/details/manualzilla ... 1/mode/2up . I can set this value to "3600" instead of "0", save the file, transfer it using Unit Manager Network, and reboot the unit – but then if I redownload the configuration file, it is set to "0" again, sigh.

That's enough good times for now; I'll take another poke at it later. Thank you for your patience and your assistance.

[Liptonbrisk]

but then if I redownload the configuration file, it is set to "0" again, sigh

Can you please clarify whether you mean the Mediatrix 2102 is downloading a configuration file from your previous service provider automatically—as opposed to you manually downloading a file and applying it yourself?

Is it possible to disconnect the device from the internet, delete the configuration link from the device, and then perform a factory reset?

It’s important to keep the ATA disconnected from the internet when deleting the server path, saving the change, and then performing a factory reset. After performing the factory reset, ensure the configuration server path associated with the original service provider is still deleted.

[Liptonbrisk]

I tried to look around a bit more for official, unmodified Mediatrix 2102 firmware. https://documentation.media5corp.com/ didn't help.

Mediatrix is a subsidiary of Media5 Corporation.
Perhaps someone there can provide you with the file: https://www.m5t.com/pages/contact-us.

They have a phone number in Quebec: 819-829-8749
Media5 Corporation
130 Sauve Street, Sherbrooke, Quebec
Canada
J1L 0A7

[Kwyjor]

Okay! More pieces are coming together. Maybe.

I found a "configuration guide" at https://usermanual.wiki/Document/Mediat ... 133371.pdf which suggests accessing advanced settings by using "Edit SNMP..." in Unit Manager Network. (This is also seen at https://www.voiptalk.org/products/mtrixsetup .) Doing this on my machine brought up an unhelpful "Error Loading mib" message - until I downloaded and installed the "MIB pack" from https://documentation.media5corp.com/di ... N+Versions . This, at last, lets me change the sipRegistrationProposedExpirationValue in UMN to 3600! And the value is definitely saved, because if I transfer the configuration file again, the correct value appears!

... Except it's still not working. https://www.freephoneline.ca/showSipSettings still says I'm disconnected, and I still don't get a dial tone.

Can you please clarify whether you mean the Mediatrix 2102 is downloading a configuration file from your previous service provider automatically—as opposed to you manually downloading a file and applying it yourself?

By "downloading" I meant "transfer the configuration file back from the unit". It is definitely transferring the configuration file from the unit since if I change the values in the web interface, those same values appear in the transferred configuration file. But for whatever reason changing values in the configuration file and then transferring the configuration file back again doesn't seem to change anything, even though the Unit Manager Network reports "success" when I do that.

The "end user site" in the web interface also has a page for uploading a configuration file, but attempting to use it just brings up a message stating "Reboot Failed. Error while uploading configuration file".

But this is all beside the point since I can now, in theory, edit everything in UMN. But what is missing?

I suppose the next step is to see if I can figure out how to enable some sort of logging and thereby obtain a useful error message.

[Liptonbrisk]

This, at last, lets me change the sipRegistrationProposedExpirationValue in UMN to 3600!

It's difficult to know whether settings reset at periodic intervals when using modified firmware that has been previously locked. I'm pretty tired and haven't looked carefully, but ensure automatic firmware updates aren't enabled: https://archive.org/details/manualzilla ... ew=theater (pages 134-136).



1) Try switching to voip4.freephoneline.ca:6060 (UDP port 6060) for the proxy and registration server. The server port needs to 6060 (UDP) when using voip4.freephoneline.ca. I have no idea if you've been temporarily IP banned by the proxy server that you were using before for making too many registration attempts within a short interval.


2) Use 600 seconds for sipReRegistrationTime (page 176). This is what some ATAs and IP Phones are set to (they re-register every 50 minutes, which works fine with Freephoneline and doesn't lead to account blocks). This means your device will attempt registration again every 50 minutes.

"Define the time, in seconds, at which a registered unit begins updating its registration before the registration expiration in the sipReRegistrationTime variable. For instance, if the variable is set to 43 and the registration lasts one hour, the unit will send new REGISTER requests 59 minutes and 17 seconds after receiving the registration acknowledgement (43 seconds before the unit becomes unregistered)."

3) sipinteropDefaultRegistrationExpiration should also be 3600 seconds

4) Freephoneline only uses UDP transport only (pages 171 and 172).

5) This is important: I can't find a menu option where Keep-alive packets are sent to keep NAT associations open. They should be sent every 20 seconds, but the only place I see to enable keep-alive is in the STUN menu settings (page 36, step 5), and an external STUN server shouldn't be specified if possible. STUN introduces an additional point of failure. When the STUN server drops, so does your VoIP service. NAT keepalive doesn't have anything to do with your current registration issue however, but it might later, and without keepalive packets being sent every 20 seconds (or so), then chances are NAT holes/associations will close and, in turn, incoming calls will stop working after awhile.

I suppose the next step is to see if I can figure out how to enable some sort of logging and thereby obtain a useful error message.

Page 236 might help
https://archive.org/details/manualzilla ... ew=theater

[Kwyjor]

Are the fields in my previous post viewtopic.php?p=81706#p81706 filled out correctly? Is it normal to have a blank "SIP Domain" and for "Registrar Port" and "Proxy Port" set to 0, or should those be something else?

Likewise, is it normal for my realm, username, and password to be set under "User Agent Authenticaion", or should that information be under "Unit Authentication"?

I have managed to enable logging by changing the "syslogMsgLocalMaxNbr" in UMN (for some reason the default value is 0), but all I am getting is:

Code: Select all

Web Server started successfully. Listening on: 192.168.10.1:80 	HttpServer 	Dec 31 19:00:05 	Informational
  	DHCP lease acquired. 	IpAddressManager 	Dec 31 19:00:07 	Informational
  	Web Server started successfully. Listening on: 192.168.10.1:80 192.168.2.14:8080/Res/ 192.168.2.14:8080 	HttpServer 	Dec 31 19:00:07 	Informational
  	Signaling type of service (TOS) value set to 184. 	SipEngine 	Aug 25 20:58:34 	Informational
  	Signaling IEEE 802.1Q (VLAN) tagging value set to 6. 	SipEngine 	Aug 25 20:58:34 	Informational
  	Sip signaling logging disabled. 	SipEngine 	Aug 25 20:58:34 	Informational
  	Sip signaling logging disabled. 	SipEngine 	Aug 25 20:58:34 	Informational
  	Sip signaling logging disabled. 	SipEngine 	Aug 25 20:58:34 	Informational
  	SIP transport disabled (tcp). 	SipEngine 	Aug 25 20:58:34 	Informational
  	L1 client authentication failed. 	SipEngine 	Aug 25 20:58:34 	Error
  	L1 registration failed, authentication failure. Will retry in 2 minutes. 	SipEngine 	Aug 25 20:58:34 	Error
  	L2 client authentication failed. 	SipEngine 	Aug 25 20:58:34 	Error
  	L2 registration failed, authentication failure. Will retry in 2 minutes. 	SipEngine 	Aug 25 20:58:34 	Error

MizuDroid, I should add, is still connecting without problems. (I always make sure to exit MizuDroid after I check it.)

Attempting to use "voip4.freephoneline.ca" and "6060" in place of "voip.freephoneline.ca" and "5060" is not making any difference.

Other things I have tried changing:
I have changed sipReRegistrationTime from 60 to 600.
sipinteropDefaultRegistrationExpiration is set to 3600 seconds, the default value.
I have also tried setting sipUAMinimumSessionExpirationDelay to 3600 instead of 1800 (page 164).
I also changed sipTransportRegistrationEnable from "disable" to "enable".
I have changed sipPublicationRefreshTime from 60 to 600 and sipPublicationProposedExpirationValue from 1800 to 3600. Oddly, there is nothing about sipPublication in the manual.

ETA: I should also add that changing the three instances of "freephoneline" to "preephoneline" does change the message, so it is definitely reading the values I am inputting, at least.

Code: Select all

 	The domain name "voip.preephoneline.ca" could not be resolved to an IP address. 	SystemManager 	Aug 25 23:07:50 	Warning
  	The domain name "voip.preephoneline.ca" could not be resolved to an IP address. 	SystemManager 	Aug 25 23:07:50 	Warning
  	L1 registration failed, registrar unreachable. Will retry in 2 minutes. 	SipEngine 	Aug 25 23:07:50 	Error
  	L2 registration failed, registrar unreachable. Will retry in 2 minutes. 	SipEngine 	Aug 25 23:07:50 	Error

ETA2: Trying "voip4.freephoneline.ca" and "6060" again just now yields

Code: Select all

L1 registration failed, registrar unreachable. Will retry in 2 minutes. 	SipEngine 	Aug 25 23:12:34 	Error
L2 registration failed, registrar unreachable. Will retry in 2 minutes. 	SipEngine 	Aug 25 23:12:35 	Error

Using "voip4.freephoneline.ca:6060" just for good measure produces

Code: Select all

 	The domain name "voip4.freephoneline.ca:6060" could not be resolved to an IP address. 	SystemManager 	Aug 25 23:17:20 	Warning
  	The domain name "voip4.freephoneline.ca:6060" could not be resolved to an IP address. 	SystemManager 	Aug 25 23:17:20 	Warning
  	L1 registration failed, registrar unreachable. Will retry in 2 minutes. 	SipEngine 	Aug 25 23:17:20 	Error
  	L2 registration failed, registrar unreachable. Will retry in 2 minutes. 	SipEngine 	Aug 25 23:17:20 	Error
  	SNMP: The notification "msTrapConfigInformation (#700)" could not be sent to msHost "0.0.0.0" and msTrapPort 162.

Specifying "voip4.freephoneline.ca" and "6060" but also specifying "Registrar Port" and "Proxy Port" as 6060 yields:

Code: Select all

L1 client authentication failed. 	SipEngine 	Aug 25 23:22:02 	Error
  	L1 registration failed, authentication failure. Will retry in 2 minutes. 	SipEngine 	Aug 25 23:22:02 	Error
  	L2 client authentication failed. 	SipEngine 	Aug 25 23:22:02 	Error
  	L2 registration failed, authentication failure. Will retry in 2 minutes. 	SipEngine 	Aug 25 23:22:02 	Error

[Liptonbrisk]

Are the fields in my previous post viewtopic.php?p=81706#p81706 filled out correctly?

You're asking me about a device I've never heard of before until you mentioned it, so all I can do is scan the manual (which I'm not being paid to do; I don't work for Fongo) and guess. Also, I'm uncertain if you're using official, unmodified firmware.

Is it normal to have a blank "SIP Domain"

It depends on the SIP client, and I can't find anything about "SIP domain" in the manual.

Normally, I would try "voip4.freephoneline.ca" (without quotation marks), when using the example of voip4.freephoneline.ca:6060 in my previous instructions, for the SIP domain. Otherwise, try freephoneline.ca.

I ignored SIP domain, thinking that perhaps you were more aware of this device than I am, and I thought if you're defining the both the registrar and proxy server anyway, then I'm not sure why SIP domain matters for Freephoneline, specifically.

and for "Registrar Port" and "Proxy Port" set to 0, or should those be something else?

When using voip4.freephoneline.ca:6060, the UDP port, 6060, must absolutely be specified.

When using voip.freephoneline.ca or voip2.freephoneline.ca, 5060 should be the value for those ports.

0 represents the default value, according to the manual, which I interpreted to mean, perhaps incorrectly, UDP 5060.
It's safer to specify the UDP port as indicated above.

Likewise, is it normal for my realm, username, and password to be set under "User Agent Authenticaion", or should that information be under "Unit Authentication"?

Again, I've never used this device, but Unit should mean the whole device. I would use User Agent Authentication.

Sip signaling logging disabled.

That's what you want enabled in order to see exactly what's happening. Unfortunately, I'm not finding a way to enable it in the manual so far.

L1 client authentication failed. SipEngine Aug 25 20:58:34 Error
L1 registration failed, authentication failure. Will retry in 2 minutes. SipEngine Aug 25 20:58:34 Error
L2 client authentication failed. SipEngine Aug 25 20:58:34 Error
L2 registration failed, authentication failure. Will retry in 2 minutes. SipEngine Aug 25 20:58:34 Error

Only attempt to register L1.

At least the failed registration retry interval appears to be 120 seconds, which is what you want.

MizuDroid, I should add, is still connecting without problems. (I always make sure to exit MizuDroid after I check it.)

Ensure the account is unregistered in MizuDroid after exiting.

I have also tried setting sipUAMinimumSessionExpirationDelay to 3600 instead of 1800 (page 164).

That's the SIP session timer and should have no bearing on your initial authentication failure issue.

[Liptonbrisk]

Using "voip4.freephoneline.ca:6060" just for good measure produces
The domain name "voip4.freephoneline.ca:6060" could not be resolved to an IP address.

That's normal and expected.

Server needs to be specified as voip4.freephoneline.ca
Port is 6060

L1 client authentication failed

Without SIP logs, it's difficult to determine what's going on.



Realm = voip4.freephoneline.ca


When you attempt to make an outbound call, what do you hear?

Do you hear an account blocked message?
Do you hear any error message?

[Kwyjor]

You're asking me about a device I've never heard of before until you mentioned it, so all I can do is scan the manual (which I'm not being paid to do; I don't work for Fongo) and guess.

Of course. My desperate hope is that some of these settings resemble some other settings you may have seen before.

Sip signaling logging disabled.

That's what you want enabled in order to see exactly what's happening. Unfortunately, I'm not finding a way to enable it in the manual so far.

Yes, that would be nice, wouldn't it? I'm not sure where to set that either, and I can't find it in the SNMP either.

ETA: Enabling "mxDebugSignalingLogEnable" in UMN (described as "Enable the logging client debugging tool for IP telephony signaling") yields "Sip signaling logging will be sent to 192.168.0.10:6000" in the log. I can apparently change "mxDebugSignalingLogHost" and "mxDebugSignalingLogPort" to whatever I want. My only guess is to try to set up Netcat to see if it can receive anything.

Unfortunately attempting to clear the settings under Port 2 in the "SIP User Configuration" just produces an unhelpful "Wrong value" message. There doesn't seem to be a way to disable "L2 client", whatever that is.

When you attempt to make an outbound call, what do you hear?

Do you hear an account blocked message?
Do you hear any error message?

Just a fast busy signal. Same as I get when the unit is completely disconnected.

[Liptonbrisk]

Yes, that would be nice, wouldn't it?

It's also frustrating not to have access to all settings within the web user interface.

Initially, I thought the problem might be related to incorrect username or password, but Freephoneline will still register when those are wrong. You'll just hear an error message.

What happens after setting "Validate Realm" to "Disable" under "User Agent Interface" for Port 1 and clicking "Submit"?

[Kwyjor]

What happens after setting "Validate Realm" to "Disable" and clicking "Submit"?

OH MY GAWD THAT WAS IT

BLAAAAAAAH.

Holy bork I figured it was going to be something like that in the end.

This has been fun, hasn't it? If you do not accept donations, may I offer to make one to a charity of your choice?

ETA: The only remaining catch is that I still can't stop it from trying to register L2. Even editing the value through SNMP in UMN rejects trying to clear it. That's not going to come back to haunt me, I hope.

[Liptonbrisk]

This has been, hasn't it?

Unfortunately, I still don't know what's going on with L2.

Edit: Maybe I’m a fool and L2 means the logging level instead of another instance of a line (L2 port) trying to register.

More importantly (and this is pretty important, as I mentioned previously), I don't know where to set Keep-alive packets to 20 seconds.
Anyway, hopefully incoming calls still work after a few hours of no activity/calls.

The situation is not ideal because I really don't know where to find appropriate settings in your device.

If you do not accept donations, may I offer to make one to a charity of your choice?

Thank you for the kind offer. It’s not necessary. I know money is scarce for a lot of people; I do think (decent) food banks are useful.

Anyway, again, I don't know if your problems are completely solved, but I can hope.

I'll probably be unavailable tomorrow afternoon and early evening.

[Liptonbrisk]

I think this thread's more appropriate location is in the Device Configuration Sharing section, so I'll move it there.