FreePBX | Register | Issues | Wiki | Portal | Support

DB20 Config

(enderst) #1

Using the wiki, I get to the last step “Save and Reboot” basestation reboots and it doesn’t pull a config.
Watching the httpd logs, I see the basestation attempting “GET /Config/.cfg”.
No /Config/ directory in /var/www/html/ nor /tftpboot/

Is there a step missing in the wiki?

(Neal Garrett) #2

The redirect didn’t work for me either. I had to browse into the base station and manually setup where to find the server and the credentials to get logged into it. Then it was able to pull the config needed.

(enderst) #3

Working for me now.
The wiki has been updated since and works down to the configuration server section. I used “Via the DECT basestation web GUI” and all is well.

Would be nice if the redirect service worked, would be even better if the ticketing recognized these phones. Only sees the s phones. Good luck getting support if you need it.

(Tony Lewis) #4

Ticketing system does recognized the dect phones. That was added awhile ago. If redirect is not working please let support know as it should be working and was when we did all the documentation.

(enderst) #5

Thanks Tony.
The whole time I’ve been using the MAC addresses in the registered product search instead of the model name. Too many s phones to scroll through so just a habit to use the MAC. The base station MAC are not searchable is what it comes down to for my fail.

I haven’t deployed it yet so I’ll be resetting and configuring it for a while. We have several customers wanting a cordless solution.

(Jerry Riggin) #6

I still can’t get my base station to hit my PBXact. I see in portal it has hit Sangoma over 63 thousand times. The provisioning URL/FQDN in portal works for 36 S500/705s. The default initial provisioning URL in the DB20 GUI is and not like it is in the desk phones. I see zero attempts from the DB20 MAC in httpd access or error logs. (Though I do see a bajillion “File does not exist: /tftpboot/ringtones/formatted/ringX.bin” in the error_log for other phones.)

Where in the DB20 GUI do you place the provisioning URL? Should it be exactly the same as the IP/FQDN I have for the working S500s in the Sangoma Portal?

(enderst) #7

Follow the wiki:

When you get to “Adding a Configuration Server to a DECT Basestation” use the steps for “Via the DECT basestation web GUI”

You should see the base station pull its config.

(Jerry Riggin) #8

Thanks, enderst.

I just looked in the DB20 Sys Log and it appears it is getting the provisioning URL from Sangoma, but failing for to hit that URL:

loc3 .Info  1970-01-01T00:00:12Z 165-[ Configuration server: path: Config/ Type: https] 
loc3 .Info  1970-01-01T00:00:12Z 165-[ Directory server not specified] 
loc0 .Info  1970-01-01T00:00:13Z 165-[ DECT master mode] 
loc3 .Info  1970-01-01T00:00:16Z 165-[ Redirecting to server: 
loc3 .Info  1970-01-01T00:02:59Z 165-[ DNS lookup of [user] failed] 
loc3 .Info  1970-01-01T00:02:59Z 165-[ No Timestamps updated.] 

( [user], [password] and [MAC] substitued for actual valid credentials.)

So the DB20 is contacting Sangoma and getting the FQDN, but the DB20 is not parsing it correctly and winds up doing a DNS lookup on the user name. Making a bug report.

(Jerry Riggin) #9

Well, it says it was provisioned from the correct server. Here’s the Sys Log after reboot:

loc3 .Info  1970-01-01T00:00:11Z 165-[ Configuration server: path: Config/ Type: http] 
loc3 .Info  1970-01-01T00:00:11Z 165-[ Directory server not specified] 
loc0 .Info  1970-01-01T00:00:12Z 165-[ DECT master mode] 
loc3 .Info  1970-01-01T00:00:12Z 165-[ Download of Config/005058700079.cfg from[]:84 succeeded; File Changed] 
loc3 .Info  1970-01-01T00:00:12Z 165-[ VoIP Number of configurations parsed: 0] 
loc3 .Info  1970-01-01T00:00:12Z 165-[ DECT Number of configurations parsed: 0] 
loc3 .Info  1970-01-01T00:00:12Z 165-[ Successful parsing of Config/005058700079.cfg from[]:84] 
loc3 .Info  1970-01-01T00:00:12Z 165-[ No Timestamps updated....] 
loc3 .Info  1970-01-01T00:00:12Z 165-[ No Timestamps updated.] 
Auth .Info  1970-01-01T00:00:12Z 165-[ No flash certificates found] 
loc7 .Info  1970-01-01T00:00:12Z 165-[ Firmware Device DB20N Version:0400 Branch:0003 Rfpi:131A09F300] 
loc7 .Info  1970-01-01T00:00:12Z 165-[ DECT Mode: US] 
loc7 .Info  1970-01-01T00:00:12Z 165-[ System Mode: (b3/55)] 
loc7 .Info  1970-01-01T00:00:12Z 165-[ Normal Reboot] 
loc7 .Info  1970-01-01T00:00:12Z 165-[ DECT protocol delay timer started (single cell)] 
loc7 .Info  1970-01-01T00:00:27Z 165-[ DECT protocol activated, delay passed (single cell)] 

But it doesn’t appear to have provisioned anything. I don’t see the extensions I configured for it in EPM, and obviously it did not get a time server. I don’t know if that is part of the provisioning for this device, but the file 005058700079.cfg has no data – only warning not to hand modify. In EPM, when I open the DB20 model in sangoma_default, it is empty. I have EPM

I still can’t register extensions. The 2 extensions appear correctly configured for the DB20 in EPM, but they don’t show up in the “Extensions” page of the DB20 GUI. On the handset, when I navigate to Connectivity > Register and enter “0000” it says, “Registering” for about a minute, then goes to home screen and says “deregistered.”

Anyone have advice on what to do next? Do I have to manually configure the extensions in the DB20 GUI before the handsets will register?

(enderst) #10

Sounds like the same problem I had yesterday, an empty config getting generated.
Ended up calling support and they downgraded my EPM to and it started working.

(Lorne Gaetz) #11

Edit: This should not be an issue any more, just upgrade EPM to current.

This is the problem. Depending on your PBX version, you want to be running either of the following versions:

you can down/upgrade using:

fwconsole ma downloadinstall endpoint --tag xxxxxx

substitute the appropriate epm ver in place of the x’s. Browse to EPM, Extension Mapping and rebuild your DB20 device then check the content of Config/<mac>.cfg you should now see actual content. Once the file is populated, re-provision the basestation and then pair the handset.

You may run into error notification(s) in the rebuild process, in which case do a ctrl-F5 hard browser refresh and try again.

(enderst) #12

I’m guessing my original issue was the same but when I said it was fixed there must have been an update to EPM (I don’t remember now). The problem I had yesterday was on a completely different system, so must have been a regression.

(Jerry Riggin) #13

I downgraded the module, and the DB20 now has extensions and timeserver. In the morning I’ll see if they can register a handset now. Looks like they will be able.

Thanks, Lorne.

(Brian Ladd) #14

I had to change the URL to in order to get my DB20 to talk to the Sangoma portal.

(Tony Lewis) #15

This was fixed. A recent DNS change got missed for Dect and we have now updated that. Sorry about that.

(Brian Ladd) #16

Thanks for quick turnaround! I came back here to reference the ticket but you beat me to it! Have a good Christmas.