SOLVED Turn off announcement of callee number - how?

[wolf Paul]

After a longer hiatus due to a house move and ensuing chaos I recently installed and put into service a Raspberry Pi 3 with the current version of Incredible PBX.

As usual, I am very pleased - great work!

There is one feature I would like to turn off and wonder if there is a way to do it without manually editing config files:
The announcement in Allison's voice of the callee number just after dialling, followed by "Connecting, one moment please." in a male voice.

Any suggestions?

If there is no GUI method, a pointer to the context to edit would also be appreciated.

 

[kyle95wm]

I have no idea what you're talking about. I have an RPi 3 set up and dont encounter this.

 

[wolf Paul]

I am running Raspian 8 (Jessie) and Incredible PBX 12.0.74, and here is what this feature sounds like:
http://wnpaul.net/Callee-Announcement-PIAF.mp3
http://wnpaul.net/Callee-Announcement-PIAF.mp3
Here is the output of "asterisk -r -vvvvvvv" during such a call:

-- Accepting AUTHENTICATED call from 192.168.113.180:46743:
-- > requested format = gsm,
-- > requested prefs = (),
-- > actual format = ulaw,
-- > host prefs = (ulaw|alaw|gsm),
-- > priority = mine
-- Executing [0080001503@from-internal:1] SayDigits("IAX2/21-12230", "80001503,") in new stack
-- <IAX2/21-12230> Playing 'digits/8.gsm' (language 'en')
[2017-04-18 11:43:13] NOTICE[1959]: chan_iax2.c:12330 __iax2_poke_noanswer: Peer '22' is now UNREACHABLE! Time: 221
-- <IAX2/21-12230> Playing 'digits/0.gsm' (language 'en')
-- <IAX2/21-12230> Playing 'digits/0.gsm' (language 'en')
[2017-04-18 11:43:14] NOTICE[1954]: chan_iax2.c:11132 socket_process_helper: Peer '22' is now REACHABLE! Time: 215
-- <IAX2/21-12230> Playing 'digits/0.gsm' (language 'en')
-- <IAX2/21-12230> Playing 'digits/1.gsm' (language 'en')
-- <IAX2/21-12230> Playing 'digits/5.gsm' (language 'en')
-- <IAX2/21-12230> Playing 'digits/0.gsm' (language 'en')
-- <IAX2/21-12230> Playing 'digits/3.gsm' (language 'en')
-- Executing [0080001503@from-internal:2] EAGI("IAX2/21-12230", "asteridex.agi,0080001503") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/asteridex.agi
-- <IAX2/21-12230>AGI Script asteridex.agi completed, returning 0
-- Executing [0080001503@from-internal:3] GotoIf("IAX2/21-12230", "0?97") in new stack
-- Executing [0080001503@from-internal:4] NoOp("IAX2/21-12230", "Number to Dial: ") in new stack
-- Executing [0080001503@from-internal:5] NoOp("IAX2/21-12230", "Person to Dial: ") in new stack
-- Executing [0080001503@from-internal:6] Flite("IAX2/21-12230", ""Connecting to: . One moment please."") in new stack
-- <IAX2/21-12230> Playing '/tmp/flite_15284804.slin' (language 'en')
-- Executing [0080001503@from-internal:7] Goto("IAX2/21-12230", "outbound-allroutes,,1") in new stack
-- Goto (outbound-allroutes,0080001503,1)

 

[kyle95wm]

That is really weird. Can you please post an image of pbxstatus command?

 

[kyle95wm]

Also I'm running 13.12.17

 

[wolf Paul]

Here is the output of pbxstatus: http://wnpaul.net/pbxstatus.png

Well, the versions are getting confusing. The version number I posted earlier (12.0.74) is what the GUI displays right after logging in.

pbxstatus shows Incredible PBX 13-12.17 at the top, and then below it says Incredible GUI 12.0.39. And "asterisk -r" shows "Asterisk 13.12.2".

 

[kyle95wm]

Please consider burning the latest 2017 image from source forge

 

[kyle95wm]

Here's what my pbxstatus looks like: http://prntscr.com/ey02ou

 

[kyle95wm]

any ideas @wardmundy?

 

[ostridge]

my pbxstatus looks like: http://prntscr.com/ey02ou

Your status screen shows both Asterisk and iptables as Down; however your Asterisk CLI has asterisk working:

output of "asterisk -r -vvvvvvv" during such a call:

iptables methodology has changed and is included in the latest image for Rpi . Please read the following link
IPBX on Pi with non-standard network

It is essential to get iptables firewall up and running, or your server is vulnerable to attack.

 

[wolf Paul]

I have found the source of my problem.

Here in Austria, it is customary to use 0 to get an outside line (instead of 9 as in the US), and all non-local numbers, including mobile, begin with a 0. Thus, everything except internal extensions and local numbers begins with 00 and that triggers Asteridex. The SayDigit and the Connecting to come from the block of Asteridex code in extensions_custom.conf.

Since I don't really use Asteridex anyway I simply commented these eleven lines, and voila, problem solved (for now).

NOW: how do I change the Subject prefix to "SOLVED" ???

 

[ostridge]

@wolf Paul
Glad you have got your workaround; however I think I remember some code in an earlier version asterisk11 for rpi on debian wheezy where the Astridex was on _000.
As you don't need astridex perhaps you won't need to ask @wardmundy for that code.

 

[wolf Paul]

@wolf Paul
Glad you have got your workaround; however I think I remember some code in an earlier version asterisk11 for rpi on debian wheezy where the Astridex was on _000.
As you don't need astridex perhaps you won't need to ask @wardmundy for that code.

Well, that should be easy enough, anyway ... just change _00. to _000. -- I just didn't want anything with multiple zeros to actually do anything, and as you say, since I don't need it ...

My initial problem was that I could not find where the speaking of the called number came from ... but some more digging helped there.