Just trying out Thinq as a provider for the first time… Does anyone out here have Trunk configuration settings that work with them ?
I’ve tried various settings on my own but can’t seem to get it to work… Outbound and Inbound… not working at all… Thinq seems to work only with IP… no registrations… i’ve never done it that way before…
Tried this –
canreinvite=nonat
nat=yes
context=from-trunk
type=peer
disallow=all
allow=ulaw
; allow=g729 ; uncomment if you purchased g.729 from Digium
trustrpid=yes
sendrpid=yes
insecure=very
qualify=yes
Yes they offer SIP trunking… I was able to get the inbound working… I have a Trunk connected now… I had to lock down the firewall by IP and allow anonymous connections… Thinq is locked down by IP on their end also…
My Incoming settings are:
type=peer
context=from-pstn
insecure=very
Calls are coming in just fine… but can’t seem to dial out…
I am getting this error –
Got SIP response 484 “Address Incomplete”
That’s incoming, not outgoing. Two very different things.
Also, it looks like you are using Chan-SIP. I recommend this now, especially when the call could be coming from more than two or three IP addresses. You should transition to PJ-SIP and identify all of your incoming addresses that way.
If you are going to continue with Chan-SIP:
Should probably be “type=friend” to allow the settings to carry over to the Outbound settings.
That setting has been deprecated for about 10 years. As noted above, you should be using “port,invite”.
For testing purposes, stick with ulaw for now. It’s universally supported (in the US) and gets rid of one more variable.
Make sure all of your settings in the Advanced Settings tab for your SIP production are set up for this. You need to double-check the inbound router as well to ensure traffic is being forwarded correctly if you are, in fact, using NAT.
insecure=port,invite is often copied from cookbook examples even though insecure=port is not required in most of the cases it is used, and insecure=invite has also been replaced with a more modern version and that is remotesecret.
So if you use remotesecret instead of secret you achieve what the user probably wants and that is to not challenge incoming invites for authentication but provide the secret if challenged on outgoing invites.
Unless there’s another way to accept calls from a specific incoming IP without registrations… Thinq’s system works with destination IP and nothing else… I was not able to get the incoming to work any other way…
Pretty much every single trunk works this way, even the ones using registration. Inbound INVITE comes from recognizable IP, route call to specified context. You either create one chan_sip peer per signalling host, or a single pjsip trunk with all signalling hosts enumerated on the match line. Then white list the signalling hosts/ranges in firewall.
Opting not to read scroll back, so apologies if it’s been discussed. I’ve encountered a surprising number of people using non-registration trunks that don’t realize they must correctly match the signalling port on the provider end with the trunk port on the PBX. So if you create a PJSIP trunk, and the PJSIP signalling port is not 5060, you must specify that at the provider end.
Ok I am trying the PJSIP setup… however I get the “all circuits are busy” message when dialing out… how can I make sure PJSIP sends out in the format Thinq needs – ie: SIP/[email protected]
