kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-09-02 11:06:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

chan_sip: Remove deprecated module.

Browse Source 
ASTERISK-30297

Change-Id: Ic700168c80b68879d9cee8bb07afe2712fb17996
This commit is contained in:
Mike Bradeen
2022-11-28 13:05:21 -07:00
committed by George Joseph
parent e66c5da145
commit 4095a382da
80 changed files with 177 additions and 45491 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
rest-api/api-docs/channels.json
View File

@@ -2129,7 +2129,7 @@
"protocol_id": {
"required": true,
"type": "string",
"description": "Protocol id from underlying channel driver (i.e. Call-ID for chan_sip/chan_pjsip; will be empty if not applicable or not implemented by driver)."
"description": "Protocol id from underlying channel driver (i.e. Call-ID for chan_pjsip; will be empty if not applicable or not implemented by driver)."
},
"name": {
"required": true,

16
rest-api/api-docs/endpoints.json
View File

@@ -31,7 +31,7 @@
"parameters": [
{
"name": "to",
"description": "The endpoint resource or technology specific URI to send the message to. Valid resources are sip, pjsip, and xmpp.",
"description": "The endpoint resource or technology specific URI to send the message to. Valid resources are pjsip, and xmpp.",
"paramType": "query",
"required": true,
"allowMultiple": false,
@@ -39,7 +39,7 @@
},
{
"name": "from",
"description": "The endpoint resource or technology specific identity to send this message from. Valid resources are sip, pjsip, and xmpp.",
"description": "The endpoint resource or technology specific identity to send this message from. Valid resources are pjsip, and xmpp.",
"paramType": "query",
"required": true,
"allowMultiple": false,
@@ -55,7 +55,7 @@
},
{
"name": "variables",
"descriptioni": "The \"variables\" key in the body object holds technology specific key/value pairs to append to the message. These can be interpreted and used by the various resource types; for example, pjsip and sip resource types will add the key/value pairs as SIP headers,",
"descriptioni": "The \"variables\" key in the body object holds technology specific key/value pairs to append to the message. These can be interpreted and used by the various resource types; for example, pjsip resource types will add the key/value pairs as SIP headers,",
"paramType": "body",
"required": false,
"dataType": "containers",
@@ -87,7 +87,7 @@
"parameters": [
{
"name": "tech",
"description": "Technology of the endpoints (sip,iax2,...)",
"description": "Technology of the endpoints (pjsip,iax2,...)",
"paramType": "path",
"dataType": "string"
}
@@ -161,7 +161,7 @@
},
{
"name": "from",
"description": "The endpoint resource or technology specific identity to send this message from. Valid resources are sip, pjsip, and xmpp.",
"description": "The endpoint resource or technology specific identity to send this message from. Valid resources are pjsip and xmpp.",
"paramType": "query",
"required": true,
"allowMultiple": false,
@@ -177,7 +177,7 @@
},
{
"name": "variables",
"descriptioni": "The \"variables\" key in the body object holds technology specific key/value pairs to append to the message. These can be interpreted and used by the various resource types; for example, pjsip and sip resource types will add the key/value pairs as SIP headers,",
"descriptioni": "The \"variables\" key in the body object holds technology specific key/value pairs to append to the message. These can be interpreted and used by the various resource types; for example, pjsip resource types will add the key/value pairs as SIP headers,",
"paramType": "body",
"required": false,
"dataType": "containers",
@@ -239,12 +239,12 @@
"properties": {
"from": {
"type": "string",
"description": "A technology specific URI specifying the source of the message. For sip and pjsip technologies, any SIP URI can be specified. For xmpp, the URI must correspond to the client connection being used to send the message.",
"description": "A technology specific URI specifying the source of the message. For pjsip technology, any SIP URI can be specified. For xmpp, the URI must correspond to the client connection being used to send the message.",
"required": true
},
"to": {
"type": "string",
"description": "A technology specific URI specifying the destination of the message. Valid technologies include sip, pjsip, and xmp. The destination of a message should be an endpoint.",
"description": "A technology specific URI specifying the destination of the message. Valid technologies include pjsip, and xmp. The destination of a message should be an endpoint.",
"required": true
},
"body": {