Hi,
> The URI is not used for matching in 3261.
Concerning responses, neither is Call-ID, To, From, or number within CSeq.
> So, in order to have better interoperability, you
> should limit to matching the fields identified by 3261.
In my opinion, the matching fields mentioned within RFC 3261
Chaudhuri
Sent: Friday, June 19, 2015 5:25 AM
To: Sip-implementors
Subject: [Sip-implementors] From Header value is getting changed from 100
trying to 200OK
Hi, I just need clarification is the below mentioned scenario will work
properly
UAC1 sending INVITE request to UAS1
Hi,
The UAS is noncompliant to RFC 3261 (and RFC 4916).
RFC 3261 section 8.2.6.2 requires that the response's To/From URI equal
request's To/From URI.
> So is UAC1 send ACK for this? Or UAC1 ignore
> that 200OK due to the change in From header value?
The UAC can basically act however it wants.
Hi, I just need clarification is the below mentioned scenario will work
properly
UAC1 sending INVITE request to UAS1
--
From: "+351964901478" ;tag=AUA401YVCeghCjaA
UAS1 is responding 100 Truing for that INVITE to UAC1
---