Oure current provider vant that we send a INVITE with a prefix but that prefix should not be part of the To: header
provider request that we add a prefix “03” to INVITE, but I cant find any options to set INVITE to something else
like this PREFIX=03
INVITE sip:email@example.com;user=phone SIP/2.0
have tried to use these, with no luck
So, is it possible to setup an outbound trunk and route so that you can call ZipDX using it’s URI on a System with only PJSIP. I had done it previously by setting up a custom trunk using SIP/$OUTNUMfirstname.lastname@example.org, and a route that calls the...
My understanding is that chan_pjsip only supports the standards recommended method of setting To: and the request URI to the same value, when originating a call.
As you can see, from
rfc3261 your ITSP is requiring you to violate a SHOULD level requirement of the SIP RFC, so they cannot expect their service to work with an arbitrary SIP client.
Indeed, there is no ability that I can think of currently to set them differently.
Thanks for the quick answer
I will contact our TSP and tell the to provide documentation to where in the RFC that state INVITE and To is allowed to differ
as according to rfc3261 it violate a SHOULD level requirement
"The initial Request-URI of the message SHOULD be set to the value of the URI in the To field. "
“The URI in the To field of the request MUST be set to the remote URI from the dialog state.”
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.