We have TrixBox connected to an Iwatsu ECS PBX. It is set up to require “92” to select an available CO line from a group of 4 lines. We can observe the CO line pick up (or not pick up) on the Iwatsu digital desk phone.
We started off with nothing in the Outbound Dial Prefix and the following in the ZAP Trunk Dial Rules
3xx
92+911
92+NXXNXXXXXX
92+NXXXXXX
This almost works. We can dial internal 3XX Iwatsu extensions. However, when we dial the local number, we can see the CO line being picked up, but the call won’t go through. We therefore figured we needed a pause after the “92” and before the number.
FreePBX won’t allow you to enter a “non-dialable character”, such as “w”, in the Dial Rules, so we tried putting “92ww” in the Outbound Dial Prefix and stripping out the “92” from the internal Iwatsu extensions with the “|” character. So we believe we are now dialling the following
92|3xx → 319 (the | strips out the 92)
911 → 92ww911
NXXNXXXXXX → 92wwNXXNXXXXXX
NXXXXXX → 92wwNXXXXXX
For some reason, with these rules, 319 picks up a CO line, but the local numbers do not.
Based on our experience, if we were to leave the Outbound Dial Prefix blank and include the “92” and the “ww” in the Dial Rules, we would be good to go. However, FreePBX won’t allow the “ww” in the Dial Rules.
What do your logs say as to what is actually being dialed – is this a
real zap driver i.e. Digium card? If not, I am not sure about the w
character – but in any case do this with enough verbosity to see what
is happening.
We have TrixBox connected to an Iwatsu ECS PBX. It is set up to require “92” to select an available CO line from a group of 4 lines. We can observe the CO line pick up (or not pick up) on the Iwatsu digital desk phone.
We started off with nothing in the Outbound Dial Prefix and the following in the ZAP Trunk Dial Rules
3xx
92+911
92+NXXNXXXXXX
92+NXXXXXX
This almost works. We can dial internal 3XX Iwatsu extensions. However, when we dial the local number, we can see the CO line being picked up, but the call won’t go through. We therefore figured we needed a pause after the “92” and before the number.
FreePBX won’t allow you to enter a “non-dialable character”, such as “w”, in the Dial Rules, so we tried putting “92ww” in the Outbound Dial Prefix and stripping out the “92” from the internal Iwatsu extensions with the “|” character. So we believe we are now dialling the following
92|3xx → 319 (the | strips out the 92)
911 → 92ww911
NXXNXXXXXX → 92wwNXXNXXXXXX
NXXXXXX → 92wwNXXXXXX
For some reason, with these rules, 319 picks up a CO line, but the local numbers do not.
Based on our experience, if we were to leave the Outbound Dial Prefix blank and include the “92” and the “ww” in the Dial Rules, we would be good to go. However, FreePBX won’t allow the “ww” in the Dial Rules.
Any ideas from FreePBX users?
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
We’re having the same issue, I’ve just dedicated a trunk with 8ww as the dialing prefix but this is a less than elegant solution, I need to dail 8ww through the dial plan so a trunk or two is not tied up just for long distance. Any help would be appreciated.
[quote=“rmclaren”]This post is languishing at Trixbox:
We looked at the log and found that “92|” would not strip out the “92ww”, so that Asterisk was actually dialling “92ww319” even with the “92|” instruction in place. I am afraid we gave up on this for now and dedicated one ZAP channel for internal calls and another ZAP channel for outgoing calls. We may revisit this later, perhaps manually editing the .conf file. However, we want to move ahead with the prototype installation and begin testing.