similar to: Macedonian DID

Displaying 20 results from an estimated 1200 matches similar to: "Macedonian DID"

2006 Feb 16
1
Rejoining Computers to the domain
Hi list I have a query, I have a samba 3.0.21 with openldap, all my windows clients are joined to PDC. but suddenly now , all my windows clients uanble to login but when i do getent passwd on the server , i could see all my computer accounts . even when i do ldapsearch -x -b "ou=Computers,dc=msdpl,dc=com" , i could see the list of computer account names but my windows clients report
2013 Jan 24
3
DECT Solution
Hello, I need to setup system of aroud 60 DECT phones with asterisk. So far I found http://www.grandstream.com/index.php/products/ip-voice-telephony/enterprise-ip-phones/dp715_710 However is there some cheap base station(similar to GSM cell) so I can handle all DECT phones centralized and plug it inside asterisk ? Thanks, Peter
2014 Dec 18
0
[PATCH 00/10] Split UFO into v4 and v6 versions.
----- Original Message ----- > UFO support in the kernel applies to both IPv4 and IPv6 protocols > with the same device feature. However some devices may not be able > to support one of the offloads. For this we split the UFO offload > feature into 2 pieces. NETIF_F_UFO now controlls the IPv4 part and > this series introduces NETIF_F_UFO6. > > As a result of this work, we
2014 Dec 18
0
[PATCH 00/10] Split UFO into v4 and v6 versions.
----- Original Message ----- > UFO support in the kernel applies to both IPv4 and IPv6 protocols > with the same device feature. However some devices may not be able > to support one of the offloads. For this we split the UFO offload > feature into 2 pieces. NETIF_F_UFO now controlls the IPv4 part and > this series introduces NETIF_F_UFO6. > > As a result of this work, we
1998 May 07
1
Compiling Samba!!
Hi, I am trying to compile Samba version 1.9.18p2 on a HP 800/D350 using HPUX 10.20 with software patches from HP installed up to Dec 97. I have seen other messages on this digest that people have been successful but I cannot. using the standard compiler which has ANSI features unbundled I get the following; extract of last half of 30+ error lines... (Bundled) cc: "nameserv.h", line
2013 Apr 01
0
Getting DIALSTATUS via agi
Hi all, Hopefully, I just need a second set of eyes on this one, but I just can't figure out what I'm doing wrong. I'm using an agi script to dial a number, check the dial result, and act accordingly. The problem is that I'm not getting anything back from DIALSTATUS, or HANGUPCAUSE. Here is the relevant perl code: ===============================================================
2010 Feb 08
6
GSM Gateway
Hello, I am looking for a gsm gateway that is SIP based i.e no need of FXO/FXS analogue connection. I searched the email archives and found messages from 2008 but not sure how accurate these are. What do you use and how well it works ? The only sensible one I found is one made by portech and one that is made by Eurodesign. The one from portech is like a trunk while the one from eurodesign
2014 Dec 17
0
[PATCH 08/10] tun: Re-uanble UFO support.
Now that UFO is split into v4 and v6 parts, we can bring back v4 support without any trouble. Continue to handle legacy applications by selecting the IPv6 fragment id but do not change the gso type. Thist makes sure that two legacy VMs may still communicate. Based on original work from Ben Hutchings. Fixes: 88e0e0e5aa7a ("drivers/net: Disable UFO through virtio") CC: Ben Hutchings
2014 Dec 17
0
[PATCH 08/10] tun: Re-uanble UFO support.
Now that UFO is split into v4 and v6 parts, we can bring back v4 support without any trouble. Continue to handle legacy applications by selecting the IPv6 fragment id but do not change the gso type. Thist makes sure that two legacy VMs may still communicate. Based on original work from Ben Hutchings. Fixes: 88e0e0e5aa7a ("drivers/net: Disable UFO through virtio") CC: Ben Hutchings
2014 Dec 18
0
[PATCH 08/10] tun: Re-uanble UFO support.
On 12/18/2014 12:51 AM, Jason Wang wrote: > > > ----- Original Message ----- >> Now that UFO is split into v4 and v6 parts, we can bring >> back v4 support without any trouble. >> >> Continue to handle legacy applications by selecting the >> IPv6 fragment id but do not change the gso type. Thist >> makes sure that two legacy VMs may still
2014 Dec 18
0
[PATCH 08/10] tun: Re-uanble UFO support.
On 12/18/2014 12:51 AM, Jason Wang wrote: > > > ----- Original Message ----- >> Now that UFO is split into v4 and v6 parts, we can bring >> back v4 support without any trouble. >> >> Continue to handle legacy applications by selecting the >> IPv6 fragment id but do not change the gso type. Thist >> makes sure that two legacy VMs may still
2011 Nov 03
15
DID from Direct from Telco
Hello Everyone, Unlike going through DIDx, DIDLogic etc.., we have an option of getting DIDs directly from local telco Bell Canada. Currently our SIP Trunk provider assigned a DID to us, and as you know, they just redirect requests it to our PBX. However, when dealing directly with a telco, what equipment will we need? Basically giving us the same capability as a DID provider. If someone can
2014 Dec 18
2
[PATCH 08/10] tun: Re-uanble UFO support.
----- Original Message ----- > Now that UFO is split into v4 and v6 parts, we can bring > back v4 support without any trouble. > > Continue to handle legacy applications by selecting the > IPv6 fragment id but do not change the gso type. Thist > makes sure that two legacy VMs may still communicate. > > Based on original work from Ben Hutchings. > > Fixes:
2014 Dec 18
2
[PATCH 08/10] tun: Re-uanble UFO support.
----- Original Message ----- > Now that UFO is split into v4 and v6 parts, we can bring > back v4 support without any trouble. > > Continue to handle legacy applications by selecting the > IPv6 fragment id but do not change the gso type. Thist > makes sure that two legacy VMs may still communicate. > > Based on original work from Ben Hutchings. > > Fixes:
2014 Dec 17
20
[PATCH 00/10] Split UFO into v4 and v6 versions.
UFO support in the kernel applies to both IPv4 and IPv6 protocols with the same device feature. However some devices may not be able to support one of the offloads. For this we split the UFO offload feature into 2 pieces. NETIF_F_UFO now controlls the IPv4 part and this series introduces NETIF_F_UFO6. As a result of this work, we can now re-enable NETIF_F_UFO on virtio_net devices and restore
2014 Dec 17
20
[PATCH 00/10] Split UFO into v4 and v6 versions.
UFO support in the kernel applies to both IPv4 and IPv6 protocols with the same device feature. However some devices may not be able to support one of the offloads. For this we split the UFO offload feature into 2 pieces. NETIF_F_UFO now controlls the IPv4 part and this series introduces NETIF_F_UFO6. As a result of this work, we can now re-enable NETIF_F_UFO on virtio_net devices and restore
2004 Nov 09
2
Firewall rules that discriminate by connection duration
I'm interested in crafting firewall rules that throttle connections that have lasted more than a certain amount of time. (Most such connections are P2P traffic, which should be given a lower priority than other connections and may constitute network abuse.) Alas, it doesn't appear that FreeBSD's IPFW can keep tabs on how long a connection has been established. Is there another firewall
2010 May 12
1
your session only lasted less than 10 seconds error
hai i have run the halt command from the xshell and the machine got restarted, now when i restart the machine, i am getting this error . I have tried to press the CTRL+ALT+F2 and tried to login with the root user but that one is also not working. can any one help me with this.. this the error message i am getting after i tried to login " your session only lasted less than 10 seconds ...try
2010 Apr 30
1
GXW4024
Hello, I consider buying three GrandStream GXW4024 and connect 72 analogue phones to asterisk Do you have any feedback how well it works with Asterisk ? I am on a budget, do you have other recommendation for similar setup that get into same budget - connect around 70 analogue phones to asterisk. Thanks in advance. Peter
2013 Sep 04
1
dahdi configuration issue
Hello List, I have configure 2 sangoma card each with 8 PRI lines with dahdi 2.6 the problem is i can see all channels configured in dahdi_cfg 480 channels configured but when I see /dev/dahdi i can only see 240 channels. what could be problem I am using it wanrouter and when I put PRI in new card i only got calls on new line that means one of the card is inactive at same time all the lines and