Move ai-voice-runtime-service host port off 9019 to avoid cross-tenant conflict

A separate deployment on the same host (aimaq-call-center) already binds
127.0.0.1:9019, so this project's ai-voice-runtime-service could never
start there. Remap the host side to 9024 and point Asterisk's
AudioSocket target at the new port; the container still listens on 9019
internally.

deployment/asterisk/extensions.conf

@@ -5,7 +5,7 @@ MVPCC_IVR_QUEUE_CODE=voice_lab_ivr
 MVPCC_IVR_FALLBACK_QUEUE_CODE=voice_lab
 MVPCC_MONITOR_DIR=/var/spool/asterisk/monitor/mvpcc
 MVPCC_HUMAN_DIAL_TARGETS=PJSIP/2001&PJSIP/2002
-MVPCC_AI_AUDIOSOCKET_SERVICE=127.0.0.1:9019
+MVPCC_AI_AUDIOSOCKET_SERVICE=127.0.0.1:9024
 MVPCC_IVR_FASTAGI_HOSTPORT=127.0.0.1:4573
 
 [from-softphones]

deployment/docker-compose.server.registry.yml

@@ -160,7 +160,7 @@ services:
       <<: *app_env
       APP_MODULE: services.ai_voice_runtime_service.app:app
     ports:
-      - "9019:9019"
+      - "9024:9019"
 
   webchat-adapter-service:
     <<: *service_defaults

deployment/docker-compose.server.yml

@@ -162,7 +162,7 @@ services:
       <<: *app_env
       APP_MODULE: services.ai_voice_runtime_service.app:app
     ports:
-      - "9019:9019"
+      - "9024:9019"
 
   webchat-adapter-service:
     <<: *service_defaults