Greetings list,
I've been using DUNDi for some time now to prevent calls between users going
out via PSTN if there's no need, set up as follows:
[macro-dundi-e164]
exten => s,1,Goto(${ARG1},1)
include => dundi-e164
[dundi-e164]
include => in-e164
switch => DUNDi/e164
My outbound call macro tries [macro-dundi-e164] first, if that fails then goes
onto PSTN connectivity.
However, I noticed a strange error last night when programming up a simple IVR
for a new customer. I added the following to [in-e164]:
exten => <number>,n,Background(ivr/hello)
exten => <number>,n,WaitExten(5)
; service
exten => 1,1,Macro(queue, service,300)
; accounts
exten => 2,1,Macro(queue,accounts,300)
exten => t,1,Goto(<number>,1)
(e164 number removed to protect client's privacy)
This works fine when calling externally, but when calling internally via DUNDi,
it's impossible to hit either IVR button because the call appears to still be
in the originating context rather than [in-e164].
I tried getting round this by changing the first line in [macro-dundi-e164]
from:
exten => s,1,Goto(${ARG1},1)
to:
exten => s,1,Goto(in-e164,${ARG1},1)
However, this breaks all external calling with an invalid extension error.
Can anyone suggest a way round this?
Thanks in advance.
Regards,
Chris
--
C.M. Bagnall, Director, Minotaur I.T. Limited
For full contact details visit http://www.minotaur.it
This email is made from 100% recycled electrons
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
