Hi, I am working on a product to implement RFC 5626. I have a question regarding with "4.3. Sending Non-REGISTER Requests, rfc 5626".
The UAC performs normal DNS resolution on the next hop URI (as described in [RFC3263]) to find a protocol, IP address, and port. For protocols that don't use TLS, if the UAC has an existing flow to this IP address, and port with the correct protocol, then the UAC MUST use the existing connection. For TLS protocols, there MUST also be a match between the host production in the next hop and one of the URIs contained in the subjectAltName in the peer certificate. If the UAC cannot use one of the existing flows, then it SHOULD form a new flow by sending a datagram or opening a new connection to the next hop, as appropriate for the transport protocol. In case the User Agent is in middle of a Call and going to send in-dialog request, and meanwhile the User Agent detects the existing flow is broken, and then according to upper statement, the UAC should form a new flow to send this in-dialog request. Of cause edge proxy is able to forward this request to peer, but what will happen if peer will send in-dialog request back to this User Agent later? Then edge proxy will reject this request from peer because the flow token in top route is pointing to crashed flow. Did I miss something? Otherwise under this situation only one User Agent can send in-dialog request to peer, but peer is not able to send in-dialog request back? Thanks a lot! _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
