[reSIProcate] strict routing?

[Christian_Gavin@xxxxxxxxxxxx]

I have a question regarding strict routing. SUBSCRIBE is required to have a
route: field in the header (otherwise, SER rejects it).

With respect to RFC 3261, the request-line destination URI will be moved to
the end of the route list and the first item of the route list will become
the request-line destination URI (this happens in
Helper::processStrictRoute).

So a SUBSCRIBE might be:

SUBSCRIBE sip:some.server.com SIP/2.0
...
To: <sip:user_to_subscribe@xxxxxxxxxxxxxxx>
From: <sip:some_subscriber@xxxxxxxxxxxxxxxxxxxxx>
...
Route: <sip:user_to_subscribe@xxxxxxxxxxxxxxx>

I tried the presSvr application and it just compares the request-line URI
to the list of AOR it has in its table. This then fails with a 404 NOT
FOUND because the request-line URI is not the SIP URI to subscribe to. I
quickly commented out the strict routing and verified SUBSCRIBE then worked
fine. My client is a modified version of basicRegister with a SUBSCRIBE
sent to the server.

According to the standards, shouldn't presSvr also consider the route: in
the message (yeah, I know it is a simple test application) ?

Thanks,
Christian