<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/60bc9429a18246a8b12bb00204f87eb3&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/60bc9429a18246a8b12bb00204f87eb3-b247a3ef6f228295.gif</thumbnail_url><duration>1411.033333</duration><title>The Phone Infrastructure Behind Voice AI</title><description>This Loom explains why reliable phone infrastructure is essential for Voice AI to work correctly. It covers how calls often route through PBX, IVR menus, call queues, and forwarding rules, and how misconfiguration can cause loops, dropped calls, or bypassing the AI. It distinguishes VoIP phone systems and PBXs from infrastructure platforms like Twilio and Telnyx, and recommends ensuring correct SIP trunking, webhooks, and routing so calls reach the agent reliably. It also outlines converting existing numbers to VoIP via porting, noting porting can take 7 to 14 business days, and advises keeping the existing line active until the port completes.</description></oembed>