Hi All,
Not sure where to post this or who to notify of this bug. Here goes.
I have purple installed.
PBX in a Flash Version = 1.7.5.6 Running on *HARDWARE* FreePBX Version = 2.8.1.4
Running Asterisk Version = 1.8.5.0
Asterisk Source Version = 1.8.5.0
Dahdi Source Version = 2.4.1.2+2.4.1
Libpri Source Version = 1.4.12
Operating System = CentOS release 5.6 (Final)
Kernel Version = 2.6.18-238.9.1.el5 - 32 Bit
Sangoma B600D with 3.5.20 software
The problem: I need to create an outbound route for my fax machine. It's on an extension (FXS port) and I need to route it out my PSTN.
So, I created an outbound route, put it at the top of the list and configured the callerID matching the extension. I have 2 routes that use the same dial pattern. It keeps taking the second route and bypassing this route. Strange
When I check the asterisk -rvvvv it shows that there is no callerID for the extension and picks the wrong route. I am thinking there is a bug. But is it in freePBX or asterisk?
Last question, is it OK to upgrade to 2.9 freePBX yet? everyone happy with stability and functionality?
Thanks for the help!
Not sure where to post this or who to notify of this bug. Here goes.
I have purple installed.
PBX in a Flash Version = 1.7.5.6 Running on *HARDWARE* FreePBX Version = 2.8.1.4
Running Asterisk Version = 1.8.5.0
Asterisk Source Version = 1.8.5.0
Dahdi Source Version = 2.4.1.2+2.4.1
Libpri Source Version = 1.4.12
Operating System = CentOS release 5.6 (Final)
Kernel Version = 2.6.18-238.9.1.el5 - 32 Bit
Sangoma B600D with 3.5.20 software
The problem: I need to create an outbound route for my fax machine. It's on an extension (FXS port) and I need to route it out my PSTN.
So, I created an outbound route, put it at the top of the list and configured the callerID matching the extension. I have 2 routes that use the same dial pattern. It keeps taking the second route and bypassing this route. Strange
When I check the asterisk -rvvvv it shows that there is no callerID for the extension and picks the wrong route. I am thinking there is a bug. But is it in freePBX or asterisk?
Last question, is it OK to upgrade to 2.9 freePBX yet? everyone happy with stability and functionality?
Thanks for the help!