search for: keewi

Displaying 4 results from an estimated 4 matches for "keewi".

Did you mean: keep
[Fwd: Re: DAHDI or Zaptel doesn't compile against 1.4.24]
2009 Mar 18
0
[Fwd: Re: DAHDI or Zaptel doesn't compile against 1.4.24]
...ir Cohen a ?crit : > On Tue, Mar 17, 2009 at 07:16:26PM +0100, Administrator TOOTAI wrote: > >> Hi, >> >> We installed the latest 1.4.24 on a test machine and can't get zaptel >> nor dahdi compile. It's a Linux Debian Etch. Errors we have: >> >> keewi:/usr/src/dahdi-linux-2.1.0.4# make >> make -C /lib/modules/2.6.18-custom.2/build ARCH=i386 >> SUBDIRS=/usr/src/dahdi-linux-2.1.0.4/drivers/dahdi >> DAHDI_INCLUDE=/usr/src/dahdi-linux-2.1.0.4/include DAHDI_MODULES_EXTRA=" >> " HOTPLUG_FIRMWARE=yes modules DAHDI_B...
SIP Registration failure
2005 Aug 27
1
SIP Registration failure
...ce is: "Failed to authenticate on REGISTER to 'phonenumber@sip.broadvoice.com' (Tries 2)" then "Registration for 'phonenumber@sip.broadvoice.com' timed out" and finaly "Giving up forever to register 'phonenumber@sip.broadvoice.com'" If I do keewi*CLI> sip show peers Name/username Host Dyn Nat ACL Mask Port Status broadvoice/<phonenumber> 147.135.20.128 255.255.255.255 5060 OK (213 ms) keewi*CLI> sip show registry Host Username Refresh State sip.broadvoice.com:5060 <phonenumber> 120 Failed In log files with sip debug I fo...
DAHDI or Zaptel doesn't compile against 1.4.24
2009 Mar 17
2
DAHDI or Zaptel doesn't compile against 1.4.24
Hi, We installed the latest 1.4.24 on a test machine and can't get zaptel nor dahdi compile. It's a Linux Debian Etch. Errors we have: keewi:/usr/src/dahdi-linux-2.1.0.4# make make -C /lib/modules/2.6.18-custom.2/build ARCH=i386 SUBDIRS=/usr/src/dahdi-linux-2.1.0.4/drivers/dahdi DAHDI_INCLUDE=/usr/src/dahdi-linux-2.1.0.4/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: entrant dans le...
Sip - no peer or user found on incoming call
2006 Feb 02
0
Sip - no peer or user found on incoming call
...only_ when the IP which with my * is registred to the GW match this from the incoming call, and then doesn't matter if type=user or type=peer, which is normal according to http://www.voip-info.org/wiki/view/Asterisk+SIP+user+vs+peer. I'm running Asterisk SVN-trunk-r8643M built by root @ keewi on a i686 running Linux on 2006-01-25 14:50:51 UTC Here is relevant part of my sip.conf register => <MyUserName>:<MySecret>@sip.mydomain.com/<MyUserName> [IN-UserName] type=user username=<MyUserName> fromuser=<MyUserName> fromdomain=<MyFromDomainName> secr...