Hello,

From: Martin Koenig [toplink-plannet GmbH] Sent: Wednesday, September 08,

...

this is not an SER problem. Loose routing is basically done

in the end

...

devices. All you can control on the server is whether the

server should be

...

in the signalling proxy chain (record_route()) and whether

you want to

...

process route-header-fields (loose_route()) or forward to the final destinanation directly (t_relay() without loose_route()).

Sorry, this is not correct. The routing mechanism (loose or strict) has to be followed by SIP proxies. Look at RFC 3261 para 16.6 step 6 where the strict routing behavior is defined: "If the copy contains a Route header field, the proxy MUST inspect the URI in its first value. If that URI does not contain an lr parameter, the proxy MUST ..."

The UA has to issue the message that is initiated, right? So the UA is issuing a request that is

BYE enduser@finaldestination Route proxy1, proxy2, proxy3

This is so because the UA will most likely be build upon 3261 and not the prior versions. One cannot change this behaviour in ser, you will always get a request that has the final destination as Request-URI.

Regards, Martin