My provider is saying that the contact header needs to have 8032893046 in it instead of the “s” that it has in it today. I did some research, and I found that this can be solved by putting an extension in the register string. When I do that however, the registration to the provider starts failing. Is there any other way to do it?
Assuming a chan_sip trunk, if you change the Register String from 8032893046:[email protected]
to 8032893046:[email protected]/8032893046
the only thing that should change is the Contact header. You can confirm this with your SIP trace.
If changing only the Contact header causes the registration to fail, IMO that’s a provider issue and you should work it out with them.
Alternatively, what goes wrong when you leave the ‘s’? If incoming calls reach your system, you should be able to change the trunk context to from-pstn-toheader and have your incoming routes work properly.
So basically, what it boiled down to. The password that was supplied to me by the provider had an @ sign in it, and I think the @ sign confused the registration process. Once we changed it to a different special character, we’ve got past that particular issue. In other words, you were right, provider issue.