Dear All,
I am experiencing a problem with the Sofia SIP stack with early media.
Here the flow:
A (Sofia) Proxy B
|-----------INVITE----------->| |
| |----- INVITE ---------->|
| | |
| |<------ 100 ------------|
|<-----------100--------------| |
| | |
|<-----------183--------------| |
| (Media Source Proxy) | |
|<===========RTP=============>| |
| |<------ 200 ------------|
|<-----------200--------------| |
| (Media Source B) | |
|<===========================RTP=======================|
| | |
|------------ACK------------->| |
| |------- ACK ----------->|
| | |
During the call setup, the Proxy sends early media so tones (ringback) is
generated by the proxy. When the endpoint B answers the call, the SDP in
the 200OK contains media description for the endpoint B. The RTP
Problem: The stack seems to assume that the SDP payload received from a
183 would be the same as the one received with the 200OK. Thereof, the
stack ignore reporting the SDP from the 200OK and doesn't intialize the
SDP structure pointer when the stack has previsously received SDP as part
of the 183. The application cannot retrieve the SDP information to update
the RTP stream direction which cause one-way audio.
Question: How can we force the stack to populate the NUA SDP structure
members in that case? Any idea would be welcomed...
Regards,
Louis Guindon
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
