autopatch updates with IAX/SIP notes #97
Conversation
Major step up in autopatch documentation. Added Mason's github info on voip.ms IAX setup and my own flowroute SIP setup info. Using general setup info instead of specific info for voip.ms and flowroute.com, although there is still some specific info in the configs that I think is helpful to leave in there.
There was a problem hiding this comment.
General things to look at :
- Sometimes you refer to the file (rpt.conf) and other times the full path (/etc/asterisk/rpt.conf).
- I noticed that sometimes you refer to "IAX and PJSIP" and other times "PJSIP and IAX".
- It would be good to use a spell checker on the entire file
docs/adv-topics/autopatch.md
Outdated
| This guide includes example configuration files that may need adjustments to get | ||
| working with specific providers and ASL versions. | ||
|
|
||
| This guide will document the general process for setting up IAX2 and SIP providers with expamples for voip.ms IAX and flowroute.com SIP. Any provider should be setup in a similar fashion. |
docs/adv-topics/autopatch.md
Outdated
| ``` | ||
|
|
||
| In the **rpt.conf** configuration file, a context in extensions.conf is defined | ||
| ### rpt.conf | ||
| In the **/etc/asterisk/rpt.conf** configuration file, a context in extensions.conf is defined | ||
| in a node stanza using the context key: |
There was a problem hiding this comment.
I'm trying to process this sentence. I think what you are trying to write is that one needs to setup a context in the /etc/asterisk/extensions.conf file. Then, in the /etc/asterisk/rpt.conf file one needs to reference that context in a node stanza.
docs/adv-topics/autopatch.md
Outdated
| @@ -66,64 +161,279 @@ context = autopatch ; dialing context for phone | |||
| callerid = "Repeater" <0000000000> ; callerid for phone calls | |||
| accountcode = RADIO ; account code (optional) | |||
| ``` | |||
| Also in the **rpt.conf** file, entries are added to the function stanza so | |||
| Also in the **/etc/asterisk/rpt.conf** file, entries are added to the function stanza so | |||
There was a problem hiding this comment.
I'm not wild about "Also in the ...". Maybe:
In the rpt.conf file, entries should also be added to the function stanza so ...
| | exten | Overrides the default autopatch extension. | | ||
| | nostar | Disables the repeater function prefix | | ||
|
|
||
| #### Create a Script to Handle Terminating Calls |
There was a problem hiding this comment.
Does this script work if exec'd as the "asterisk" user (as would happen with the "0 = cmd,..." function you detailed above)?
| #!/bin/bash | ||
| # Target pattern to match (adjust as needed for different calls) | ||
| TARGET_PATTERN="IAX2/voipms-" | ||
| # TARGET_PATTERN="PJSIP/flowroute-" |
There was a problem hiding this comment.
Is there any way to avoid having to specify explicit patterns here (and below where the patterns are checked)? I'm thinking that any "PJSIP/" can be targeted. The question is whether we can tell the difference from an IAX2 "ASL" connection and an IAX2 "phone" connection.
docs/adv-topics/autopatch.md
Outdated
| ``` | ||
| For outbound SIP connections it should look like this: | ||
|
|
||
| ### extentions.conf |
There was a problem hiding this comment.
extentions.conf --> extensions.conf
... and do you want to use the full path?
docs/adv-topics/autopatch.md
Outdated
| In **/etc/asterisk/extensions.conf**, a stanza for the autopatch context is added which | ||
| refers to the peer stanza in iax.conf or pjsip.conf. These examples will likely need to be adjusted to work with a specific provider: | ||
|
|
||
| For outbound IAX connections extensions.conf: |
There was a problem hiding this comment.
For outbound IAX connections, add :
docs/adv-topics/autopatch.md
Outdated
| exten => _NXXNXXXXXX,n,Hangup() | ||
|
|
||
| ``` | ||
| For outbound SIP connections extensions.conf, this example uses IP auth: |
There was a problem hiding this comment.
For outbound SIP connections using IP auth, add :
docs/adv-topics/autopatch.md
Outdated
| exten => _NXXNXXXXXX,n,Hangup() | ||
| ``` | ||
|
|
||
| Setup 911 extention |
There was a problem hiding this comment.
To setup the 911 extension, add :
(and yes, here you also need to correct the spelling of extension :-)
|
Happy to update the misspellings. If you are looking for someone to do things like update every instance of a filename and add or remove the full path, I'm not the right person for that type of editing. |
|
We should always be using full paths to files. They should be updated/fixed by the requestor at merge time. |
|
It feels to me that with the amount of documentation updates that are needed just to get to a point where people can be successful by using the documentation, perhaps a new wiki or something that's easier to update would better serve the project. |
|
@knobby4444 The great thing about documentation platforms is no one reads it regardless of how you publish it... |
Major step up in autopatch documentation. Added Mason's github info on voip.ms IAX setup and my own flowroute SIP setup info. Other updates include duplex info.