The replies must mirror the complete original via stack as in request.
Otherwise, the proxy does not know where to forward the replies.
-jiri
ps -- Cisco IOS 12.3 includes lot of bug fixes. If this is actually
a Cisco bug, upgrading is the first step I would try.
At 09:17 PM 11/14/2003, Daniel Medina wrote:
The message dumps seem to indicate that the Cisco
gateway is sending,
as you say, messages to the proxy server with only one via header field
in it.
The messages are
SIP/2.0 183 Session Progress Via: SIP/2.0/UDP
SIP/2.0 100 Trying Via: SIP/2.0/UDP
Should ser be seeing these as errors? I thought they were part of the
RFC.
On Fri, Nov 14, 2003 at 03:23:51AM +0100, Jiri Kuthan wrote:
The logs
say
ERROR: forward_msg: no 2nd via found in reply
(repeated a few times)
Outside line
(Indicating that the caller actually passed)
route[2]:SIP-to-PSTN call routed
ERROR: reply cannot be parsed
Well, unless I see message dumps I assume that it happens what your
log tell: someone sends a reply to proxy server with only one via
header field in it, or other defect. (Other situatation when this may
happen is when SER acts as a UAC, like if it generates local CANCELs,
and replies come back after the transaction state is already gone.)
-jiri
--
Dan