Set up Andrews & Arnold messaging

Use this guide to receive and send A&A text messages in a SessionCloud BYO PBX account or a standalone SessionTalk account connected to a portal mailbox. Calling and SMS use separate settings.

Prepare the number

You need access to the A&A Control Pages for the VoIP number and to your BYO PBX project in SessionCloud. Confirm that A&A can receive SMS for the number. Configure its outgoing SMS password in A&A; this is separate from its SIP calling password.

Create the portal connection

1. Open Provisioning > Advanced > Messaging in your SessionCloud project.
2. Enable SMS and save the project.
3. Under Incoming and outgoing SMS, choose Andrews & Arnold.
4. Enter the A&A number in full international format as SMS username, and its outgoing SMS password as SMS password.
5. Enable and save the connection. Copy its Webhook URL.

The portal supplies the A&A API URL and field mappings. The outgoing SMS password stays in the portal when the app uses this connection.

Tell A&A where to send incoming messages

1. Sign in to A&A Control Pages and open the settings for the receiving number.
2. Find SMS Inbound and add the complete Webhook URL copied from SessionCloud as an HTTPS forwarding target.
3. Keep the URL unchanged, including its ?token=... credential, and save the A&A settings.

Do not add a trailing ? or &: A&A interprets those endings as a request to use HTTP GET. Our listener requires POST. The generated URL ends in its credential, so A&A sends URL-encoded POST data. A&A permits multiple forwarding targets separated by spaces; check existing targets before replacing them. See the A&A SMS API instructions .

A&A sends the originating number (oa), destination number (da), message (ud) and service-centre timestamp (scts). The portal uses da to select the assigned mailbox. You do not enter a phone IP address or a push-server address in A&A.

Assign the number and connect the app

In Assign a number, select the saved A&A connection, enter the receiving number with + and country code, and enter the app account’s exact SIP username and SIP domain. These identify the app account; they are not necessarily the same as the SMS username.

Follow Connect the app: SessionCloud uses authenticated provisioning, while standalone SessionTalk can import the number’s private App setup code.

Test incoming delivery

Send a short SMS from another phone to the A&A number. Check App delivery > Last received SMS in the portal, then confirm receipt in the app. Background the app, lock the phone, send a second SMS and tap its notification. Test an outgoing reply separately.

The connection supports text SMS. MMS and delivery-report callbacks are not implemented for A&A. Sent means accepted by the outgoing gateway, not confirmed delivery.

Keep the Webhook URL private. If it is exposed, use Replace webhook credential, copy the replacement URL into A&A and retest. The previous URL stops working immediately. See Webhook security and Troubleshooting SMS.