80910: Message To Voice Only Session Rejected

This warning appears when Proxy receives an inbound message for a Session whose mode is voice-only. Proxy Sessions support message-only, voice-only, and voice-and-message, so Proxy rejects messaging traffic for a voice-only Session.

• The Session was created with mode set to voice-only.
• Your application expected one Session to handle both calls and messages, but the Session was not created with voice-and-message.
• The Proxy numbers available to your Service were selected for voice handling, while your messaging flow still routed an inbound SMS to that Session. Proxy number pools can contain numbers with Voice or SMS capabilities, and in many countries numbers support only one of those capabilities.

• Create the Session with mode set to voice-and-message if participants need to communicate over both voice and messaging.
• Create the Session with mode set to message-only if the interaction should support messaging only.
• Review your Session creation workflow and choose the correct mode before traffic begins. The Session create API accepts mode, while the Session update API does not expose mode as an update parameter.
• Verify that the Proxy numbers in your pool are SMS-capable if you expect inbound messages. In many countries, you need separate numbers for Voice and SMS.

• Session resource
• Proxy Quickstart for SMS and Voice
• Phone number management