Is it possible to inject specific BYOC trunk metadata (like carrier ID or SIP header values) into the Bot API conversation context for our 15 AP-Southeast-1 trunks? The documentation at Genesys Docs does not explicitly support custom trunk attributes, and our current sentiment analysis pipeline requires this data to distinguish carrier-specific audio artifacts. We need a way to pass this from the SIP INVITE stage directly to the bot logic without modifying the carrier setup.