Testing Your SMS v3 Integration

Note: If you're new to OpenMarket, then integrate with our Global SMS (version 4) operations.
Customers currently integrated using v3 may continue to use it, although we encourage customers to migrate to v4 in order to take advantage of new features. Please also note that there are no SDKs available for either version of the Global SMS API.

OpenMarket provides a Customer Integration Environment (CIE) for testing your integration. All responses to the request are simulated by OpenMarket, so neither the mobile operators nor end users are sent actual SMS messages.

You can test:

  • Request syntax and values
  • Send SMS requests to both international and US/Canada standard rate SMS requests
  • Retrieve message status requests
  • Operator lookup requests

If no errors are found in the request, the CIE responds with a ticket ID. If an error is found, the CIE responds with an OpenMarket response code.

Use the same account ID and password you use when submitting messages in production. You can use the same short codes, long codes, and alphanumeric source addresses in the CIE that you intend to use in production.

Constraints when using the CIE

  • Reporting is not supported
  • You cannot test mobile originated (MO) messages
  • The CIE is not intended for performance or load testing

Prerequisites

No special provisioning is required in order to use the CIE unless you want to use it for a demo account or to do any kind of performance testing. For those cases, contact your account manager to make sure your OpenMarket account is properly provisioned.

Operator lookup requests

You may use the CIE to simulate looking up the carrier ID for a given phone number using Operator Lookup. In the CIE, the carrier ID for T-Mobile (79) is always returned for operator lookups.

Connecting to the CIE

Use the following information to connect to the CIE.

HTTP

URL to submit MTs (XML/HTTP, SDKs)

https://smsc-cie.openmarket.com/wmp

URL for preview lookups

https://smsc-cie.openmarket.com/wmp

URL for query requests

https://smsc-cie.openmarket.com/wmp

US standard rate simulations

When you submit MTs, you will receive responses for both successful and failed messages. Errors are usually caused by improperly formatted messages or invalid parameters. For example, if you submit a message with a carrier ID that OpenMarket does not support, you will receive a response specific to that error condition.

To test simulated end-to-end message delivery, including error conditions related to unsuccessful message delivery to the carrier or subscriber handset, you must use the test scenarios provided here. The CIE returns a delivery receipt if you request a delivery receipt on MT submit. The Carrier ID field indicates the supported carriers for each test case.

Carrier ID 383 = AT&T

Carrier ID 77 = Verizon Wireless

Carrier ID 79 = T-Mobile USA

Carrier ID 34 = Sprint

If you omit Carrier ID in the test cases, then the CIE uses a default Carrier ID of 383 (AT&T).

Test scenarios for US standard rate MT messages

You will find the response code in the delivery receipt for a test message.

Phone number

Carrier ID

Charge type

Response code

Response code description

14081230000

34

0

0

"Message sent"

Note that you should consider this a successful message delivery if you receive this receipt, as some operators do not provide further updates.

14081230000

383, 77, 79

0

4

"Message delivered"

14081234567

34, 77

0

3041

"US standard rate message blocked by the OpenMarket deactivated numbers firewall"

This code is relevant for US messaging only. It's returned if the mobile number is on a list of deactivated numbers. Your program should now take the number out of your messaging list. See Handling Deactivated Phone Numbers for more information.

14075550155

77

0

810

"Failed message delivery"