When I used the auto settings for sipgate in B4 I could not receive calls. Here are the steps I took to resolve the issue:
1. Switch to manual mode and enter FreePBX admin site
2. Change DID in incoming route from phone number to sipgate usename (7 digit number)
3. Change destination from "custom-linuxmce,102,1" to extensions, then select an extension
I also had to manually add an extension for my Budgetone 100 as it was only added to the DHCP conf, and not to asterisk.
Is anyone else having problems? Is it just sipgate? And what is wrong with the custom dial script?
Regards,
Chris
I have noticed the same thing, found this in one of the asterisk logs:
[Mar 6 23:11:25] WARNING[19471] pbx.c: Channel 'SIP/0878700000-081dffa8' sent into invalid extension '102' in context 'custom-linuxmce', but no invalid handler
Hi
Linuxmce unfortunatly does not seem to detect ip phones and set them up at present.
If you add a new phone in the phones section of the webadmin instead of the FreePbx admin you then only have to edit inbound DID setting as above, You dont then have to point the incoming did to the extension the standard linuxmce call handler wilol work and will flash on the orbiters the incoming call and allow it to be answered on any phone.
regards
I haven't added any phones using freepbx, and still I only get that error in the logs on incoming calls. This used to just work in Beta3. I'm also not using sipgate so I don't have to change the incoming DID, as the phone number is the username in my case.
Quote from: chrisbirkinshaw on March 06, 2008, 12:26:31 PM
When I used the auto settings for sipgate in B4 I could not receive calls. Here are the steps I took to resolve the issue:
1. Switch to manual mode and enter FreePBX admin site
2. Change DID in incoming route from phone number to sipgate usename (7 digit number)
3. Change destination from "custom-linuxmce,102,1" to extensions, then select an extension
I also had to manually add an extension for my Budgetone 100 as it was only added to the DHCP conf, and not to asterisk.
Is anyone else having problems? Is it just sipgate? And what is wrong with the custom dial script?
Regards,
Chris
Yes we noticed this problem on Friday... but did not have a chance to debug it properly. Will do some more digging tomorrow. have you mantis'd this yet?
Andrew
Have added as two separate bugs.
Chris