4 May
2005
4 May
'05
1:28 p.m.
Hi Zeus!
Zeus Ng schrieb:
First, the ACK should follow section 12.2 (indeed
12.2.1.1), Requests within
a Dialog, not section 12.1.2 according to section 13.2.2.4, 2xx Responses.
------
The UAC core MUST generate an ACK request for each 2xx received from
the transaction layer. The header fields of the ACK are constructed
in the same way as for any request sent within a dialog
------
I disagee: the SER is an UAS not an UAC.
IMHO, the concernig chapters are 16.6 subpoint 8 ("16.6 Request
Forwarding"; "8. Add a Via header field value") and 8.1.1.7 ("8.1.1.7
Via"). Both chapters state the UAS (SER) MUST add a Via with a branch
parameter starting with the magic cookie "z9hG4bK".
The ACK generated by the UAC looks good to me, anyway.
Second, do you happened to have a line like this in
your SER config.
aliase=your_proxy_name:5080 or aliase=your_proxy_ip:5080?
Are you sure about the trailing 'e' in "aliase"? I've two
alias-definitions (one for the IP, one for the realm) in my ser.cfg. But
they don't have the port added. I've already added the ports in the
listen statements.
Alex Mack