• No se han encontrado resultados

CAPÍTULO I LAS CIENCIAS DEL HERMAFRODITISMO Y DE LA INTERSEXUALIDAD:

ESTADOS INTERSEXUALES

32.1 B

ACKUP AND

R

ESTORE

There is an ongoing issue with Backup and Restore. It is difficult to ascertain with confidence which version has an accurate backup and Restore facility. Users have to test each version of AAH installed individually. This is merely a head up for users.

32.2 C

ONFLICT BETWEEN

ZAP C

ARD AND

FAX M

ODULE

There is a reported conflict between ZAP cards and FAX module that may require certain files to be removed as Asterisk v2.4/2.5, it will not start unless app_rxfax.so and app_txfax.so is removed from /usr/lib/asterisk/modules. This is reported on the following link.

http://sourceforge.net/forum/forum.php?thread_id=1433624&forum_id=420324

32.3 E

DITING EMAIL NOTIFICATION MESSAGE

When customising or editing your e-mail notification message in /etc/asterisk/vm_email.inc you are advised to use an editor (such as nano) as I have found that AMP tends to loose the embedded formatting character.

32.4 E

NDLESS

L

OOP DURING

D

IRECTORY SEARCH

(

V

2.0)

When setting up the general setting in AAH 2.0, avoid selecting “first or last name” as the search criteria for Company Directory. Selecting this option will cause Digital Receptionist to go into an endless loop if either # or *411 is selected during the playback of Digital receptionist (Read on for the fix).

You may however select “first name” or “last name” however if # is chosen during the playback of Digital Receptionist, the endless loop will also occur as I have found out below.

In AAH 2.0, when Digital receptionist answers a call, if a caller press # for directory, the Digital receptionist will go into an endless loop. To overcome this, I took the easiest way out by changing the script relating to # in extensions.conf to this:

;DIR-CONTEXT set in Digital Receptionist exten => #,1,Wait(1)

exten => #,2,AGI(directory,${DIR-CONTEXT},ext-local,${DIRECTORY:0:1}${DIRECTORY_OPTS})

exten => #,3,Playback(vm-goodbye) exten => #,4,Hangup

As it turned out, there is a number of .gsm sound files missing from the /var/lib/asterisk/sounds directory. This is documented here:

http://sourceforge.net/tracker/index.php?func=detail&aid=1365968&group_id=123387&atid=696349

You may download the missing sound files from the above link and include them in the /var/lib/asterisk/sounds directory and problem solved.

If you have made the changes as I did above, please ensure that you insert the “o” back ☺

This issue has been addressed in version 2.1

32.5 F

LASH

O

PERATOR

P

ANEL

(B

UG

D

ETECTED IN VERSION

1.3)

1. After doing the manual edits of the password (security), Asterisk@Home need to be restarted. Otherwise the new password will not take effect. The old default password of “passw0rd” will still be in effect.

To restart, using CLI, type the following: amportal stop to stop AAH and amportal start will restart AAH.

2. Sometimes the flash panel cannot tell when a hang-up has occurred. It will show your extension as being busy but to no one. This can be fixed by restarting asterisk and hopefully it will be fixed in further versions of FOP. 3. There is an absolute call transfer timeout but at this stage, information on

it is still elusive. Maybe someone will be able to contribute to the remedy. (Source Reference: Mark Brooker, asternic.org)

32.6 M

AX

C

HANNELS

B

UG

There has been reports that due to a bug to deprecated command, it makes Asterisk@Home's calculation of maximum channels invalid. To fix it, you have to do the following:

1. Goto Config edit and open extensions.conf 2. Under the [macro-dialout-trunk], do the following:

a. Comment out line s,7 thus

;exten => s,7,CheckGroup(${OUTMAXCHANS_${ARG1}})

b. Insert a new line as shown below:

exten => s,7,GotoIf($[${GROUP_COUNT()} > ${OUTMAXCHANS_${ARG1}}]?108)

3. Then click the Update button and reload Asterisk to activate the change.

32.6.1 Corrected in version 2.8

32.7 R

ING

G

ROUP

H

UNT

S

YNTAX

B

UG

(

V

2.2

AND V

2.5)

The ring group hunt syntax bug that appears in AAH version 2.2 seems to stay with us in AAH version 2.5. This caused Asterisk to only ring all extension or it will just progress to your no answer option if the hunt option is selected.

Neilmc, one of the Whirlpool Forum participant pointed me to the solution obtained by Christian Müller at

http://tinyurl.com/nutqk

that discovered the error as a result of a typo in extensions.conf.

The offending line is under the [macro-dial] context:

exten => s,22,GotoIf($[$[${HuntMembers} >= 1]?30 ) ; if this is from rg-group, don't strip prefix

This should be replaced with:

exten => s,22,GotoIf($[${HuntMembers} >= 1]?30 ) ; if this is from rg-group, don't strip prefix.

The typo error is the extra $[ that appears in the original line. What a difference a

“$[“ made

32.7.1 Corrected in version 2.8

This error has been addressed in version 2.8

32.8 S

ECURING

A

STERISK

@H

OME CONSOLE

A

LT

+F9

Asterisk has a hidden feature/security risk. On the keyboard you can just press down “Alt” & “F9” simultaneously, then you get access to Asterisk console without having to logon to the actual system and with no Asterisk restrictions. I have not personally verified this but I am not taking any chances. However to exploit this, one need to have a direct access to the Asterisk computer ☺

This can be a security risk and to disable it just edit /usr/sbin/safe_asterisk

nano /usr/sbin/safe_asterisk

and change CONSOLE=yes to CONSOLE=no

And while you are at it, change the email address as well so you get emails when Asterisk crashes.

Now restart asterisk with the command: amportal stop to stop AAH and amportal start will restart AAH.

32.9 S

OUND

D

IRECTORY

P

ERMISSION

(

V

2.6)

There is a permission issue with the /var/lib/asterisk/sounds directory which breaks the voicemail prompts and drops back to busy.

To overcome this, the permission to the /var/lib/asterisk/sounds directory should be set to 755 using the chmod command at the command line.

chmod 755 /var/lib/asterisk/sounds

32.10 W

AKE

U

P

C

ALLS

(V2.2)

There are problems with the Wakeup Calls. A number of the voice files assumed to be in /var/lib/asterisk/sounds/extra are missing. In fact the directory doesn’t exist in the Asterisk@Home setup.

The wakeconfirm application that is used to prompt the user as a confirmation method that user is actually awake, is also missing.

As a result, WakeUp Calls will not work.

32.10.1 Corrected in version 2.4

This bug has been addressed in Version 2.4; however the wakeconfirm is still not working.