Ranjit,
Based on the further detail you provide below I conclude that this is
most likely a question about 3GPP IMS behavior and specifications. I
suggest that you take this to a 3GPP forum. (I don't know what that
would be. Hopefully one of the people here who are involved in 3GPP can
make
to:schoenin...@gmail.com>,
"mailto:Sip-implementors@lists.cs.columbia.edu;
<mailto:Sip-implementors@lists.cs.columbia.edu>, Christer Holmberg
<mailto:christer.holmb...@ericsson.com>, "mailto:pkyzi...@alum.mit.edu;
<mailto:pkyzi...@alum.mit.edu>
Subject: Re: [Sip-implemen
a.edu"
, Christer Holmberg
, "pkyzi...@alum.mit.edu"
Subject: Re: [Sip-implementors] Fwd: ue-addr parameter in SIP Contact header
Hi Philip
Yes, I agree that connection and relation to UE are maintained by P-CSCF and
S-CSCF does not need them. But in some call scenarios,
;
> *From: *Ranjit Avasarala
> *Date: *Monday, 7 October 2019 at 6.42
> *To: *Philipp Schöning , "
> Sip-implementors@lists.cs.columbia.edu" <
> Sip-implementors@lists.cs.columbia.edu>, Christer Holmberg <
> christer.holmb...@ericsson.com>, "pkyzi.
Hi Philip
Yes, I agree that connection and relation to UE are maintained by P-CSCF
and S-CSCF does not need them. But in some call scenarios, the S-CSCF
connects to subsequent network elements like MRF and it is supposed to pass
the "ue-addr" parameter it receives from P-CSCF (in Contact header)
Hi Ranjit,
I can't answer the question, but I have another question:
Isn't the connection and relation to the UE maintained by the P-CSCF?
>From my perspective the S-CSCF does not have any relation to the UE.
BR
Philipp
___
Sip-implementors mailing
Hello SIP experts
I have a scenario where, the S-CSCF is ignoring
ue-addr=x.y.z.a;transport=udp parameter in INVITE request. Ignoring in the
sense that it is not adding the "ue-addr" parameter in the INVITE it
forwards to next hop
but in another scenario, when the "ue-addr" is of the format
