1/ So for Auth-mode the username/pass is stored on the MP? That means we need to ensure no one can access the MP e.g. via ssh or via physical access. Guess the latter is similar to a cell phone but without a SIM it’s easier for another SIP device on the network to mimic the MP.

2/ Several people have asked about the choice of Asterisk on the MP – an entry in the Village Telco FAQ summarises the reasons.

Curiously, no one has given a really good answer to the question “why not Asterisk?” yet

3/ By default the MPs are pre-confiured to be able to dial the IP of other MPs on the same mesh. Basically you power them up, get dial tone, and dial an IP. No configuration is required.

It would be good to ensure authentication is only required for off-mesh calls via a gateway. That way the MP will keep it’s ease-of-use/zero-conf feel.

Cheers,

David

Authenticated calls will match a A2Billing account/credit
Unauthenticated calls will enter another Asterisk context in A2billing prompting for the account number (pay phone mode)

So in a nutshell we need a way to commute a potato from one mode to another.

One way is to create an IVR to set a PIN number in the mesh potato, if the number is pre-pended by the PIN the call is authenticated. Something to talk in March in Europe or to ask in the list!

I wonder if running Asterisk in the MP is really the way to go, or is better to run something lighter… a basic SIP client.

Re system integration what code do you need to place on the Mesh Potatoes to make them work with your billing system?

Thanks,

David