I tested the script on a 0.6.5 system with geni586 0n 4/30 and it works
as advertised.
How does this differ from that series of postings?
John Novack
Noël Nachtegael wrote:
It's difficult for me to believe that this is an asterisk 1.4.24.1
problem.
I didn't found any reference to such cases i
It's difficult for me to believe that this is an asterisk 1.4.24.1 problem.
I didn't found any reference to such cases in any change logs or
asterisk main forums.
I can't belive that I'm the only one creating callfiles with the
'classical' system(echo) commands?
Is there another user creating callf
Have you posed your question on the asterisk users mail list? Have you
checked the change logs from your old version of asterisk up to current?
Somewhere there is documentation that explains the changes that took place.
You just have to track it down.
2009/5/2 Noël Nachtegael
> thank you for t
thank you for this answer.
If this is the situation, what can I do execpt staying with the 0.6.2
version of astlinux?
Am I alone in this case? Is nobody else using the system echo function
to create callback files?
noël
Darrick Hartman wrote:
> Noël Nachtegael wrote:
>
>> thank you for the an
Noël Nachtegael wrote:
> thank you for the answers.
>
> I tried
> ...
> exten => ,n,Hangup()
> exten => h,1,NoOp(appel entrant ${CALLERID(num)} vers canal h)
> ;ajouter le 00 dans le numéro de l'appelant
> exten => h,n,Set(CALLERID(num) = 00${CALLERID(num)})
> exten => h,n,System(echo channel:
thank you for the answers.
I tried
...
exten => ,n,Hangup()
exten => h,1,NoOp(appel entrant ${CALLERID(num)} vers canal h)
;ajouter le 00 dans le numéro de l'appelant
exten => h,n,Set(CALLERID(num) = 00${CALLERID(num)})
exten => h,n,System(echo channel: SIP/mycontext-out/${CALLERID(num)} >
/tm
Also tested with 0.6.5 geni586 version installed on an HP Thin client
and it also works as it should
John Novack
Michael Keuter wrote:
I did the testing with the last 0.65 version and I'm on a 4801 hardware.
again it's working fine with version 0.62
David Kerr wrote:
Yes, maybe. Wh
>I did the testing with the last 0.65 version and I'm on a 4801 hardware.
>again it's working fine with version 0.62
>
>
>David Kerr wrote:
>
>>Yes, maybe. What hardware are you running on?
>>
>>On my Alix2c3 I found
>>considerable instability with the System()
>>command inside dialplans on 0.6
I did the testing with the last 0.65 version and I'm on a 4801 hardware.
again it's working fine with version 0.62
David Kerr wrote:
> Yes, maybe. What hardware are you running on?
>
> On my Alix2c3 I found considerable instability with the System()
> command inside dialplans on 0.6.x versions
Yes, maybe. What hardware are you running on?
On my Alix2c3 I found considerable instability with the System() command
inside dialplans on 0.6.x versions of Astlinux. Problem only existed on my
Alix2c3, was not reproducible on a VMWare test environment. Problem does not
exist on trunk (pre 0.7) v
Noël Nachtegael wrote:
> hi every body,
>
> it's now from the version 0.63 that a dialplan command
> System(echo some text > /tmp/file.ext) in extensions.conf
> doesn't work anymore and hangs up my system.
>
> this command is working on my version 0.62
>
> Has someone encountered the same situa
hi every body,
it's now from the version 0.63 that a dialplan command
System(echo some text > /tmp/file.ext) in extensions.conf
doesn't work anymore and hangs up my system.
this command is working on my version 0.62
Has someone encountered the same situation?
---
12 matches
Mail list logo
