- Порезанный
- 27 апреля 2026 г. в 05:26 UTC
- Автор
- Kamo
- Обещать
- 379c783
The /api/voip/** catch-all in APIGatewayController was shadowing the dedicated VoipRecordingUploadController POST /api/voip/recordings/upload mapping when Spring resolved cross-controller request mappings. Requests from kamo-asterisk-support were silently being proxied to VOIPService (which has no recording-upload endpoint) and coming back as 401/404. Add an explicit /api/voip/recordings/** carve-out next to the existing /api/voip/webhook and /api/voip/oauth/callback ones. The dedicated POST /api/voip/recordings/upload mapping is more specific and wins, so the controller actually runs; any other /recordings/ path returns a clean 404 instead of being forwarded to VOIPService.