Right, it's a problem with remote end-point.
I recommend you to fix it if possible. But to circumvent
the problem with sipXtapi, we can add some code to perform as if
SSRC changed if Seq suddenly changes. Patch is welcome.

On Wed, Feb 18, 2009 at 1:27 AM, Paulo Vicentini
<vicentini.pa...@gmail.com> wrote:
> For instance:
> got SIP 183....
> incoming RTPs :
> SSRC=0xE2B0C9A5, Seq=231, Time=36960
> SSRC=0xE2B0C9A5, Seq=232, Time=37120
> SIP/SDP Status: 200 OK, with session description
>  SSRC=0xE2B0C9A5, Seq=0, Time=0, Mark => audio processing fails
>  SSRC=0xE2B0C9A5, Seq=1, Time=160
>  SSRC=0xE2B0C9A5, Seq=2, Time=320
> remote endpoint keeps SSRC but reset Seq / Time
> b.r.
> Paulo
> On Tue, Feb 17, 2009 at 6:37 PM, Alexander Chemeris
> <alexander.cheme...@sipez.com> wrote:
>>
>> On Tue, Feb 17, 2009 at 11:47 PM, Paulo Vicentini
>> <vicentini.pa...@gmail.com> wrote:
>> > It seems that sipXtapi-3.2 is not RTP marker bit changes aware.
>> >
>> > For instance, after early media, if the proxy set RTP: 1... = Marker:
>> > True,
>> > audio processing will fail
>>
>> I'm not sure I completely understand you, but here is my shoot:
>>
>> Marker bit is only of an informative value, and implementation can
>> ignore it according to the standard. Also by the standard it is used
>> to indicate start of a talkspurt, not to split streams. So if stream
>> completely changes, this should be signaled with SSRC change.
>>
>>
>> --
>> Regards,
>> Alexander Chemeris.
>>
>> SIPez LLC.
>> SIP VoIP, IM and Presence Consulting
>> http://www.SIPez.com
>> tel: +1 (617) 273-4000
>
>
> _______________________________________________
> sipxtapi-dev mailing list
> sipxtapi-dev@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
>



-- 
Regards,
Alexander Chemeris.

SIPez LLC.
SIP VoIP, IM and Presence Consulting
http://www.SIPez.com
tel: +1 (617) 273-4000
_______________________________________________
sipxtapi-dev mailing list
sipxtapi-dev@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/

Reply via email to