Installation guide

4. Troubleshooting

4.1 What to do if you can’t connect to the MP

anymore - using the Fallback-IP

This can easily happen if you are messing around with the IP settings of the MP.

Luckily the MP has a additional IP subnet at the Ethernet port that can not be

changed or disabled from a web interface.

On your PC configure the Ethernet port to use 172.31.255.253/30 (netmask

255.255.255.252). You can add multiple IP addresses to each interface, so you

don't have to reconfigure it if you need other addresses as well.

After finishing the configuration you should be able to access the MP01 using IP

172.31.255.254.

4.2 My MP01 can’t make calls

You have set up you MP01 IPs but can't make calls. Here are some basic tests:

1. Can you hear dial tone in a phone connected to the MP? If not please reboot

it and try again. Some of the modules have come loose while shipping.

2. Check you mesh network. Telnet/ssh into your MP and:

batmand -cbd1

You should see the IP of the other MP(s) on your mesh. If you see no IPs then

check your WiFi settings are identical except for the IP. These can be checked in

/etc/config/wireless or via the GUI. Also compare "iwconfig ath0" on both MPs

and "ifconfig ath0".

3. Try pinging one MP from the other.

4. On each MP, dial 4001. This performs an echo test. Can you hear your own

voice coming back to you?

5. Start an Asterisk CLI and see what happens when you dial an IP:

root@OpenWrt:~# asterisk -r

OpenWrt*CLI> set verbose 3

Note: The 'set verbose' command is deprecated, please use 'core set verbose'

instead.

Now dial the IP of another MP. You should see something like:

-- event_offhook

-- AST_STATE_DOWN:

-- start mp_new

-- event_dtmf 1

-- event_dtmf 4

-- event_dtmf 2

-- event_digit_timer

-- extension exists, starting PBX 142

-- Executing [142@default:1] Dial("MP/1", "SIP/4000@10.130.1.142")

in new stack