RFC 3608: Simply put, the registrar generates a service route for the registering UA and returns it in the response to each successful REGISTER request. This service route has the form of a Route header field that the registering UA may use to send requests through the service proxy selected by the registrar. The UA would use this route by inserting it as a preloaded Route header field in requests originated by the UA intended for routing through the service proxy Does that clarify the things? Regards ----- Original Message ----- From: "Benny Prijono" <bennylp@xxxxxxxxx> To: "pjsip embedded/DSP SIP discussion" <pjsip at lists.pjsip.org> Sent: Tuesday, October 30, 2007 6:16 PM Subject: Re: [pjsip] Service-route overriding proxy > Roland Klabunde wrote: >> Hi Benny, >> >> Hmm. Not sure. My montiorings: >> >> 1) No specification of service-route in config >> * Register OK, server returns service route pointing to scscf:6060 >> * Invite is blocked by the registrar with error "Bad request - not >> following >> indicated service route". The request has been sent to pcscf:5060 >> >> 2) Specification of service-route in config >> * Register as above >> * Invite is now sent to scscf:6060 (as specified in service route). This >> ends up in no response. >> >> Shouldn't the Ua send the Invite to pcscf:5060, providing the received >> service route somewhere in the INVITE header in order to let the pcscf >> know, >> where to route the request? > > > Frankly I'm not sure. I thought that if PCSCF wants to stay in the > path of subsequent requests, it should have been added in the S-R > list by the registrar. That's what I concluded from (briefly) > looking at the examples in RFC 3608. Or is this a wrong interpretation? > > -benny > >> As far as I can remember there was no ;lr in the service route. What >> would >> that change (besides the fact that I can't control the IMS platform)? >> >> Regards > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
