8 Commits (793bb59d2d40da9fe506de14112a0bb41b60098b)

Author	SHA1	Message	Date
Donat Zenichev	84a0c3e84f	MT#57256 Do not change OA state of similar 183 SDP ... We don't have to change the SDP OA state, in case the 183 response has exactly the same SDP content (same SDP session version) as we already have seen before in previous 183 message. Change-Id: Ica008104c31e979cdcb352cefea39db4d1ff3c56	3 years ago
Donat Zenichev	ab7c1851fd	MT#56321 core::AmOfferAnswer add logging into most important places ... We have to improve AmOfferAnswer functions in terms of adding more logging, to let the debug of the OA be more clear. Also in parallel the refactoring is done in scope of AmOfferAnswer in order to make reading more convenient. Change-Id: If7353f1285057760dd5fbeada984a5ef96af9854	3 years ago
Donat Zenichev	60e16ed526	MT#56321 AmOfferAnswer: Re-use existing SDP for 183 with no body ... Re-use existing local sdp, in case there is a sequential 183 coming, but it has no SDP. This will fix the cases, when: - first 183 has been sent, and provided to the system the SDP - second/third etc. 183 is coming, but has no SDP body To not confuse the recipient (end subscriber) of these 183, the media description in the scenario with 183 having no SDP body, mustn't be changed (session id, media and attributes). Previously the behavior was to generate local SDP with a new session id and add sems-b2b into the media processing by that (new media port, codecs and other attributes). However, this change doesn't have an influence on very first 183 sent with no SDP body, because there was essentially no local SDP saved before. So in this situation behavior is not changed. Change-Id: I53dd57ae8a4739d5356d94fff45fb290896fd777	3 years ago
Donat Zenichev	d11c7486d0	MT#56321 core::AmOfferAnswer - refactor onReplyOut() ... Because of messy organizing of the code in the function, it's not possible to read that and work with that. Change-Id: I4a56000a6f33051f9267048dcb620fb1a4eba7c6	3 years ago
Marco Capetta	d45dcf1ecf	MT#55831 Fix issue if an UPDATE is received after 183 ... If an SDP UPDATE is received after the 183, but before the 200, SEMS fails when it receive the final ACK. In fact SEMS tries to find the SDP content inside the ACK message itself. The solution is copied from sems-pbx module where the issue doesn't happen. (real ticket number: TT#43503) Change-Id: I5a432dc57c701d7eb0d5306d6005508e3310e7ba	3 years ago
Jozef Kenyeres	534be90e08	MT#55831 fix failed relay of 200OK without SDP ... fix failed relay of 200OK without SDP (real ticket number: TT#9521) Change-Id: I8932962961af364dab1df360afc4b02459d65ac0	3 years ago
Victor Seva	2bf464e5cb	Imported Upstream version 1.6.0~20150612~a2d214df36	11 years ago
Victor Seva	df9992620d	Imported Upstream version 1.6.0~20140516~eaa616	12 years ago