[sip-comm-dev] invite processing uses To: header instead of RequestURI


#1

Developers,

Currently, an incoming invite is processed using the To: header, but it should
use the RequestURI.

Proxies can contain many aliases for a user, but the proxy will always re-write the requestURI to match the contact of the REGISTER message.

-steve

diff.txt (846 Bytes)


#2

Hello again Steve,

Nice catch again. Will fix it.

Thanks
Emil

Developers,

Currently, an incoming invite is processed using the To: header, but it should
use the RequestURI.

Proxies can contain many aliases for a user, but the proxy will
always re-write the requestURI to match the contact of the REGISTER
message.

-steve

Cheers
Emil

http://www.emcho.com

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hello Steve,

Fixed!!

Thanks again
Emil

Developers,

Currently, an incoming invite is processed using the To: header, but it should
use the RequestURI.

Proxies can contain many aliases for a user, but the proxy will
always re-write the requestURI to match the contact of the REGISTER
message.

-steve

http://www.emcho.com

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net