I am unable to get my PBX to register an extension over the mesh. See the diagram for my setup.
If I remove the mesh link, the registration works fine. All the components work fine individually.
What am I doing wrong and how can I fix it?
Bob W8ERD
If I remove the mesh link, the registration works fine. All the components work fine individually.
What am I doing wrong and how can I fix it?
Bob W8ERD
File Attachment:
Hi, Bob:
My PBX and all its configured extensions are part of a local AREDN Network.
My PBX is a LAN service of one of my AREDN nodes.
My PBX is not a service on the LAN of my home router.
There may be reason why you put your PBX outside your AREDN network.
Is there a requirement for having your PBX on the LAN of your home router
instead of the LAN of your AR300 or Bullet?
Your topic:
"PBX extension registration over mesh "
However, from your PDF, the TP-Link router and the PBX are outside of your 'mesh'.
Please rephrase.
73, Chuck
Without the mesh, it registers fine.
Bob W8ERD
There are many other extensions connected to the pbx via the router, and they work OK.
I have no services defined. Please send me the service definitions I need to use.
I am attaching the big picture to show you what I am trying to do.
Bob W8ERD
Nice picture of the system.
The Bullet will need to share its WAN.
3.22.6.0 and earlier will need: 'Allow others to use my WAN' enabled (not default) and
'Prevent LAN devices from accessing WAN' left disabled: (default).
In the current production:
aredn.@wan[0].olsrd_gw enabled (this is a change from default)
The 'Wireless Router' likely does not 'advertise' the PBX with a domain name, so
registration will be by IP address at the 'Mesh telephone'.
I think.
73, Chuck
Bob W8ERD
1) Was my speculation correct that the router is only operating as a switch and all devices are on the LAN side of the router?
2) Is there a WAN connection to the router? If yes, what?
3) Is the router acting as a DHCP server?
4) Is the AREDN node that is connected to the router acting as a DHCP server?
5) Is the phone trying to reach the PBX via an IP address or a URL?
More after those answers....
2. No
3. yes
4. yes.
5. IP address
Bob W8ERD. Thanks for your help!
For this application, the easiest would be to disable DHCP on the router and let the mesh node that is connected to the router function as the DHCP server. You would need to change the mode on the AREDN to something larger than the default 5 devices or else you will run out of DHCP addresses. Doing it this way would result in all devices getting a 10.x.y.z AREDN mesh IP address. You would also want to assign a DHCP reservation in the AREDN node for the PBX so that it always gets the same IP address. Note, if you set a static IP in the PBX (must be in the address space for the AREDN LAN given by the AREDN node), still give the PBX a DHCP reservation in order to prevent the AREDN node from assigning that IP to some other device. Then you would simply tell the phone that the PBX can be found at whatever 10.x.y.z address it is assigned.
One more comment. Although I said this would be the easiest, it may not be the best - especially if you later plan on adding internet into the equation. But that's a discussion for a later day.
Turned off dhcp in the router.
turned on dhcp in the bullet
checked the "allow others..."box in the bullet.
Now - The bullet is doing nothing. I cannot log into it even with its IP address.
Other nodes do not see the bullet as being on the air. It has lights.
I cannot log into the router.
I rebooted the bullet.No change.
Rebooted the router. No change.
Restarted PC several times. No change.
No Hope
Is the Bullet getting an IP address from the Wireless Router?
No, without a VLAN switch there is no WAN available on the bullet.
Leave DHCP enabled on the Wireless Router, Bullet, and AR300M.
In: https://www.arednmesh.org/sites/default/files/portable%20post%20office.pdf
If you could swap the AR300M and the Bullet, the AR300M has a WAN port to access the Wireless Router and
obtain an IP address on the Wireless Router's LAN.
Option 2:
Remove the Bullet and let the AR300M operate in client Wi-Fi mode to connect to the Wireless Router.
Option 3:
Swap the Bullet and AR300M
IP Phone gets an IP address from the Bullet's LAN.
Bullet RF links with the AR300M.
The WAN port of the AR300M gets an IP address from the Wireless Router.
Now it seems to be back to normal. Its dhcp is on.
I was unable to log into the bullet and it did not show up as a neighbor in the ar300.
Cycling its power did not help. It has lights on, but is otherwise dead. Should I push its reset button?
I have another bullet which I substituted for the first one. I can log into it and it shows up as a neighbor in the AR300.
Its DHCP is off.
The AR300 DHCP is on.
So it seems like we are back to square one.
Now starting from here, what should I change?
Thanks for all your help!
Bob W8ERD
Hi, Jim:
In my #13
https://www.arednmesh.org/comment/20242#comment-20242
and using Bob's diagram
https://www.arednmesh.org/sites/default/files/portable%20post%20office.pdf
The WAN of the Bullet would be in the LAN of the Wireless Router.
But Bob has no VLAN switch, thus no access to the WAN of the Bullet.
Option 2:
The Bullet (and its unavailable WAN) is omitted.
The AR300M configured as a Wi-Fi client would be in the LAN of the Wireless Router.
The IP Phone gets an IP address from the AR300M (AR300M DHCP is enabled to serve the IP Phone).
Option 3:
The Bullet and the AR300M swap places in the diagram.
The Bullet is default AREDN and provides an IP address to the IP Phone via DHCP.
The AR300M is default AREDN, its WAN port connects to a LAN port on the Wireless Router.
The Wi-Fi of the AR300M is the LAN of the Wireless Router.
The LAN of the AR300M is separate and unused.
There is no more than 1 DHCP server on any LAN.
I think. :-|
3s, Chuck
This whole thing would work if the router has DHCP disabled (so it is functioning ONLY as a switch), the Bullet provides DHCP for everything on the drawing. That would mean everything on the drawing would get a 10.x.y.z address from the Bullet. Otherwise there needs to be something that knows how to route and be VLAN aware. The hardware shown does not have that capability.
I see 11 IP addresses needed, so need at a minimum:
/setup '13 Host Direct' on the Bullet.
The mesh phone and the AR300. together with a battery, make up a portable telephone system, which I plan to carry around in the field.
Bob
At present you are mixing SISO and MIMO.
https://arednmesh.readthedocs.io/en/latest/arednHow-toGuides/siso-mimo.html
"Whenever possible try not to mix device types on radio links.
As a general rule, use MIMO-to-MIMO for most types of RF links."
I see 3 options
Option 1:
Use the Bullet with factory OS configured as a Bridge on the LAN of the Wi-Fi Router.
Let the AR300M be a client to the Wireless Router using the Bullet as a transparent bridge.
Option 2:
Get a VLAN switch so that the WAN of the Bullet can get an IP address from the LAN of the Wi-Fi Router.
Option 3:
Omit the Bullet and configure the AR300M as a client to the Wireless Router.
3s, Chuck
What about the spacing and polarization of the 2 antennas?
Bob W8ERD
Turned off dhcp in the router.
Turned on dhcp in the bullet and set to 13 hosts.
Very mixed results.
The bullet registers:
5 cell phones (all of them)
only 2 corded phones (out of 4)
not the router
not the pbx
Suggestions?
Bob W8ERD
To be semanticly correct:
The Bullet does not register, but it may offer and reserve IP addresses via DHCP.
VoIP phones 'register' with a PBX.
In the configuration offered, the Wireless Router does not get an IP address...it is only a switch.
Uh, not sure about the pbx not getting an IP address.
View/share '/cgi-bin/ports' to ensure that 13 addresses were not consumed somehow.
In your diagram, I am seeing 12 devices needing an IP address via DHCP, yet there is no workstation.
Could a workstation or laptop or tablet or other device be consuming the 13th IP address?
73, Chuck
Please tell me what to do to get View/share....
Yes the PC is attached to the router. The bullet does not show it as having an assigned address, yet it works if I log into the
IP address of the bullet.
Bob W8ERD
Bob
"View/share '/cgi-bin/ports' to ensure that 13 addresses were not consumed somehow."
View: A screen capture attached to a reply to #23.
Share: Using your mouse...click and drag and copy the portion of the screen containing 'Current DHCP Leases' pasted into a reply to #23
e.g.
As another experiment, I set to the bullet to 29 hosts.
No. change.It still assined addreses to 2 of the 4 corded phonesand nothing else.
Bob. W8ERD
No. change.It still assined addreses to 2 of the 4 corded phonesand nothing else."
Hi, Bob:
Good,
Let us stay with 29 hosts as you have 12 in your diagram.
Let me try some tests with my bullet and some other devices with 3.22.8.0 and see if I can get 12+ reservations.
With 3.22.8.0:
Anyone else out there with a node that does > 12 IP reservations?
...with a Bullet that does > 12 IP reservations?
73, Chuck
So it is not running outnof addresses.
Bob W8ERD
Not necessarily.
DHCP address reservations are likely retained for 1 week.
A warm boot might reset the reservations.
Need to view the 'DHCP Address Reservations' section of 'cgi-bin/ports'.
73, Chuck
"only 2 corded phones (out of 4)
not the router
not the pbx"
Ensure that those devices are requesting an address via DHCP.
Maybe try with only attaching those devices
(and the Wireless Router configured as a switch)
after a reboot of the Bullet.
If you are using a computer to view your network devices, from where/what is it getting its address?
From the Bullet or the AR300M?
Chuck
For the cell phones, the bullet assigns addresses as soon as they are turned on.
For the PBX, unplugging or power cycling causes no change, It still has the address it had back when the router was issuing addresses.
The PC is getting its address from the bullet.
If I power cycle the bullet, all the above address assigments remain the same except for the PC.
The PC then gets its address from the AR300.
Bob W8ERD
"For the PBX, unplugging or power cycling causes no change, It still has the address it had back when the router was issuing addresses."
Hi, Bob:
Perhaps configure the PBX to request an address via DHCP or
the PBX is requesting an address but cannot reach the Bullet.
73, Chuck
changed the cable from router to PBX.
changed the pbx to a different port on the router
connected PBX directly to bullet
restarted bullet and PBX
no change.
I don't understand how to have the PBX request an address. Is that not the normal way?
What am I missing?
I could reset the router and that would turn on its dhcp to enable me to log into the PBX if I need to change something there.
Bob W8ERD
http://www.grandstream.com/hubfs/Product_Documentation/UCM6102_quick_installation_guide.pdf
CONFIGURING THE UCM6102 VIA WEB GUI:
1. Connect the computer to the same network as the UCM6102.
2. Ensure the UCM6102 is properly powered up and shows its IP address in the LCD.
3. Open a web browser on the computer and enter the web GUI URL in the format:
http(s)://IP-Address:Port
The default protocol is HTTPS and the default port number is 8089.
4. The web GUI login page will show (see Figure below). The default username and password for administrator are “admin”. 5. For the detailed information to configure SIP Extensions, PSTN lines, SIP trunks and all the other system settings via web GUI, please download the UCM6102 user manual here: http://www.grandstream.com/support
Hi, Bob:
Tell us about item 2.
Tell/show us the DHCP address range of the Bullet.
Chuck
I can now log into the PBX normally, and I fixed some incorrect settings.
The bullet address range is 34-62.
But the GXP phone does not get an address assignment from the bullet. It just shows 0,0,0,0 if I set its dhcp server to the bullet.
Bob W8ERD
Hi, Bob:
" It just shows 0,0,0,0 if I set its dhcp server to the bullet."
I don't think a DHCP server should 'set' by a client.
IIRC, the client sends a DHCP server request to FF:FF:FF:FF:FF:FF and accepts the first DHCP server that responds.
https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol#Operation
I have Grandstream GXP1630 and GXV32765 phones and have never 'set a DHCP server'.
Hey, wait a second,
in your diagram the Grandstream phone should be getting an IP address from the AR300M16,
not the Bullet !
https://www.arednmesh.org/sites/default/files/portable%20post%20office.pdf
73, Chuck
Yes I know the phone should go to the AR3000 for dns, but I was experimenting to see if the phone was on the same network
as the PBX, it would be registered. I still cannot get the phone registered with the PBX when it is connected to the AR300.
Bob
Hi, Bob:
0.0.0.0
http://nc8q-phone-1073/#page:network_basic
NETWORK -> Basic Settings -> Preferred DNS Server: Was, likely, left untouched.
However, my settings are DHCP.
That setting is under 'DHCP'.
'Preferred DNS Server' is under 'Static', which I do not use.
Please, no more experimenting. Unknown to me experimentation on your end makes it difficult for me to assist you.
"if the phone was on the same network as the PBX, it would be registered."
The Grandstream phone is not on the same LAN as the PBX!
The phone is on the LAN of the AR300M16.
The PBX is on the LAN of the Bullet.
As in your diagram, the Grandstream phone is in the network of the AR300M16.
If the AR300M16 is AREDN linked with the Bullet and the PBX is advertised on the LAN of the Bullet,
then the phone knows the AR300M16 as the DNS server and
the AR300M16 knows the route to the PBX is via the Bullet and
the Bullet knows the route to the PBX.
Please confirm that the Grandstream phone is getting an IP address from the AR300M16.
Please confirm that the AR300M16 is linked with the Bullet.
Please confirm that the PBX is advertised on the Bullet.
Please confirm that the PBX appears with the Bullet on the /cgi-bin/mesh page of the AR300M16.
Please confirm that the AR300M16 appears on the /cgi-bin/mesh page of the Bullet.
3s, Chuck
The ARM is linked to the bullet via wireless.
The PBX is not advertised on the bullet because I don't know how.
Please give me the Advertised Services text line to make this happen.
So the PBX does not appear with the Bullet on the mesh page of the ARM.
The ARM appears on the mesh page of the bullet.
Bob
Hi, Bob:
Sorry, stike-out the parts with advertising. Advertising is not needed.
The PBX's 'DHCP Address Reservations' are required.
Attached is a screen shot of how the PBX should appear on the AR300M16.
3s, Chuck
Bob
Hi, Bob:
Navigate to the '/setup' page of the Bullet.
Fill in the selections for 'Hostname IP Address MAC Address' from the values in 'Current DHCP Leases'.
Click 'Add'.
Wait 20 seconds.
Now the AR300M16 and the phone on its LAN can route to the PBX.
3s, Chuck
What do I need to change on these pages?
Bob
The PBX should appear under 'Current DHCP Leases'.
This issue needs fixing.
The PBX should be configured as a DHCP client and
should be obtaining a DHCP reservation on the Bullet.
Once the PBX appears in'Current DHCP Leases' it can be added to 'DHCP Address Reservations'.
Also missing:
Up to 4 analog telephone adapters should also have Current DHCP Leases.
Up to 4 cell phones should also have Current DHCP Leases.
a 'cell phone acting as an interface should also have a Current DHCP Lease.
You may need to set the Bullet's LAN to '29 host Direct'.
Including all the items in your diagram plus 'Bob-PC', I see 12 reservations needed.
What device is the Hostname '*' ?
3s, Chuck
29 hosts is set in the bullet. I turned on the corded phones. I don't like to have the cellphones on too often as that
drains their batteries.
Pages