wait_until_answered: true 2025-08-17 213636,636 - INFO livekit.agents - received job request {"job_id": "AJ_uRV9wAHZ8wKF", "dispatch_id": "", "room_name": "outbound-cmc5319nr0004syrkp6nxvmyk-1755455794", "agent_name": "", "resuming": false} 2025-08-17 213636,908 - INFO livekit.agents - initializing process {"pid": 70847} 2025-08-17 213637,063 - ERROR livekit.agents - Error creating SIP participant: TwirpError(code=unavailable, message=twirp error unknown: unexpected status from INVITE response: sip status: 503 (SERVICE_UNAVAILABLE), status=503, metadata={'error_details': 'CA4STXVuZXhwZWN0ZWQgc3RhdHVzIGZyb20gSU5WSVRFIHJlc3BvbnNlOiBzaXAgc3RhdHVzOiA1MDMgKFNFUlZJQ0VfVU5BVkFJTEFCTEUpGiwKJXR5cGUuZ29vZ2xlYXBpcy5jb20vbGl2ZWtpdC5TSVBTdGF0dXMSAwj3Aw==', 'sip_status': 'SIP_STATUS_SERVICE_UNAVAILABLE', 'sip_status_code': '503'}) 2025-08-17 213637,065 - ERROR livekit.agents - Error details: Traceback (most recent call last): File "/Users/macos/Desktop/Z/server/fastapi_app.py", line 246, in make_outbound_call participant = await livekit_api.sip.create_sip_participant(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/macos/Desktop/Z/server/venv/lib/python3.11/site-packages/livekit/api/sip_service.py", line 416, in create_sip_participant return await self._client.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/macos/Desktop/Z/server/venv/lib/python3.11/site-packages/livekit/api/twirp_client.py", line 129, in request raise TwirpError( livekit.api.twirp_client.TwirpError: TwirpError(code=unavailable, message=twirp error unknown: unexpected status from INVITE response: sip status: 503 (SERVICE_UNAVAILABLE), status=503, metadata={'error_details': 'CA4STXVuZXhwZWN0ZWQgc3RhdHVzIGZyb20gSU5WSVRFIHJlc3BvbnNlOiBzaXAgc3RhdHVzOiA1MDMgKFNFUlZJQ0VfVU5BVkFJTEFCTEUpGiwKJXR5cGUuZ29vZ2xlYXBpcy5jb20vbGl2ZWtpdC5TSVBTdGF0dXMSAwj3Aw==', 'sip_status': 'SIP_STATUS_SERVICE_UNAVAILABLE', 'sip_status_code': '503'}) 2025-08-17 213637,065 - ERROR livekit.agents - SIP 503 SERVICE_UNAVAILABLE error. This could be due to: 2025-08-17 213637,065 - ERROR livekit.agents - 1. The destination phone number format is not supported 2025-08-17 213637,065 - ERROR livekit.agents - 2. The SIP trunk is not properly configured for outbound calls 2025-08-17 213637,065 - ERROR livekit.agents - 3. The SIP provider is experiencing issues 2025-08-17 213637,065 - ERROR livekit.agents - 4. The destination phone number is not reachable 2025-08-17 213637,066 - ERROR livekit.agents - Full error message: TwirpError(code=unavailable, message=twirp error unknown: unexpected status from INVITE response: sip status: 503 (SERVICE_UNAVAILABLE), status=503, metadata={'error_details': 'CA4STXVuZXhwZWN0ZWQgc3RhdHVzIGZyb20gSU5WSVRFIHJlc3BvbnNlOiBzaXAgc3RhdHVzOiA1MDMgKFNFUlZJQ0VfVU5BVkFJTEFCTEUpGiwKJXR5cGUuZ29vZ2xlYXBpcy5jb20vbGl2ZWtpdC5TSVBTdGF0dXMSAwj3Aw==', 'sip_status': 'SIP_STATUS_SERVICE_UNAVAILABLE', 'sip_status_code': '503'}) 2025-08-17 213637,066 - ERROR asyncio - Unclosed client session client_session: <aiohttp.client.ClientSession object at 0x11b53dd50> 2025-08-17 213637,066 - ERROR asyncio - Unclosed connector connections: ['deque([(<aiohttp.client_proto.ResponseHandler object at 0x11b577850>, 217843.001722501)])'] connector: <aiohttp.connector.TCPConnector object at 0x11b476c50>

Thanks for reaching out, CIAOBENGA. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

non of this is working

Hey there! If the first steps didn’t quite fix that SIP 503 SERVICE_UNAVAILABLE error, no worries—here are some more things we can try together: 1. Network Connectivity: Let’s make sure your NAT traversal is set up correctly and that your network is open to the right ports: ◦ SIP signaling: Port 5060 (UDP/TCP) or 5061 (TLS) ◦ RTP media: Port range 10000-20000 (UDP) 1. Authentication: It’s a good idea to double-check your API credentials and SIP trunk setup to rule out any sign-in hiccups. 2. Trunk Configuration: Make sure the trunk ID points to a trunk that’s actually there and reachable, and that the destination number is valid and active. 3. Provider-Specific Issues: Sometimes the provider might be the key—reach out to your SIP trunking provider to confirm: ◦ Their service is up and running smoothly ◦ Your account is all good on their end ◦ No configuration glitches on their side ◦ Your trunk has the right permissions for the calls you’re trying to make If you’ve tried all this and it’s still not working, just let me know—I’m here to help or can get someone else involved to sort it out with you. Sources: SIP troubleshooting guide | LiveKit Docs | SIP Integration | livekit/livekit_composite | DeepWiki