7 Commits (master)

Author	SHA1	Message	Date
Donat Zenichev	5bb04271c1	MT#62859 AmB2BSession::acceptPendingInviteB2B use local conn/port ... Don't re-exploit the connection information and port (taken from the coming SDP offer) for creation of faked SDP answer (200OK). This is confusing and can break things in rtpengine monologues handling. Better to create fake SDP answer based on already learned local SDP port and entirely connection information. Change-Id: Id71453022fd6c93f6743f1046588447b52c38c07	11 months ago
Donat Zenichev	3b94b6d14b	MT#59962 Aling the AmOfferAnswer model ... Make the AmOfferAnswer model actual and introduce according class API updates. Accordingly update CallLeg, SBCCallLeg and AmSipDialog. Change-Id: Iab26f4a7577af56df68ffe693859eaac08913b7f	11 months ago
Donat Zenichev	ede52ab0b3	MT#61912 OA: save the established body when it's generated ... When OA generates own SDP body (e.g. case with accepted invite in DSP), save it as established_body for this leg, in order to be able to re-invite this leg later. It can happen there is still no SDP seen from the callee side (other side), and in case we want to send established re-invite towards this leg, this will fail, since no SDP body seen yet. Change-Id: Ifd9f0fb70d27deac871de4eed1648f7c152813f3	1 year ago
Donat Zenichev	129b407bfb	MT#61574 AmOfferAnswer: don't generate SDP answer if offer empty ... When replying with 200OK generated by SEMS to INVITE requests, which have no SDP body included, just answer with empty 200OK. This sets the `OAState` of the call leg to `OA_None`. Change-Id: Ic28e80d670ba4ce98be6abac9d17689688f99f71	2 years ago
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
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	4 years ago
Victor Seva	ff47897962	Imported Upstream version 1.6.0~20140516~eaa616	12 years ago