Just going to drop this here because it was such a weird problem others might might come across it too. We found that if if a T-Mobile cell phone dialed into our Fusion platform and we returned a 200 OK with a P-Asserted-Identity = 1000@domain.com, then T-Mobile would not send us any audio. It would work and audio would flow both directions if the extension was something else like extension 2200, but not 1000. The only thing I can figure is that they have added some kind of spam filter. The funny thing is that T-Mobile even told us it was the PAI, but I didn't believe them for an entire day. I thought it was ridiculous to say audio issues were caused by the PAI header! Little did I know.
Here's the fix for those of you that might run into this.
Here's the fix for those of you that might run into this.
Code:
<extension name="pstn_callee_number" continue="true" uuid="39f1a610-d895-4a5f-8766-a2d5c6650c82">
<condition field="${call_direction}" expression="^inbound$">
<action application="set" data="callee_id_number=${caller_destination}"/>
</condition>
</extension>