[reSIProcate] handling an INVITE with no/incorrect port in the request-uri

["Justin Matthews" <jmatthewsr@xxxxxxxxx>]

Hello,
        I am looking for some advice on handling the following situation:
my resip/dum app is set to listen on some port other than 5060 and receives
an INVITE with a request-uri that does not designate the port (ie user@host
instead of user@host:port), yet the packet is sent to the proper port.
Because the packet is sent to the proper port the message propagates
successfully through resip/dum.  The local contact in the dialog is set to
the request-uri (with no port), so when I send back a 200, the contact does
not contain the port and the ACK is sent to 5060 instead of my listening
port.

This occurs on a cisco 7960 (6-03 && 7-04 firmware tested) and because there
are a number of users with that firmware, I am inclined to silently fix this
issue instead of sending back a 404.

I was thinking of using onReadyToSend to modify the contents of any
responses for this particular scenario.  

Is there any other way, for example to set the contact using AppDialog, to
fix it outright?

Thanks,

-Justin