Re: [OpenSIPStack] incoming routes

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

> {quote:title=illizit wrote:}{quote}
> Is there a specific reason why it works like this?
> 

RFC 3261 
10.3 Processing REGISTER Requests

5. The registrar extracts the address-of-record from the To header
         field of the request.  If the address-of-record is not valid
         for the domain in the Request-URI, the registrar MUST send a
         404 (Not Found) response and skip the remaining steps.  The URI
         MUST then be converted to a canonical form.  To do that, all
         URI parameters MUST be removed (including the user-param), and
         any escaped characters MUST be converted to their unescaped
         form.  The result serves as an index into the list of bindings

I simply mean your provider is not sending the correct AOR it got from the REGISTER request.   And that correct AOR processing is vital for OSBC SIP Trunking operation.

> If not, do you know which part of the code this sip trunking is in so I can modify it? According to this website, the from tag in a sip packet should say where the call originated from and the to tag should be the uri of where it is going. 
> 
> 

See:

B2BUAConnection * SBCSIPTrunkEndPoint::OnCreateB2BUA(
  const SIPMessage & request,
  const OString & sessionId,
  B2BUACall * /*call*/
)

Feel free to send in patches.