search for: tincan

Displaying 4 results from an estimated 4 matches for "tincan".

2020 Feb 04
0
Always Be Conferencing v16e - pure AEL-based dial plan solution
...e conf type name. exten => 922,n,Set(ringtime=120) ; MAYBE CHANGE ME! Rings remote end / path for 2 minutes. exten => 922,n,AELSub(pngnpbx-abc-simple,${abctypename}) ; Simple setup. (Either "abc-simple", "abc-init" or "abc-tincan" must be first.) exten => 922,n,AELSub(pngnpbx-abc-path,1,${ringtime},${path}) ; Set the first (and only) call path to use on call to remote end. exten => 922,n,AELSub(pngnpbx-abc-remote,${callback},static) ; Originate out the path/trunk using your call-back number as the Ca...
2009 Nov 18
2
jspeex question
The link is http://www.adobe.com/devnet/rtmp/. TC Message stands for TinCan message. It is 11 bytes long, first byte is message type, three bytes of payload length four bytes of timestamp and three bytes of stream ID. The first byte of the payload for audio message is the format byte and the rest of the byte is the payload. Jozsef ----- Original Message ---- From: Je...
2009 Nov 18
0
jspeex question
...t for the first byte) to the jspeex decoder and write the results to a file. Jozsef - it is possible to specify 8KHz in the flash client and decode it as such. Speex definitely does not need to be 16KHz. Jozsef Vass wrote: > The link is http://www.adobe.com/devnet/rtmp/. TC Message stands for TinCan message. It is 11 bytes long, first byte is message type, three bytes of payload length four bytes of timestamp and three bytes of stream ID. > > The first byte of the payload for audio message is the format byte and the rest of the byte is the payload. > > Jozsef > > > > -...
2009 Nov 18
3
jspeex question
FLV contains TC messages? TC message payload contains a format byte and speex frames (up to eight). In the format byte 0xb0 indicates speex. Speex is always 16 kHz, 16 bit, mono. Jozsef Message: 1 Date: Mon, 16 Nov 2009 14:40:20 -0600 From: Jeff Ramin <jeff.ramin at singlewire.com> Subject: [Speex-dev] jspeex question To: speex-dev at xiph.org Message-ID: <4B01B8B4.8020904 at