[Serdev] API question

[Jiri Kuthan]

At 12:59 AM 8/25/2004, Andrew Mee wrote:
>I sent a message yesterday regarding this with full logs, but it is awaiting moderator approval :(

please try not to make your postings big. There are many people subscribed to the
mailing list and we are intersted in keeping the message volume reasonable for
them. If you have bulk attachements, put them on the web. The threshold is 40k.

>In these logs it proves the point (I think) that the ACK uses the wrong info.
>The UA tells the Proxy/Other end to contact at a specific port, but it actually contacts on the other port....
>
>I'll fwd it to you directly.
>
>I actually have 3 issues :)
>
>1. ACK being sent to the incorrect port
>2. is MS RTC using strict routing means that SER does not fwd the Message to the other end but back to itself
>3. (while related to 2) is that while trying to create a patch in SER to fix MS RTC messages I found that I had trouble with parsing the headers and the resultant output gets malformed. And I get to learn a little of the code at the same time as I have a few long-term ideas :)

Well, I think the headache is in unique combination of obsoleted RFC2543
strict-routing with use of maddr in Messenger. SER does not handle it
approprietly, and I am not sure if it can and at what cost.

-jiri