is it possible to inject custom sip trunk identifiers into screen recording metadata via the api? we are seeing generic session ids in the analytics dashboard for our apac byoc trunks, making it impossible to correlate failed recordings with specific carrier failover events. need a way to tag these sessions programmatically before the recording action triggers.