search for: 00x

..., or the error message all circuits are busy Numbers being passed to the trunk for the call ? National is 020xxxxxxxx will result in 20xxxxxxxx being sent and dialled, which works ? Mobile is 07xxxxxxxxx will result in 7xxxxxxxxx being sent and dialled, which works ? International 00x[any number of digits] will result in 00x[any number of digits] which does not work I do not see why this does not work. I do know that for every call, the flag sent is national - how can I make sure the correct flag is sent for the call? By flag, I mean the TON, (type of number) Any assistance...

...us/usb/xxx And for libusb, Quote: * Fri Jan 27 2006 Jindrich Novy <jnovy at redhat.com> 0.1.11-2 - change device search order, /dev/bus/usb is tried first, then /proc/bus/usb, and never try /sys/bus/usb (#178994) Unquote This was released in libusb 0.1.12 so now the device is /dev/bus/usb/00x/00x The /proc/bus/usb/xxx/xxx is setup to belong to root:usb now. Regards Kjell P.S. Peter Selinger made me change mail client. Didn't notice that it was not cc'd to the list.

Hi, I'm trying to get a Powerware 3105 UPS working on SuSE 10.0. I have compiled nut from the current Subversion repository. This UPS uses the bcmxcp_usb driver. I cannot get the driver to find the ups on the USB bus. The error message I get is:- -------------- bcmxcp_usb -u nut -DDDDD -a pw3105 -------------------- Network UPS Tools - BCMXCP UPS driver 0.10 (2.1.0) debug level is

...,2,3,9-12 msn=xxxxxxxxx incomingmsn=* device => /dev/ttyI0 device => /dev/ttyI1 device => /dev/ttyI2 device => /dev/ttyI3 The lines in extensions.conf that handle outgoing calls exten => _0XXXXXXXXX,1,Dial(${TRUNK}:${EXTEN},50,Ttr) exten => _0XXXXXXXXX,2,congestion exten => _00X.,1,Dial(${TRUNK}:${EXTEN},50,Ttr) exten => _00X.,2,congestion exten => _4XXXXX,1,Dial(${TRUNK}:0342${EXTEN},50,Ttr) exten => 112,1,Dial(${TRUNK}:112,50,Ttr) exten => _0[89]00X.,1,Dial(${TRUNK}:${EXTEN},50,Ttr) exten => _0[89]00X,2,congestion Greetz, Michiel

I tried switching to the USB version of bcmxcp_usb and get this error when I try starting up upsdrvctl or bcmxcp_usb like so: /etc/nut/bcmxcp_usb -DDDD -a powerware -u nut I used this for ups.conf: [powerware] driver = bcmxcp_usb port = auto With the serial/usb dongle, I used this successfully: [powerware] driver = bcmxcp port = /dev/ttyUSB0 What devices does

Hi, I'm trying to get a Powerware 5115 to communicate with the NUT via USB under Debian Linux and need help. Here is the output that I see. co-nh5:/tmp/mnt/projects/pwusb/nut-2.4.1# /usr/local/ups/bin/upsdrvctl -u root start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Communications with UPS lost:

Hello, I'm having trouble installing Samba on a SCO Open Server 5 system. I have gone over the Skunkware CD and the Caldera Website. I can find TAR'd versions of SAMBA but for some reason it won't let me start smbd or nmbd without giving me a core dump. Does anyone know either 1. why I'm getting the core dumps or 2. If there is a package install for OSv5. The reason I ask

I am trying to get a SPA-3000 to work behind NAT - for the sake of the exercice. The SPA is on the local network at the address 192.168.0.125 behind a NATted linux router. The machine I am trying to work with is a friend's (let's call it lolo.dyndns.org) and I've installed Asterisk 1.0.3 on it. I can see the SPA register but when I try to make an outbound call I get the message:

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1

...osition=20 =3D> ''inline'', :stream =3D> false I get this. The raw pdf code sent replacing the main div with : =00%=00P=00D=00F=00-=001=00.=004=00 =00%=FF=FD=FF=FD=FF=FD=FF=FD=00 = =002=002=002=001=00 =000=00 =00o=00b=00j=00 =00<=00>=00 =00e=00n=00d=00o=00= b=00j=00=20 =00x=00r=00e=00f=00 =002=002=002=001=00 =003=005=00 = =000=000=000=000=000=000=000=000=001=006=00 =000=000=000=000=000=00 =00n=00= =20 =000=000=000=000=000=000=002=001=005=003=00 =000=000=000=000=000=00 =00n=00= =000=000=000=000=000=000=000=009=009=006=00 =000=000=000=000=000=00=20 =00n=00 =000=000=000...

...need msvcr90.dll._crt_debugger_hook 29426 UDF support: VOLUME_GetSuperblockSerial invalid for some volume types 29918 LibreOffice fonts antialiasing is wrong 29969 msvcr90/msvcr90 test sometimes hangs 30030 LuxMark 2.0 crashes on startup (msvcrt C++ exception handling) 30200 Writing 00x integers instead of 0x 30351 Firefox + Selenium hangs on startup 30444 Microsoft SQL Server Management Studio Express (SSMSE): opening new query window fails due to atl80 insufficiency 30512 Tencent Messenger 2008/2009 crashes with initialization failure due to atl80.dll AtlCreateRegistrar...

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking