You are here

GS 1625

5 posts / 0 new
Last post
GS 1625

Hello, having problems getting my GP-1625 sip account to register with my RPIPBX via a dtd linked Areden node.

Trying to put Port forwarding rules in IP tables of DtD Aredn node, and it  is wanting IP address of the dtdlink on this node. Not sure where to find that info.

The Wifi IP for the DtD linked node is Thanks



nc8q's picture
RasPBX - Asterisk for Raspberry Pi

My RasRPIs have an advertised IP address.
I have no port forward.
'nc8q-raspbx[.local.mesh]' resolves to an IP address on every node on the network.
I have configured the RasPBX on one of my home nodes:

Image Attachments: 
nc8q's picture
Looks like this on the network

Your IP phone may register by using either the IP address or the domain name of the PBX.
Note 'nc8q-raspbx.local.mesh' ( in image.
Short name should also resolve: example 'nc8q-raspbx' >

Image Attachments: 
N2MH's picture
Should be pretty easy...


Setting up your phone and pbx should be pretty straightforward, but there's some things you need to do besides configuring your phone. This assumes that the phone and pbx are on nodes on the same network and that the nodes know how to talk to each other. You should not have to fiddle around with port forwarding if both the phone and pbx are on the same mesh network. If this is not your setup, then more information will be needed. In addition, sip, which is how your phone talks to a pbx, has been known to have problems when port forwarded.

On the PBX side of things

1. In the node that serves the pbx, you need to reserve the ip address of the pbx. This will ensure that the pbx address will not change and always retain the same ip address. Note that you do not have to make it a clickable url unless you want that behavior.
2. There is an extension configured in the pbx for the phone you wish to connect.

On the phone side

1. Ensure that the phone is set for dhcp - that is, it is set to grab an ip address from the node it is plugged into.
2. In the phone, at a minimum, you need to configure a) the ip address of the pbx, b) it's extension number (which has to match what is configured in the pbx) and c) a secret (password) that must also match what is in the pbx for this extension.

You will probably find multiple places in the phone to enter an extension number. One may be called simply "extension", another may be called "authentication extension", or other something else. For the purposes of getting up and running with a minimum of fuss, enter the same extension number in everything that looks like it needs an extension number. Once the phone is up and running, you can always try to remove one field at a time until the phone stops working if you wish to clean up things.

Likewise, some phones need a proxy ip address in addition to the pbx ip address. At first, leave the proxy setting blank and only set it to the pbx ip address if all else fails. Normally, you should not need a proxy.

Lastly, when first getting the phone to talk to the pbx, bring it up on the same node as the pbx. This will ensure that there are no network issues between the phone and the pbx. Once the phone is up and running, then move it to your other node and it should come up on that node. You may need to power the phone down before moving it just to clear it out. If the network is good, the phone should come right up and work just like it did on the other node. In fact, you should now be able to move that phone to any other node on your mesh network and it should work.

73, Mark, N2MH

PS Let us know how you make out.


I have some 1625 running and
I have some 1625 running and sometimes it takes sometime to connect to the PBX... Usually less than 5minutes, I had one that took like 30minutes to finally connect with the PBX on the first run.

When I first configured the PBX, I had to add a firewall exception for LAN IPs...

Don't forget it may takes sometime for the DNS to propagates depending on the network size.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer