similar to: Connecting a TE to a NT BRI isdn

Hi everybody, I have corrected this line in extensions.conf by stripping spaces off and now it executes: exten => 22999,1,VoiceMailMain(s${CALLERIDNUM}) when it runs, the mail box number is asked and password too. I expected no question were made, because I inserted CALLERIDNUMBER and s in front of box number. Anybody knows why? Thank to you all, very kind members of this list! Ciao Mauro

Hi everybody, I'm in a middle of a Asterisk learning period. I am at a very good point except I'm not able to use VoiceMailMain. This Is my simple dialplan regarding VoiceMail ;Number that the IP Phones dial to access voice mail exten => 22999,1,VoiceMailMain (s${CALLERIDNUM}) exten => 22999,2,Wait(3) exten => 22999,3,Hangup Why do I get Forbidden 403 and one console display

Hi dear group members, I have finally an Asterisk box working, capable of receiving and making calls. I have this issue while calling mobiles from our SIP softphones: -------------------------- linux*CLI> -- Executing NoOp("SIP/2000-6850", "3487024125") in new stack -- Executing Dial("SIP/2000-6850", "ZAP/g1/3487024125") in new stack -- Called

Hi everybody I'm trying to make Asterisk 1.2.1 run under VMWARE and Suse 9.2. I use ZTDUMMY module for timing and ZTTEST gets an average precision of 98,4 %. Is there any way to improve it? Best regards Mauro Zanin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060117/945d544a/attachment.htm

Hi everybody, I have this issue: I need to automatically park an incoming call, play a welcome prompt and then connect to some extension but under extension user's command. I was thinking to use a small database to comunicate between asterisk and the main application. Has anybody had this kind of experience? Best regards Mauro

Hi Everybody, I'm experiencing this kind of issue. One ASTERISK 1.2.17 is connected to a Bristuffed HFC single ISDN channel card. Everything seems to work but sometimes the third party caller when listening to MOH listens some "SSHHHHH!" instead of MOH, this is not continuos, MOH plays ok for, say, 20 seconds then the sound and then another 30 seconds of good MOH. We have some

Hi everybody I have installed a TrixBox with Asterisk 1.2.14 and relative upgreaded software. I Bristuffed it with last version of bristuff to use a Hemlet PCI ISDN CARD in a normal Italian EUROISDN installation. The * works fine except for the ISDN CARD. It is always Channel D down, but if a Call comes in, it works perfectly for some time, both inbound and outbound. It prompts Channel D UP!

Try different entry in this parameter. In Italy mobiles start with 3, while public services with 1 and normal user numbers with 0. Using pridialplan=none, every number different from 0 was resulting in termination code 1, normally used for number never seen on the network. Ciao Mauro

Hi Everybody, as far as I see, I installed 1.2.12.1 on a 1.2.0 box. Everything ran OK, but VoiceMail application stated that there were no entries in voicemail.conf, so it didn't work. Installed again 1.2.0 and voil? the VoiceMail app. was working again. I asked to the group, but it seems I'm the only one with this issue! In Italy we say: "Chi lascia la via vecchia per la nuova, sa

Hi everybody, I'm testing Asterisk 1.2.14(you can say: why such an old version? I say: I'm using Trixbox..). I must be as fast as a flash to press *2 and do an attended transfer. If I wait only a tenth of a second nothing happens. I think it is an issue. I have seen the source code and found nothing bad. Is this a known issue? Many thanks Best regards Mauro

Hi Ravi, thank you very much for your support and explanation. If I understand, the ctime xlator feature is not present in the current gluster package but it will be in the future release, right? Thank you again, Mauro > Il giorno 02 gen 2018, alle ore 12:53, Ravishankar N <ravishankar at redhat.com> ha scritto: > > I think it is safe to ignore it. The problem exists due to the

I think it is safe to ignore it. The problem exists? due to the minor difference in file time stamps in the backend bricks of the same sub volume (for a given file) and during the course of tar, the timestamp can be served from different bricks causing it to complain . The ctime xlator[1] feature once ready should fix this issue by storing time stamps as xattrs on the bricks. i.e. all bricks

Hi All, any news about this issue? Can I ignore this kind of error message or I have to do something to correct it? Thank you in advance and sorry for my insistence. Regards, Mauro > Il giorno 29 dic 2017, alle ore 11:45, Mauro Tridici <mauro.tridici at cmcc.it> ha scritto: > > > Hi Nithya, > > thank you very much for your support and sorry for the late. > Below

I have configured /etc/asterisk/zapata.conf, but now Asterisk refuses to start: Aug 5 10:47:29 ERROR[1076842624]: chan_zap.c:5976 mkintf: Unable to get parameters Aug 5 10:47:29 ERROR[1076842624]: chan_zap.c:9478 setup_zap: Unable to register channel '1-15' Aug 5 10:47:29 WARNING[1076842624]: loader.c:328 ast_load_resource: chan_zap.so: load_module failed, returning -1 == Unregistered

Hi Nithya, thank you very much for your support and sorry for the late. Below you can find the output of ?gluster volume info tier2? command and the gluster software stack version: gluster volume info Volume Name: tier2 Type: Distributed-Disperse Volume ID: a28d88c5-3295-4e35-98d4-210b3af9358c Status: Started Snapshot Count: 0 Number of Bricks: 6 x (4 + 2) = 36 Transport-type: tcp Bricks:

Hi Mauro, What version of Gluster are you running and what is your volume configuration? IIRC, this was seen because of mismatches in the ctime returned to the client. I don't think there were issues with the files but I will leave it to Ravi and Raghavendra to comment. Regards, Nithya On 29 December 2017 at 04:10, Mauro Tridici <mauro.tridici at cmcc.it> wrote: > > Hi All,

Hi Mauro Tridici, >From the information provided it appears like you have placed 2 bricks of a subvolume on one host. Please confirm. The number of hosts that could go down without losing access to data can be derived based on the brick configuration/distribution. Please let us know the brick distribution plan. Regards, Sunil kumar Acharya Senior Software Engineer Red Hat

Hi All, anyone had the same experience? Could you provide me some information about this error? It happens only on GlusterFS file system. Thank you, Mauro > Il giorno 20 dic 2017, alle ore 16:57, Mauro Tridici <mauro.tridici at cmcc.it> ha scritto: > > > Dear Users, > > I?m experiencing a random problem ( "file changed as we read it? error) during tar files

Defaults should be fine in your size. In big clusters I usually set event-threads to 4. On Mon, Sep 18, 2017 at 10:39 PM, Mauro Tridici <mauro.tridici at cmcc.it> wrote: > > Dear All, > > I just implemented a (6x(4+2)) DISTRIBUTED DISPERSED gluster (v.3.10) volume > based on the following hardware: > > - 3 gluster servers (each server with 2 CPU 10 cores, 64GB RAM, 12

As I said before, I'm not a linux expert. In which file of kernel source can I look for any missing code ? And specially what do I have to check ? __________________________________________ Mauro Staretz - MI Montreal Inform?tica Ltda Microsoft MCSE+I / MCDBA / MCP - Oracle OCP Tel: 55-21-2291-6116 R.2104 Fax: 55-21-2533-6028 __________________________________________ -----Mensagem