Thanks, Paul for the detailed response, it more or less matches my own
understanding. Do you think for the sake of implementation it can be
compressed down to something like that:
- if you are making SIP RESPONSE to an incoming request use "Server",
otherwise if generating new REQUEST use "User-Ag
Have you seen RFC3326? It might be just what you are looking for and I
know at least a few implementations that support it to various extent.
-Max
On Tue, Apr 28, 2020 at 2:01 PM Ranjit Avasarala
wrote:
> Hi SIP Experts
>
> there are numerous scenarios where a SIP server would respond with 500
Hi SIP Experts
there are numerous scenarios where a SIP server would respond with 500
Internal Server Error response. Troubleshooting the 500 error is not easy
due to the lack of any reason in the response though some servers do append
Reason header. e.g.
500 Internal Server Error
...
Hi Paul, Maxim
I agree with both and from the implementations i have seen so far, I see
User-Agent header being inserted by UE devices like smartphones : e.g.
User-Agent: LG IMS client: 6.0 and Server header is inserted by the
intermediate servers like CSCF, AS, MRF, etc: E.g. Server: CSCF
On 4/28/20 1:08 PM, Maxim Sobolev wrote:
Hi,
I've noticed that in the last few years few implementations have gained
popularity who use User-Agent in both requests and responses. Instead of
User-Agent in requests and Server in responses which I always believed
(perhaps incorrectly) to be the rig
Hi,
I've noticed that in the last few years few implementations have gained
popularity who use User-Agent in both requests and responses. Instead of
User-Agent in requests and Server in responses which I always believed
(perhaps incorrectly) to be the right way of doing it. The argument there
is t
