There is actually a setting to force new SSRC in a condition like that.

Internally it's called RTP_BUG_CHANGE_SSRC_ON_MARKER. If I remember correctly it should be set in the sofia profile config:

<param name="auto-rtp-bugs" data="CHANGE_SSRC_ON_MARKER"/>

Try that out and see if it helps.

/Peter


2014-03-28 11:37 GMT+01:00 Richard Brady <rnbrady@gmail.com>:
Hi Anthony and team

I have a situation where the timestamp in a RTP stream generated by FS jumps backwards. Version 1.2.22.

It seems the cause of this is that media from the A leg starts late. So in the meantime we start generating media on the B leg with our own timestamp. 

Then media starts arriving on the A leg so we relay it and we start using that timestamp instead of our own. 

FS sets the marker bit when this happens but I'm not sure this makes it OK to turn back the timestamp. I think we should actually be using a new SSRC. 

Any thoughts? (happy to raise a Jira ticket and verify in master).

Richard


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org