Hi, Stas!
I can't think of any way to overcome this. However, re-INVITEs and ACK
should be treated in the same manner, without too much processing.
My assumption is that you are doing some extra processing on re-INVITEs
which might delay its forward. Can you check that?
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 02/02/2017 10:31 PM, Stas Kobzar wrote:
Hello List,
My call flow has initial INVITE and re-INVITE to update RTP IP/port.
Usually everything works well, but sometimes OpenSIPS come up with
following example:
UA OpenSIPS PSTN GW
-------------------------------------------
INV(CSeq: 100) -----> | ---> INV(CSeq: 100)
<---- 200 OK | <--- 200 OK
(UA sends ACK then new INVITE)
ACK(CSeq: 100) -----> |
reINV(Cseq: 101) ---> |
(OpenSIPS relays first INVITE then ACK)
| ---> reINV(CSeq: 101)
| ---> ACK(CSeq: 100)
When PSTN gateway receives re-INVITE before ACK for previous INVITE
it responds 500 with Retry-After header.
This is correct behaviour which conforms to the RFC 3261 section 14.2
My question is:
Is it possible to assure order of received and relayed messages within
the same SIP session? Is there any configuration parameter?
Thank you,
--
Stas Kobzar
Developeur VoIP / VoIP Developer
Modulis.ca Inc.
# Bureau / Office: 514-284-2020 x 246
Email: s <http://firstname.lastname>[email protected]
https://www.modulis.com <https://www.modulis.com/>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
