https://cloud.google.com/speech-to-text/docs/streaming-recognize
Soporte & Consultoria
miércoles, 6 de octubre de 2021
https://cloud.google.com/speech-to-text/docs/streaming-recognize
https://cloud.google.com/speech-to-text/docs/streaming-recognize
jueves, 23 de septiembre de 2021
Bandwidth Requirements
General Requirement:
Bria Mobile: Wi-Fi or a 3G/4G wireless connection.
Bria Desktop: IP network connection (broadband, LAN, wireless); Constant Internet connection
Specifics:
Since Bria is using VoIP technology, the internet requirement or bandwidth required by Bria for VoIP communications varies hugely depending on several key factors: the compression technology (i.e. which codec), packet overheads, the network protocol used (Ethernet for example). The main thing that Bria has an impact on is around the type of compression used, i.e. which codec and what the bitrate is for that codec. See below some commonly used codecs, their bitrate and estimated bandwidth usage:
| Codec | Bitrate | Bandwidth Usage |
| G.711 | 64 Kbps | 87.2 Kbps |
| G.729 | 8 Kbps | 31.2 Kbps |
| G722 | 48-64 Kbps | 80 Kbps |
| Opus | 6 Kbps to 510 Kbps (variable bit rate) | Varies, up to 500 kbps for HD Audio |
When more bandwidth is available, quality and usage will increase to deliver the best experience. Below is a table detailing the type of Streams, minimum and recommended download/upload speeds for best user experience:
| Stream Type | Minimum Download/Upload Speed | Recommended Download/Upload Speed |
| Audio Stream | 90kbps/90kbps (G.711 Codec) | 100kbps/100kbps(Normal Audio) |
| 40kbps/40kbps (G.729 Codec) | 500kbps/500kbps (HD Audio using Opus) | |
| 30kbps/30kbps (Opus or Silk Codec) | ||
| Video Stream - QCIF | 128kbps / 128kbps | 256kbps / 256kbps |
| Video Stream - CIF | 256kbps / 256kbps | 512kbps / 512kbps |
| Video Stream - VGA | 512kbps / 512kbps | 768kbps / 768kbps |
| Video Stream - 720p | 1024kbps / 1024kbps | 1512kbps / 1512kbps |
| Video Stream - HD(1080p) | 1.2 Mbps/ 1.2 Mbps | 2 Mbps /2 Mbps |
Notes:
- Audio Stream: Audio codecs used are G711, OPUS or SILK which are Variable Bit Rate Codecs and G729 codec
- G711 is one of the most mature and widely used audio codecs for VoIP. G711 is a good choice for networks where traditional telephony quality is acceptable and there is enough bandwidth in the internal network infrastructure to support the expected number of 64 Kb/s voice conversations.
- Opus supports both constant and variable/dynamically adjustable bitrates between 6 Kbps to 510 Kbps (according to opus-codec.org) It can be configured with ultra-low bitrates for networks with the most limited bandwidths, and also includes HD Audio.
- G729 codec uses an algorithm for extreme compression, works well with low bandwidth.
- VoIP audio/video stream is full-duplex, meaning that both ends can send/receive traffic at the same time so:
- Actual bandwidth would be x 2
- Multiply by 3 for a 3 party conference call,
- Upload speeds are obviously as important as download speeds(there’s usually and different rates depending on the Internet Service Provider)
- Incoming/outgoing media streams may be encoded with different codecs and hence calculating actual bandwidth is not as simple as x 2 multiplication
- There are various factors that will affect the bandwidth that a Video Call on Bria consumes, including Resolution and Frame Rate, and most importantly the Video Codec used. For H.264 codec, a fairly accurate table is available on Wikipedia under the “Levels” section. Bria supports up to 1080P resolution which allows offering up to Level 3.1 profiles for a Video Call.
Supported Bria Video Image Resolutions:
QCIF = 176x144 pixels
CIF = 352x288 pixels
VGA = 640x480 pixels
HD-720p = 1280x720 pixels
In summary, to estimate the network bandwidth required to support Bria Softphones optimally:
- Choose or know the CODEC on Bria you plan to deploy in your network.
- Multiply each CODEC's bandwidth requirements by the number of simultaneous calls the network must support.
- For example, if you are using a G.729 CODEC for audio calling, and you need to support 100 simultaneous calls, then multiply 40 Kbits per second by 100 calls to calculate that you need 4 Mbps of symmetrical transmit-and-receive bandwidth to support the estimated call volume. If you are using G711 a/u codec, multiply 87.2 Kbits per second by 100 calls – the result is 8.72 ~ 9 Mbps of symmetrical transmit-and-receive bandwidth to support the estimated call volume. Please refer to the table above for the minimum and recommended download & upload speeds.
- When calculating the total network load, add the bandwidth required to support Bria traffic (including Multiparty Conferencing requirements and or Video calling if enabled) to the bandwidth required to support your existing network traffic.
viernes, 3 de septiembre de 2021
Asterisk webrtc configuration
https://wiki.asterisk.org/wiki/display/AST/Configuring+Asterisk+for+WebRTC+Clients
asterisk -vvvvvvvvvgc” | grep http
https://community.asterisk.org/t/asterisk-15-https-server/72517/6
https://feeding.cloud.geek.nz/posts/using-letsencrypt-cert-with-asterisk/
--------------------channel driver= pjsip
Transport = 0.0.0.0-wss
Enable AVPF = yes
Enable ICE Support =Yes
Enable rtcp Mux =Yes
RTP Symmetric = Yes
Rewrite Contact = Yes
Force rport= Yes
Enable WebRTC defaults =Yes
Media Encryption = SRTP
Allow Non-Encrypted Media (Opportunistic SRTP) = Yes
Enable DTLS= No
Auto Generate Certificate =No
Use Certificate = default
DTLS Verify = fingerprint
DTLS Setup = Act/Pass
DTLS Rekey Interval= 0
SIP explained
https://datatracker.ietf.org/doc/html/rfc7329
martes, 31 de agosto de 2021
OPTION REQUEST explained
11.1 Construction of OPTIONS Request An OPTIONS request is constructed using the standard rules for a SIP request as discussed in Section 8.1.1. A Contact header field MAY be present in an OPTIONS. An Accept header field SHOULD be included to indicate the type of message body the UAC wishes to receive in the response. Typically, this is set to a format that is used to describe the media capabilities of a UA, such as SDP (application/sdp). The response to an OPTIONS request is assumed to be scoped to the Request-URI in the original request. However, only when an OPTIONS is sent as part of an established dialog is it guaranteed that future requests will be received by the server that generated the OPTIONS response. Example OPTIONS request: OPTIONS sip:carol@chicago.com SIP/2.0 Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKhjhs8ass877 Max-Forwards: 70 To: <sip:carol@chicago.com> From: Alice <sip:alice@atlanta.com>;tag=1928301774 Call-ID: a84b4c76e66710 CSeq: 63104 OPTIONS Contact: <sip:alice@pc33.atlanta.com> Accept: application/sdp Content-Length: 0 Rosenberg, et. al. Standards Track [Page 67]
RFC 3261 SIP: Session Initiation Protocol June 2002 11.2 Processing of OPTIONS Request The response to an OPTIONS is constructed using the standard rules for a SIP response as discussed in Section 8.2.6. The response code chosen MUST be the same that would have been chosen had the request been an INVITE. That is, a 200 (OK) would be returned if the UAS is ready to accept a call, a 486 (Busy Here) would be returned if the UAS is busy, etc. This allows an OPTIONS request to be used to determine the basic state of a UAS, which can be an indication of whether the UAS will accept an INVITE request. An OPTIONS request received within a dialog generates a 200 (OK) response that is identical to one constructed outside a dialog and does not have any impact on the dialog. This use of OPTIONS has limitations due to the differences in proxy handling of OPTIONS and INVITE requests. While a forked INVITE can result in multiple 200 (OK) responses being returned, a forked OPTIONS will only result in a single 200 (OK) response, since it is treated by proxies using the non-INVITE handling. See Section 16.7 for the normative details. If the response to an OPTIONS is generated by a proxy server, the proxy returns a 200 (OK), listing the capabilities of the server. The response does not contain a message body. Allow, Accept, Accept-Encoding, Accept-Language, and Supported header fields SHOULD be present in a 200 (OK) response to an OPTIONS request. If the response is generated by a proxy, the Allow header field SHOULD be omitted as it is ambiguous since a proxy is method agnostic. Contact header fields MAY be present in a 200 (OK) response and have the same semantics as in a 3xx response. That is, they may list a set of alternative names and methods of reaching the user. A Warning header field MAY be present. A message body MAY be sent, the type of which is determined by the Accept header field in the OPTIONS request (application/sdp is the default if the Accept header field is not present). If the types include one that can describe media capabilities, the UAS SHOULD include a body in the response for that purpose. Details on the construction of such a body in the case of application/sdp are described in [13]. Rosenberg, et. al. Standards Track [Page 68]
RFC 3261 SIP: Session Initiation Protocol June 2002 Example OPTIONS response generated by a UAS (corresponding to the request in Section 11.1): SIP/2.0 200 OK Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKhjhs8ass877 ;received=192.0.2.4 To: <sip:carol@chicago.com>;tag=93810874 From: Alice <sip:alice@atlanta.com>;tag=1928301774 Call-ID: a84b4c76e66710 CSeq: 63104 OPTIONS Contact: <sip:carol@chicago.com> Contact: <mailto:carol@chicago.com> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE Accept: application/sdp Accept-Encoding: gzip Accept-Language: en Supported: foo Content-Type: application/sdp Content-Length: 274 (SDP not shown)
https://datatracker.ietf.org/doc/html/rfc3261#page-67
martes, 24 de agosto de 2021
FreePBX not sending email from GUI but command line works
/usr/sbin/sendmail -t
https://community.freepbx.org/t/updated-to-freepbx-13-sendmail-working-extension-emails-are-not/56731/9