@Dashrender When your devices are shown as UNAVAILABLE but marked as REGISTERED, try to decrease the qualify frequency value on the technology profile assigned to your devices. For PJSIP is usually the "Default PJSIP Profile", for SIP, is usually the "Default SIP Profile".
About, One Way Audio, remember to configure the External Address and the local address on the SIP Settings or PJSIP Settings, depending on the technology you are using.
@JaredBusch On Next major versions of VitalPBX, the main protocol will be PJSIP instead of SIP, due as you know SIP has been totally deprecated.
@JaredBusch Well looks like you are a gentleman, I have not offended you in any way. But if you want to continue in that way don't worry I will not continue posting on your blog.
I am just giving you an answer to your "issues".
Have a good day or night.
@JaredBusch This is required depending on the type of authentication you are implementing. I guess that when you use user, password, and registration you don't need to define this parameter.
However, I guess with the documentation provided by VitalPBX and Skyetel the users can configure this provider without issues.
https://community.vitalpbx.org/skyetel-sip-trunk-with-vitalpbx/
The conclusion:
VitalPBX comes with the parameter "srv_lookup" enabled by default, and, you must define either the IP addresses or the domain in the match field when connecting trunks using skyetel.
@JaredBusch Then, put na.skyetel.com on the match field. That's it
@JaredBusch As I told you, you can try putting srv.skyetel.com in the match field. You need to define the match parameter because is part of the identify section. You can put IP addresses or domains.
@JaredBusch In that case you must put the host in the match field. I guess you must put: srv.skyetel.com
Skyetel said in your blog:
That being said, if you are feeling ambitious and want to try an unpublished (but supported) technique, you can use srv.skyetel.com instead of term.skyetel.com. It uses SRV records instead of A records. We keep this unpublished to encourage people to use our IPs - SRV causes a lot of problems for inexperienced administrators, but some PBXs require it when using multiple IPs as we do.
You've created a tutorial for FPBX, and you defined the match field also as you did on VitalPBX. So, I guess that's the right process.
https://mangolassi.it/topic/19615/setting-up-a-skyetel-sip-trunk-in-freepbx
@JaredBusch Match is required for incoming authentication. The remote host is for outbound calls.
More info here:
https://github.com/asterisk/asterisk/blob/master/configs/samples/pjsip.conf.sample#L1304
Skyetel Documentation
https://support.skyetel.com/hc/en-us/articles/360041173493-Skyetel-IP-Addresses
Inbound IPs
These are the IP Address inbound calls will originate from
Description
SIP IP Addresses
North West 52.41.52.34
South West 52.8.201.128
North East 52.60.138.31
South East 50.17.48.216
Tutorial: https://support.skyetel.com/hc/en-us/articles/360041177833-VitalPBX
@JaredBusch That option comes enabled by default, well in case you are talking of this option:
@JaredBusch On Next major versions of VitalPBX, the main protocol will be PJSIP instead of SIP, due as you know SIP has been totally deprecated.
@Dashrender When your devices are shown as UNAVAILABLE but marked as REGISTERED, try to decrease the qualify frequency value on the technology profile assigned to your devices. For PJSIP is usually the "Default PJSIP Profile", for SIP, is usually the "Default SIP Profile".
About, One Way Audio, remember to configure the External Address and the local address on the SIP Settings or PJSIP Settings, depending on the technology you are using.
@JasGot You can write to [email protected] in case you get banned by the VitalPBX's forum or if you have any kind of license, and you present some issue with the add-ons or the core system.