Unsolved VitalPBX 3
-
@ing-joserivera26 said in VitalPBX 3:
@JaredBusch Match is required for incoming authentication. The remote host is for outbound calls.
I know what the fields are for.
Your link to the Asterisk github clearly tells you that it should work as I describe.
If the system was properly doing the SRV lookup, it should see these 4 addresses.
-
@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 -
@ing-joserivera26 said in VitalPBX 3:
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.
Nice try. That was before I spoke with the FreePBX developers about the subject. Try noting the date on that post.
-
@ing-joserivera26 said in VitalPBX 3:
@JaredBusch In that case you must put the host in the match field. I guess you must put: srv.skyetel.com
Skytel said in your blog:
SkyEtel
-
@ing-joserivera26 said in VitalPBX 3:
@JaredBusch In that case you must put the host in the match field. I guess you must put: srv.skyetel.com
Ou of date. That is from before the NA region even existed.
term.skyetel.com does not have SRV records.
srv.skyetel.com does not (or did not used to) have A records.
na.skyetel.com has both A records and SRV records. -
@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 Then, put na.skyetel.com on the match field. That's it
-
@ing-joserivera26 said in VitalPBX 3:
@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.
If it must be defined (which it must be), then VitalPBX should not accept it empty.
Or VitalPBX should automatically populate it behind the scenes with the host information as that is all that is known.
-
@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. -
@ing-joserivera26 said in VitalPBX 3:
@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.
Except the point of making a GUI is not to make your users understand Asterisk requirements. The GUI should "know" these things.
This is why FreePBX disables the username and secret fields if you say no auth.
It is also why it automatically populates the match with the host unless you manually go to "advanced" settings and override it.
Stop being a butt hurt asshole because someone said things about your precious toy that you don't like.
No one said VitalPBX is a crappy piece of shit that should never be considered.
-
@MontesVitalPBX said in VitalPBX 3:
@JaredBusch Hey, sorry I never got the email for this mention. We are looking into your post, but cannot find it. It appears that your account was not verified So that is why moderation was needed, but we weren't able to find your post. I have gone ahead and verified your account so you should be able to post once again. Now, it would be good if you can try again, so we can solve it, and continue running your issues on the VitalPBX forum so our support and dev team can take a look into it.
Moderated again..
-
@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.
-
@ing-joserivera26 said in VitalPBX 3:
I will not continue posting on your blog.
This is not my blog. This is an public community targeting IT professionals.
I would (and have) posted on the VitalPBX community, but it seems that i'm eternally moderated.
