After a painful couple of months, I’ve made the decision to switch phone service providers. I won’t go into details, but I’m working with a new provider now and attempting to use a test DID to ensure communication works before we port our numbers over.
I’m struggling getting the DID from their SIP trunk. I’ve reached out to them as well, but I thought you folks have seen a lot more than I have, and potentially them. I have another trunk with Voip.ms I used while configuring the system and testing things. The Voip.ms number seems to work just fine.
I’ve poked through Reports > Asterisk Logfiles, and watched the calls come in on both. With the new provider’s number, I just don’t see a DID coming through anywhere, just “s.” I’ve read to check the “To” header, which I’m not sure where to see that, but if I search the Asterisk Logfiles for the DID, it never appears. As a hail mary, I threw “from-pstn-toheader” into the trunk’s pjsip context, to no avail.
Any thoughts anyone? Is it possible this is just a provider misconfiguration issue? Or is there something on my end I should look for or check or reconfigure?
s is the value of Contact User. For many simple cases, this is what you set.
Otherwise you need to find out how they provide the DID to you. The To header is a common way of doing that, in which case there is an alternate initial context, named something like from-pstn-toheader, to handle that.
This should not be a difficult problem. At the Asterisk command prompt (not a shell prompt) type pjsip set logger on
and make a test call in. The Asterisk log will now include a SIP trace. Look at the incoming INVITE and report whether the DID appears anywhere. If so, you can set up a (possibly custom) context to fish it out from whereever.
If not, are you using registration or IP authentication? If IP auth, there is probably a per-DID setting on the provider’s portal that you can set to include the DID number. If registration, does the provider offer sub-accounts or similar? If so, you can put each DID into its own sub-account to distinguish them.
If none of the above are applicable, unless you have an NDA or simlar agreement with the provider, post details – someone reading this will likely know how to configure the trunk (or how to ask the provider to fix).
I think my provider is working on something at this point as I’m getting a busy signal at the test number now. And yes, 5555-ABCD represents an account number for the provider. Problem is the account number has no correlation to the DID, so trying to translate 150 sub accounts to 150 extensions wouldn’t be ideal.
And no, no NDA, but the problem is they are a small local provider in my area - Planet Networks. They’ve been super helpful with everything we’ve been going through. I just don’t want to use up all of the good-will.
On the trunk setup we’re using registration for outbound calls. But nothing for Inbound. We’re firewalling that to their list of server addresses. So I assume in this situation, it’s IP auth…
If you can specify your domain name or IP address on their portal, there should be an option to put a number before the @ in your SIP URI, which could be the DID number.
Digging this up as we’ve got it working. They had to make some tweaks on their end, and had me turn on “Trust RPID/PAI” and set “Send RPID/PAI” to Both. I assume these changes in conjunction with some changes they made on there end is what did the trick.
Thank you for those who pitched ideas and helped out. You helped keep me sane.