On 2/22/21 9:09 AM, Sundbaum Per-Johan (Telenor Sverige AB) wrote:
Hi again !
Correction, there are of course not any "require: 100Rel" in INVITE, sorry I
mixed things up !
BR/pj
We have a vendor that is saying that they correctly answers initial INVITE with 400 BadRequest
because the INVITE have SIP header "supported: precondition" and also required:
100rel", but not the equivalent QOS parameters in SDP.
Personally I think that this behavior is definitely against the "spirit" of
SIP, but is it really in accordance with 3GPP 24.229 ?
I won't comment on 3gpp-specific aspects. But from a pure sip
perspective I see nothing wrong with declaring supported:precondition
but choosing not to negotiate any preconditions at that time. There is a
distinction between support and use.
Based on your stated facts, and assuming there was nothing else wrong,
IMO the UAS should have processed the incoming request.
If you post the full request then it should be possible to be more
definitive about this. (The link you posted below doesn't work for me.)
Thanks,
Paul
"The MSC sends 400 Bad Request because the received SIP Invite has precondition
in the header part but no precondition related attributes in the SDP part.
This behavior is according to Function Specification Session Initiation
Protocol, 1/155 17 FAY 112 172/9 Uen Rev. B And 3GPP 24.229.
2.21.1.1.1 INVITE Received with SDP
Offer<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcalstore.internal.ericsson.com%2Felex%3Fid%3D8956%26ORPA%3Dpreco%26SR%3DTOPIC%26FN%3D1_15517-FAY112172_11Uen.B.html%23TOP&data=04%7C01%7Cper-johan.sundbaum%40telenor.se%7C6f6fbf4500384237177208d8d7005097%7C1676489c5c7246b7ba639ab90c4aad44%7C1%7C0%7C637495743640289713%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3WtMUlx80DjAupu6sjxlK4Sh0TsONPiVGPna2h3clnc%3D&reserved=0>
When MSC-S receives initial INVITE with SDP offer containing precondition related
attributes within SDP body, it requires both precondition and 100rel to be present
in Require or Supported header. MSC-S behavior is the same regardless if
precondition tag is received in Require or Supported header. If any of the required
option-tags is missing, INVITE is rejected wit 421 Extension Required and the
missing option-tags within Require header. If the received SDP offer contains no
precondition related attributes, but both precondition and 100relare present in
Require or Supported header, INVITE is rejected with 400 Bad Request."
BR/pj
Sensitivity: Internal
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
