Asterisk, FreePBX, and Draytel/Draytek accounts

Lord this has been fun to set up.

Had it working before with Asterisk/SARK/SAIL but trying it with FreePBX on my trusty SME Server

First remember that calls go like this :

PSTN > Trunk > Inbound Route > Extension > Outbound Route > Trunk > PSTN

1. Devices

Secret : a password
Device ID : a number e.g start from 9001
Device type : adhoc
This is better as users have to log in and out using *11 and *12 giving you a 2 layer security

2. Users

User Extension : a number e.g. start from 5001
User password : a multi digit PIN
Display Name : username

3. Ring Groups (if required)

Ring-Group Number : pick a number e.g. 600
Description : Draytel Ring all
Extension list : add your extensions


4. Trunk

I have had various settings. This works but I get 'Unmonitored' in Asterisk info and I'm sure it wasn't when I first did it - I thought it said 'OK'. Such is life.

Name : Draytel
Outbound CID : <Your PSTN number>
CID Options : Allow Any CID
Max Channels - Set currently at 2 but I think it can be 5

Outgoing Settings :

Name : Draytel
Peer Details :
type=friend
username=your customer/account number
fromuser=your customer/account number
secret=your customer/account password
host=draytel.org
fromdomain=draytel.org
qualify=yes
context=from-pstn
dtmfmode=rfc2833
insecure=very
disallow=all
allow=ulaw
Incoming Settings : are empty


Registration string :

In the following form

accountnumber:password@draytel.org/your incoming number

e.g. :

6548975:pass@draytel.org/02091234567

5. Outbound Route

Name : Draytel Outbound

Some Dial patterns

Trunk Sequence for Matched : Draytel

6. Inbound Route

Desctiption : Draytel Inbound
DID number : your PSTN Drayel Number
Destination : Pick an extension or a Ring Group




That should be it.

For issues with no sound look carefully at your NAT settings (after you have checked your Mic is working !) I think that 99% of all sound problems are due to incorrect NAT settings, so check, check, and check again.

SIP Phones settings :

Qutecom :

Username : The device name from above e.g. 9001
Password : from the Device password

SIP Domain/Realm : IP or Domain name of server
Displayname : Your name :-)

If necessary

Server : IP or Domain name of server
Proxy: IP or Domain name of server

 Enjoy :-)

Eclipse debugging problems

Lord I could write volumes on Eclipse, and regrettably much of it would involving hurling computers out of upper storey windows and smashing my brain against a large immovable object.

It's a love hate kinda thing. I love it, when it works. But boy do I hate it when it doesn't. It throws more temper tantrums than my entire family put together. The ide(a) is great. The execution is akin to that of Mary Queen of Scots. Slightly messy, and may take several blows to entirely sever the head. Yuck. But I digress.

I have a CentOS based server (my beloved little contribs.org) with Zend Debugger on it. Took a while to get it right. And don't forget to change Zend versions with PHP. Oh, and the odd problem with missing libraries (see earlier posts)

Anyway, after I upgraded to Juno I seem to be plagued with problems. The mess first stemmed from not sorting out my projects properly when I upgraded. Should have committed the lot to SVN and started again. But I was between things, didn't want to commit a whole pile of stuff that probably wouldn't happen (I know, I know....branches & all that jazz) so I cheated. Damn, damn, damn.

The worst problem has been getting the debugger running properly so here are some things to watch for.

• 1. Check your php.ini - don't guess or assume. Use php -v & php -m
• 2. Use phpinfo - don't guess or assume. Zend Debugger info appear ????
• 3. See here for 'incompatible version' - try changing to a different port - see this bug which should have been fixed yonks ago. Grrrrrrrr.
• 4. Got something going on like DLTK processing ??? That can stop the whole thing. Try closing off ALL projects except the one you want (did it for me in this instance)

If all else fails, lob it out of the window and get a beer :-)