channels: Spelling fixes

Correct typos of the following word families:

appease
permanently
overriding
residue
silliness
extension
channels
globally
reference
japanese
group
coordinate
registry
information
inconvenience
attempts
cadence
payloads
presence
provisioning
mimics
behavior
width
natively
syslabel
not owning
unquelch
mostly
constants
interesting
active
unequipped
brodmann
commanding
backlogged
without
bitstream
firmware
maintain
exclusive
practically
structs
appearance
range
retransmission
indication
provisional
associating
always
whether
cyrillic
distinctive
components
reinitialized
initialized
capability
switches
occurring
happened
outbound

ASTERISK-29714

Change-Id: Ife52ee89cd2170b684fa651ca72b1cb911a57339
This commit is contained in:
Josh Soref
2021-10-30 21:04:31 -04:00
committed by Joshua Colp
parent 4fc59ccc92
commit c1b21bee6d
24 changed files with 75 additions and 75 deletions

View File

@@ -50,7 +50,7 @@ int sip_parse_host(char *line, int lineno, char **hostname, int *portnum, enum a
* \param flags An array of ast_flags that will be set by this function
*
* \note The nat-related values in both mask and flags are assumed to empty. This function
* will treat the first "yes" or "no" value in a list of values as overiding all other values
* will treat the first "yes" or "no" value in a list of values as overriding all other values
* and will stop parsing. Auto values will override their non-auto counterparts.
*/
void sip_parse_nat_option(const char *value, struct ast_flags *mask, struct ast_flags *flags);

View File

@@ -143,7 +143,7 @@ int get_in_brackets_full(char *tmp, char **out, char **residue);
int parse_name_andor_addr(char *uri, const char *scheme, char **name,
char **user, char **pass, char **domain,
struct uriparams *params, char **headers,
char **remander);
char **residue);
/*! \brief Parse all contact header contacts
* \retval 0 success

View File

@@ -444,7 +444,7 @@ enum invitestates {
};
/*! \brief When sending a SIP message, we can send with a few options, depending on
* type of SIP request. UNRELIABLE is moslty used for responses to repeated requests,
* type of SIP request. UNRELIABLE is mostly used for responses to repeated requests,
* where the original response would be sent RELIABLE in an INVITE transaction
*/
enum xmittype {
@@ -1100,7 +1100,7 @@ struct sip_pvt {
int t38_maxdatagram; /*!< T.38 FaxMaxDatagram override */
int request_queue_sched_id; /*!< Scheduler ID of any scheduled action to process queued requests */
int provisional_keepalive_sched_id; /*!< Scheduler ID for provisional responses that need to be sent out to avoid cancellation */
const char *last_provisional; /*!< The last successfully transmitted provisonal response message */
const char *last_provisional; /*!< The last successfully transmitted provisional response message */
int authtries; /*!< Times we've tried to authenticate */
struct sip_proxy *outboundproxy; /*!< Outbound proxy for this dialog. Use ref_proxy to set this instead of setting it directly*/
struct t38properties t38; /*!< T38 settings */

View File

@@ -728,7 +728,7 @@ const char *get_calleridname(const char *input, char *output, size_t outputsize)
/* clear any empty characters in the beginning */
input = ast_skip_blanks(input);
/* make sure the output buffer is initilized */
/* make sure the output buffer is initialized */
*orig_output = '\0';
/* make room for '\0' at the end of the output buffer */