On Fri, Nov 22, 2013 at 00:27:29, Thomas Titty wrote: > Subject: RE: SIP OPTIONS not forwarded at Bono > > Thanks a lot Matt. I had made the two domain names same. Now I > reverted the deployment name to example.com and SIP OPTIONS are > forwarded between the SIP clients.
Great news! > Now, I am able to make the SIP INVITE reach the application server, > but the INVITE request back from the AS is rejected at bono due to > > " 22-11-2013 00:15:43.364 Warning stateful_proxy.cpp:1186: Rejecting > request from untrusted source" and SIP/2.0 403 Forbidden. Bono and sprout expose SIP on multiple ports. Bono exposes two ports: 5060 (untrusted) and 5058 (trusted). Sprout exposes one port: 5054 (trusted). >From the logs you attached, it looks as though the AS is receiving the request >from sprout but sending it back to bono on port 5060. Port 5060 is untrusted >and so expects flows to be authenticated - REGISTERs are challenged but other >SIP methods are simply rejected. When sprout send the INVITE to the AS, it should have included a Route header specifying that the INVITE should be routed back to sprout. The sprout logs would show whether or not this is the case. If the AS is continuing processing on the original call, it should use this Route header. (The Route header also includes an Original Dialog Identifier (ODI) token that allows sprout to correlate the incoming INVITE from the AS back to the INVITE it sent out to the AS.) Alternatively, the AS might want to set up independent calls. For example, a conference server outdial might operate like this. In this case, the AS should send directly to sprout port 5054. Please can you check the Route headers sprout sent to the AS and the logic the AS uses to build the Route headers on the INVITE it sends back? As above, the sprout logs will show the Route headers sent out to the AS. Please let me know how you get on. Thanks, Matt _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
