The Asterisk Development Team would like to announce the release of Asterisk
13.34.0.
This release is available for immediate download at
https://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 13.34.0 resolves several issues reported by the
community and would have not
The Asterisk Development Team would like to announce the release of Asterisk
17.5.0.
This release is available for immediate download at
https://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 17.5.0 resolves several issues reported by the
community and would have not been
The Asterisk Development Team would like to announce the release of Asterisk
16.11.0.
This release is available for immediate download at
https://downloads.asterisk.org/pub/telephony/asterisk
The release of Asterisk 16.11.0 resolves several issues reported by the
community and would have not
Lately, I read [1].
So it seems both Jitsi desktop and Linphone are on par, on this ;-)))
[1] https://community.jitsi.org/t/busy-lamp-field-bug/15931
Le ven. 5 juin 2020 à 13:34, John Hughes a écrit :
> On 26/05/2020 15:33, Olivier wrote:
>
> Hi John,
>
> 1. Could you get any further, in your
On Wed, Jun 10, 2020 at 3:25 PM Administrator wrote:
> Hi list,
>
> We have a strange behavior: a customer Snom300 behind a public FW has
> contact like
>
> contact :
> sip:user@x.y.39.147:2048;x-ast-orig-host=169.254.252.1:2048
x-ast-orig-host is a header we add to incoming
I have a call from a call file:
Action: Originate
Async: yes
Channel: SIP/2012
Codecs: ulaw,alaw,gsm
Context: dialout
Exten: callprogress
Priority: 1
Timeout: 2
Variable: SIPADDHEADER="Alert-Info: Ring Answer"
ActionID: 100014
CallerID: Axis < 525 >
The SIP/2012 is a IP Speaker on the
On Thu, 11 Jun 2020, Jerry Geis wrote:
I have a call from a call file:
This looks a lot more like an AMI event than a call file. In any case, it
doesn't matter.
Action: Originate
Async: yes
Channel: SIP/2012
Codecs: ulaw,alaw,gsm
Context: dialout
Exten: callprogress
Priority: 1
Timeout:
