Search results

No rush... but I am still very much interested in this. Thank you for your efforts.

@krzykat Did you ever post the howto? If so, where?

@krzykat Did you ever get this finished? I would really like to see the code.

Any Updates on this?

ok just ran: /sbin/ldconfig -v now I'm getting: pico2wave --wave sample.wav -l en-US "Here is a sample, using the PICO text to speech engine." pico2wave: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by pico2wave)

just tried installing following the NV article. when testing I get: pico2wave --wave sample.wav -l en-US "Here is a sample, using the PICO text to speech engine." pico2wave: error while loading shared libraries: libttspico.so.0: cannot open shared object file: No such file or directory locate...

I'm glad you got it sorted out.

That shouldn't matter. I have client with routers that were put in service 14 years ago. ie mostly Linksys WRT54G's and CISCO RV042's. If the problem really is the router, get rid of it. For our smaller clients (less than 30 devices) we still use WRT54GL's ($39.99) and DD-WRT Firmware and...

THANK YOU!!! I should've known this myself. Heck, I have done that exact set up in the past. :banghead::banghead::banghead:

Ugh... I have NEVER found SIP ALG to be a good solution for anything. First thing I would check is the extension's "NAT Mode" setting in the PBX's control panel. It should be set to Yes or Automatic. Try that and check back with you findings.

@geopeterwc Thanks but that doesn't apply here. Lemme add some details. The PBX is hosted in a datacenter. I was talking about the internet connection the ip phones use to connect to the PBX. That's why I was saying "unavailable/unregistered" connections. Sorry for the confusion.

Client asked for the ability to have calls forwarded to cell phones of employees if the internet at their office location goes down. In other words, when all the phones at that location are unavailable/unregistered. I know you can set a misc destination to cell number for an extension that is...

It turns out you're right there were many check boxes that I assumed were checked. Upon further inspection, sadly they were not. Thank you for pointing me in the right direction.

I'm seeing the same problem

Bill can you point me to a howto or something similar?

Has any found a solution yet? I have managed a work around by sending the sip through a vpn, but there's a lot of admin overhead not user friendly.

thanks Joe, I didn't know that.

ward as atsak said, Voip Innovations use IP auth. there is no user registration

definitely have the ip's added. I have two trunks set up. In the peer details: type=friend insecure=very host=64.136.174.30 dtmf=auto disallow=all context=from-trunk canreinvite=no caninvite=no allow=ulaw&alaw and type=friend insecure=very host=64.136.174.31 dtmf=auto disallow=all...

I have several systems setup that use Voip Innovations for trunking. However, I am having major problems getting inbound calling to work properly with Incredible PBX 13-12.0 for CentOS 6. It seems as though Incredible PBX 13-12.0 for CentOS 6 needs the trunk setup differently than past...