search for: eingehender

...context [capi-in] for icoming ISDN calls: ====== [capi-in] ; Faxe fuer Ruben exten => 12345,1,Macro(faxin,ruben.roegels at jumping-frog.org,${EXTEN}) ====== My macro for the fax receiving looks like that: ====== [macro-faxin] ; Faxe ; ARG1 = eMail-Adresse exten => s,1,Verbose(${BOUNDARY} Eingehender Ruf von ${CALLERID(num)}) exten => s,n,Verbose(${BOUNDARY} BCHANNELINFO ${BCHANNELINFO}) ; nur verarbeiten, wenn B-Kanal frei ist exten => s,n,GotoIf($[${BCHANNELINFO} = 2]?hangup:free) exten => s,n(free),NoOp() exten => s,n,Set(TO=${ARG1}) exten => s,n,Verbose(1,${BOUNDARY} Eingehen...

...asterisk server. (Version 1.4.15 RPM Build running on Fedora Core 7) After 3 day's running, i'v got this message in my logfile: Dec 14 13:14:09 amsec-tk1 asterisk[4321]: VERBOSE[11363]: -- Executing [9020 at AMS-UPPORT-HOTLINE:1] System("SIP/SN2400-67ec6aa0", "echo -e "Eingehender Support Anruf am 14.12.2007 um 13:14 durch die Nummer <06xxxxxxxx> \n" >> /drbd/ams-support-hotline.txt") in new stack Dec 14 13:14:09 amsec-tk1 asterisk[4321]: WARNING[11363]: asterisk.c:820 in ast_safe_system: Fork failed: Cannot allocate memory Reserved memory was about 1...

Hello. I have a strange problem with the MeetMe application. Configured is a misdn msn to go into a preconfigured MeetMe room. exten => 12,1,MeetMe(1234,pIM) The first caller gets the prompt to enter the pin and then gets connected to the MeetMe room. The second caller gets also the prompt but after entering the right key he hears a dialtone followed by the message: The number you have

Dear Mailinglist-User currently we`re working with an IP-PBX, based on Asterisk, with SIP, H.323 and ISDN-Capabilities. SIP and ISDN works fine, but H.323 not. In our first test, we started to connect Asterisk to an Cisco IOS-Gatekeeper with the "chan_oh323" (version 0.6.5). We successfully tested in/egress calls without any problems. But when we started to connect our Asterisk

I have been running Samba 2.2.8 on a Solaris 8 server with a valid NetBIOS server name on the AD domain. The Samba 2.2.8 configuration was configured for security = domain. Everything was fine until the AD domain controllers were "upgraded" to Windows Server 2003 SP1. User authentication would no longer function with the following error message in the samba 2.2.8 log:

I thought about saying this in v1.2.beta1 release annoouncement, but looks like it'll take a few more days. So I've moved to Blacksburg, Virginia and I'm now working for Mailtrust the rest of this year. Here's some talk about it: http://mailtrust.com/blog (A bit stupid looking picture, but then again all my pictures seem to be that way so I didn't bother getting a new one

I thought about saying this in v1.2.beta1 release annoouncement, but looks like it'll take a few more days. So I've moved to Blacksburg, Virginia and I'm now working for Mailtrust the rest of this year. Here's some talk about it: http://mailtrust.com/blog (A bit stupid looking picture, but then again all my pictures seem to be that way so I didn't bother getting a new one

Hallo zusammen, ?ber den Policy Service von Dovecot zum Abfragen der User Quotas wurde ja schon diskutiert - auch gibt es eine gute Anleitung zum Einrichten, nur leider bekomme ich den Policy Server nicht korrekt konfiguriert. Folgende Fehler werden protokolliert: May 3 22:00:13 mail postfix/smtpd[17463]: warning: access table unix:private/quota-status entry has empty value May 3 22:00:42