Login to CP as either a distributor or reseller
\nNavigate to the reseller level
\nHover over Endpoints and then click the Recording Servers link
\nClick the New Server button
\nComplete the Add Server information and click Save
\nMessage Copy (formerly known as SMS Copy) is a feature of the Tango Networks Extend service that allows the UCaaS platform of a Tango Networks Extend partner, to receive a copy of SMS and MMS messages sent to/from mobile subscribers using an Extend SIM.
\nMessage Copy is an API-only push service that provides a copy of the message metadata and content in the form of an HTTP(S) JSON POST to a partnerβs receiving endpoint.
\nSubscribers do not interact with the Message Copy service. The Message Copy feature is transparent to subscribers, and they are unaware of the service and whether it is enabled or disabled.
\nThe Message Copy feature supports:
\nUS and UK GPMN subscribers only
\nAll contents of the message copy are encoded in JSON format, using the UTF-8 character set
\nSMS originations and terminations
\nperson to person messaging
\nnumeric and alphanumeric sender/recipient addresses*
\nMMS originations and terminations:
\nperson to person messaging
\ngroup messaging (sometimes called group chat)
\nNumeric sender/recipient addresses
\nThe Message Copy service is not a billable feature and has no impact on invoices
\n* While a mobile device can receive messages from an alphanumeric sender, a mobile can only originate a message to a numeric address.
\nThe Message Copy feature does not support:
\nSystem messages - including Message Waiting indication messages, over-the-air SIM configuration messages, iMessage/FaceTime/iCloud activation messsages, and other binary messages
\nData-only messaging services - services like Apple's iMessage and or Android's RCS do not use the SMS or MMS signaling paths, as such, these data-only messages are not accessible by the Tango Networks Messaging infrastructure nor the Tango Networks Message Copy service.
\nIn order to use the Message Copy feature, the following Control Panel (CP) provisioning must be done first:
\nA distributor or reseller defines a Recording Server at the reseller level including the target endpointβs URL for offloading.
\nA distributor or reseller enables the Message Copy feature at the group level for all subscribers in a group.
\nOnce the Message Copy feature has been enabled for a group of subscribers the following recurring operations
\nTango Networks Extend platform initiates an offload cycle periodically, no faster than once every 4 minutes.
\nEach offload cycle sends up to 50 messages.
\nEach message is offloaded as a single JSON formatted HTTP(S) POST to the Recording Server target URL.
\nOnce a messages is successfully offloaded to the customer URL, the message is deleted from the Tango Networks Extend platform servers.
\nIf a message fails to offload, it will be tried again at the next offload cycle.
\nWhile the Message Copy service supports both HTTP and HTTPS for its POST requests to a partnerβs receiving endpoint, it is recommended that HTTPS be used to keep the contents of the copied messages secure in transit by using TLS encryption. HTTPS requires that the customer provide a proper valid public SSL certificate, issued by a CA.
\nBearer authentication is an HTTP authentication scheme that involves security tokens called bearer tokens. These tokens are data filled against the provisioning Message Copy Recording Server. If provisioned every request includes the token as part of the Authentication Header.
\nA single Message Copy offload cycle can generate up to 50 HTTP(S) POST events to a partner's receiving endpoint. To lower the impact on the partner's receiving endpoint, the HTTP(S) POST events are sent serially, not in parallel. Tango Networks Extend platform initiates an offload cycle periodically, no faster than once every 4 minutes.
\nWhen a message is offloaded to the partnerβs receiving endpoint, the message metadata and content are encoded using the following JSON schema:
\n\"smsEvent\" : [ {\n \"direction\" : \"string\", <\"mo\" or \"mt\">\n \"startTime\" : \"string\", <\"yyyy-MM-dd'T'HH:mm:ss.SSSZ\">\n \"segment\" : { <Optional> - No longer included by Message Copy\n \"id\" : \"string\", - No longer included by Message Copy \n \"number\" : int, - No longer included by Message Copy\n \"total\" : int - No longer included by Message Copy\n },\n \"subscriberParty\" : {\n \"domain\" : \"string\", <domain of customer/tenant>\n \"mobile\" : \"string\", <subscriber international Mobile Number>\n \"did\" : \"string\", <subscriber international DID>\n \"subrId\" : \"string\" <subscriber Tango Extend ID>\n },\n \"otherParty\" : {\n \"number\" : \"string\" <Received number identifying other user>\n },\n \"message\" : \"string\" <message content>\n \"messageType\" : \"string\" <\"sms\" or \"mms\">\n \"messageContentType\" : \"string\" <content-type/sub-type of message content> \n} ]\n\nThis section describes the Control Panel (CP) actions needed to enable the
Message Copy feature.
CP Distributor or Reseller creates a Recording Server including the target URL for offloading.*
\nCP Distributor or Reseller enables the Message Copy feature specifying the Recording Server.
\n* If the Recording Server URL is HTTPS, a valid signed certificate is required. Refer to Security for more information.
\nThe Recording Server defines a server name, the target country, and a URL
for the customerβs offload server.
Login to CP as either a distributor or reseller
\nNavigate to the reseller level
\nHover over Endpoints and then click the Recording Servers link
\nClick the New Server button
\nComplete the Add Server information and click Save
\nAll of the following fields are mandatory:
\nName - Provide a unique and identifiable name
\nHomeLoation - Select Home Location of this recording server
\nCountry - Select Country
\nServer Type - Select Message Copy
\nURL - Provide a valid HTTPS or HTTP URL for the offloading target server*
\nAuthentication Key - Optional Bearer Authentication Token
\n* If the URL is HTTPS, a valid signed certificate is required. Refer to Security for more information.
\nMessage Copy enables (or disables) the Message Copy feature for all subscribers in a Group.
\nAs either a distributor or reseller in CP
\nNavigate to a Group
\nHover over Endpoints and then click the Edit Message Copy Settings link
\nEnable/Disable the feature, select the Recording Server, and click Save.
\nAll fields are mandatory:
\nSend a copy of all messages for all subscribers in a Group - (defaults to OFF) - Slide to ON to enable Message Copy for all subscriber in this Group
\nMessage Copy Server - Select the Recording Server from the drop-down menu.*
\n* If the Recording Server uses HTTPS, after a valid signed certificate has been loaded, the service is ready. For Recording Servers that use HTTP, no furtehr action is required. Refer to Security for more information.
\nThe Tango Networks Messaging Copy feature includes all necessary message metadata and content to enable a partner to recreate (and display) a copied message. This section describes how a partner can use the provided information to re-create and display a message locally.
\nThe following fields are used for both SMS and MMS messages:
\ndirection - This will indicate whether the message was an originated by the mobile mo, or terminated to the mobile mt
startTime - This is the timestamp for when the message was processed.
\nmobile - For an mo, this is the from party. For an mt this is the to party.
number - For an mo, this is the to party. For an mt this is the from party.*
messageType - This will be sms for SMS messages and mms for MMS messages.
* For a Group MMS message, only the first recipient is shown in the number field. The full list of recipients is included in the message contents. Refer to Processing MMS Messages for more information.
To recreate and display an SMS message, the following additional fields can be used:
\nmessageContentType - This indicated the character set encoding of the message content. For sms messages, this will be text/plain; charset=UTF-8.
message - This is the message content that should be displayed. The string can be directly copied as a UTF-8 string, which will automatically handle emoji and extended characters,
\nThe following is an example of an JSON file for an SMS origination:
\n{\n \"smsEvent\" : [ {\n \"direction\" : \"mo\",\n \"startTime\" : \"2024-09-16T19:30:39.090+0000\",\n \"subscriberParty\" : {\n \"domain\" : \"software.tango-networks\",\n \"mobile\" : \"19465559040\",\n \"did\" : \"19465559040\",\n \"subrId\" : \"s021157\"\n },\n \"otherParty\" : {\n \"number\" : \"12145555273\"\n },\n \"message\" : \"This is SMS one π.\",\n \"messageType\" : \"sms\",\n \"messageContentType\" : \"text/plain; charset=UTF-8\"\n } ]\n}\n\nProcessing the various offloaded JSON files can be done in many ways. It really depends on the requirements of the partner. Here is an simple bash shell script that will create a csv file for all offloaded SMS messages:
\necho \"date,direction,extendmobile,otherparty,message\" > output.csv; \\\ngrep -l '\"messageType\" : \"sms\"' * | while read aFile ; do cat ${aFile} \\\n| jq -r '[.smsEvent[].startTime, .smsEvent[].direction, .smsEvent[].subscriberParty.mobile, .smsEvent[].otherParty.number, \n.smsEvent[].message] | @csv' ; done >> output.csv\n\nThe output.csv generated by the above script will look something like the following:
\ndate,direction,extendmobile,otherparty,message\n\"2024-09-16T19:30:39.090+0000\",\"mo\",\"19465559040\",\"12145555273\",\"This is SMS one π.\"\n\"2024-09-16T20:42:31.055+0000\",\"mt\",\"19465559040\",\"12145555273\",\"This is a a \"\"SMS termination\"\" message.\"\n\nTo recreate and display an MMS message, additional parsing and processing must be performed on the message content body. The display form of an MMS message is binary in nature (for example a PNG image a stream of binary data). The Tango Networks Extend infrastructure re-uses the text-based MM7 protocol encoding of an MMS message that comes from the MMSC Gateway. Specifically, MMS messages are encoded as 3GPP MMS Version 5.3.0 using MM7 Schema REL-5-MM7-1-2. This same format is re-used by the Messaging Copy feature.
\nIn slightly less technical terms, the MMS message is stored in a multipart, text-only format, consisting of:
\nSOAP envelope - This is the first part, and is always present. It contains, among other things, the To, From, and Subject information of the MMS message.*
application/smil - This part describes how a message should be displayed. Think of it as HTML doc that describes the layout of MMS.
\ncontent part(s) - An MMS message can contain multiple content parts (e.g., a text part plus one more media files, or just multiple media files, etc.). There will always be at least one of the following in an MMS message:
\ntext/plain - This is the text portion of the MMS content (i.e., whatever the person typed). This is an optional part.
\nimage/xxx (xxx is a supported image format, e.g., png, jpeg, bmp, etc.) - This is a base64 encoded image file. There can be multiple images in a single MMS message.
\naudio/xxx (xxx is a supported audio format, e.g., wav, ogg, mp3, etc.) - This is a base64 encoded audio file. There can be multiple audio files in a single MMS message.
\ntext/x-vcard (or text/vcard) - This is a vcard. If the vcard contains a photo, it will be encoded in base64.
\n* For Group MMS messages the entire list of recipients is present in the Recipients portion of the SOAP envelope.
The above list of content type/sub-types is not an exhaustive list, these are just common ones that are seen in a typcial MMS message.
\nOne of the common use cases for partner post processing would be to see the image portion of an MMS message. Here is a series of bash commands that will extract and recreate images for all offloaded MMS messages:
\ngrep -l '\"messageType\" : \"mms\"' * | \\\nwhile read aFile ; do \\\n uuid=$(echo ${aFile} | cut -f1-5 -d'-') ; \\\n grep -oP \"(?<=\\\"(message)\\\" : \\\")[^(,$)]+\" ${aFile} | awk '{gsub(/\\\\r\\\\n/,RS)} 1' > mm7_message.txt\n csplit -s -f part -n 3 -z mm7_message.txt /-----mime-/ '{*}'\n grep -le \"Content-Transfer-Encoding: base64\" part* | \\\n while read aPart ; do \\\n filename=$(grep -oP 'name=\\\\\"\\K[^\\\\]+' ${aPart}) ; \\\n base64_data=$(awk '/^$/ {p=1; next} p' ${aPart} | grep -v '^-') ; \\\n echo \"${base64_data}\" | base64 -d > \"${uuid}-${filename}\" ; \\\n echo \"File extracted: ${uuid}-${filename}\" ; \\\n /bin/rm part* ; /bin/rm mm7_message.txt ; \\\n done ; \\\ndone\n\nThe output of the above script will look something like:
\nFile extracted: 2d0f8fdd-e91e-41d8-b341-04a3eaa8b417-image000000.png\n\nThis image file can then be opened in any image viewer (or browser) application to show:
\nThis is just an example of one way to process an offloaded MMS message. The bash schell commands could easily be wrapped in a script to add more descriptive output and to do enhanced message processing.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"π Tango Networks Message Copy API","slug":"tango-networks-message-copy-api"},{"content":"βHow does Message Copy work?","slug":"how-does-message-copy-work"},{"content":"π Security","slug":"security"},{"content":"π Authentication","slug":"authentication"},{"content":"π¦ Rate and usage limits","slug":"rate-and-usage-limits"},{"content":"πJSON Schema","slug":"json-schema"},{"content":"π» Control Panel Provisioning","slug":"control-panel-provisioning"},{"content":"π© Using Offloaded Messages","slug":"using-offloaded-messages"}],"owner":"2404338","collectionId":"5813d06f-f2d8-41e9-aba6-d86710180a56","publishedId":"2sAXqtZgGa","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2024-12-11T17:48:16.000Z"},"item":[{"name":"SMS Origination - text only","id":"05d21192-c5ff-4492-a69c-2a9fb69c2044","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"smsEvent\" : [ {\n \"direction\" : \"mo\",\n \"startTime\" : \"2024-09-16T19:21:45.783+0000\",\n \"subscriberParty\" : {\n \"domain\" : \"software.tango-networks\",\n \"mobile\" : \"19465559040\",\n \"did\" : \"19465559040\",\n \"subrId\" : \"s021157\"\n },\n \"otherParty\" : {\n \"number\" : \"12145555273\"\n },\n \"message\" : \"An SMS origination.\",\n \"messageType\" : \"sms\",\n \"messageContentType\" : \"text/plain; charset=UTF-8\"\n } ]\n}","options":{"raw":{"language":"json"}}},"url":"","description":"This is an example POST for the offloading of an SMS origination message. In this example:
\nThe Tango Networks Extend subscriber's international mobile number is: 19465559040
The terminating number is: 12145555273
The text of the message is: An SMS origination
JSON Field Definitions
\nSubscriberParty JSON Object
\nView More
\nOtherParty JSON Object
\nView More
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"X-API-Key"},{"key":"value","value":"{{token}}"}]},"isInherited":true,"source":{"_postman_id":"5813d06f-f2d8-41e9-aba6-d86710180a56","id":"5813d06f-f2d8-41e9-aba6-d86710180a56","name":"Tango Networks Message Copy API","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"05d21192-c5ff-4492-a69c-2a9fb69c2044"},{"name":"SMS Origination - text with emoji","id":"ce2ecf47-9de5-4af2-92e7-3182bf95f37b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"smsEvent\" : [ {\n \"direction\" : \"mo\",\n \"startTime\" : \"2024-09-16T19:28:15.626+0000\",\n \"subscriberParty\" : {\n \"domain\" : \"software.tango-networks\",\n \"mobile\" : \"19465559040\",\n \"did\" : \"19465559040\",\n \"subrId\" : \"s021157\"\n },\n \"otherParty\" : {\n \"number\" : \"12145555273\"\n },\n \"message\" : \"This is a long message being saved. πππππππ. The rain in Spain falls mainly on the plain.\",\n \"messageType\" : \"sms\",\n \"messageContentType\" : \"text/plain; charset=UTF-8\"\n } ]\n}","options":{"raw":{"language":"json"}}},"url":"","description":"This is an example POST for the offloading of an SMS origination message. In this example:
\nThe Tango Networks Extend subscriber's international mobile number is: 19465559040
The terminating number is: 12145555273
The text of the message is: This is a long message being saved. πππππππ. The rain in Spain falls mainly on the plain.
JSON Field Definitions
\nSubscriberParty JSON Object
\nView More
\nOtherParty JSON Object
\nView More
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"X-API-Key"},{"key":"value","value":"{{token}}"}]},"isInherited":true,"source":{"_postman_id":"5813d06f-f2d8-41e9-aba6-d86710180a56","id":"5813d06f-f2d8-41e9-aba6-d86710180a56","name":"Tango Networks Message Copy API","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"ce2ecf47-9de5-4af2-92e7-3182bf95f37b"},{"name":"SMS Termination - text only","id":"f4bbe597-8dac-41eb-8fc7-4e8d2bed54c3","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"smsEvent\" : [ {\n \"direction\" : \"mt\",\n \"startTime\" : \"2024-09-16T20:48:50.157+0000\",\n \"subscriberParty\" : {\n \"domain\" : \"software.tango-networks\",\n \"mobile\" : \"19465559040\",\n \"did\" : \"19465559040\",\n \"subrId\" : \"s021157\"\n },\n \"otherParty\" : {\n \"number\" : \"12145555273\"\n },\n \"message\" : \"An SMS termination message.\",\n \"messageType\" : \"sms\",\n \"messageContentType\" : \"text/plain; charset=UTF-8\"\n } ]\n}","options":{"raw":{"language":"json"}}},"url":"","description":"This is an example POST for the offloading of an SMS termination message. In this example:
\nThe Tango Networks Extend subscriber's international mobile number is: 19465559040
The originating number is: 12145555273
The text of the message is: An SMS termination message.
JSON Field Definitions
\nSubscriberParty JSON Object
\nView More
\nOtherParty JSON Object
\nView More
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"X-API-Key"},{"key":"value","value":"{{token}}"}]},"isInherited":true,"source":{"_postman_id":"5813d06f-f2d8-41e9-aba6-d86710180a56","id":"5813d06f-f2d8-41e9-aba6-d86710180a56","name":"Tango Networks Message Copy API","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"f4bbe597-8dac-41eb-8fc7-4e8d2bed54c3"},{"name":"SMS Termination - text emoji","id":"1c008894-3c13-4243-9aef-fac3c3290146","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"smsEvent\" : [ {\n \"direction\" : \"mt\",\n \"startTime\" : \"2024-09-16T20:48:50.157+0000\",\n \"subscriberParty\" : {\n \"domain\" : \"software.tango-networks\",\n \"mobile\" : \"19452569040\",\n \"did\" : \"19452569040\",\n \"subrId\" : \"d000157\"\n },\n \"otherParty\" : {\n \"number\" : \"12147275273\"\n },\n \"message\" : \"An SMS termination message with emoji characters: ππ€π\",\n \"messageType\" : \"sms\",\n \"messageContentType\" : \"text/plain; charset=UTF-8\"\n } ]\n}","options":{"raw":{"language":"json"}}},"url":"","description":"This is an example POST for the offloading of an SMS termination message. In this example:
\nThe Tango Networks Extend subscriber's international mobile number is: 19465559040
The terminating number is: 12145555273
The text of the message is: An SMS termination message with emoji characters: ππ€π
JSON Field Definitions
\nSubscriberParty JSON Object
\nView More
\nOtherParty JSON Object
\nView More
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"X-API-Key"},{"key":"value","value":"{{token}}"}]},"isInherited":true,"source":{"_postman_id":"5813d06f-f2d8-41e9-aba6-d86710180a56","id":"5813d06f-f2d8-41e9-aba6-d86710180a56","name":"Tango Networks Message Copy API","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"1c008894-3c13-4243-9aef-fac3c3290146"},{"name":"MMS Origination","id":"5e38cf8e-cf41-47b6-9c3e-58c7fefa160d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"smsEvent\" : [ {\n \"direction\" : \"mo\",\n \"startTime\" : \"2024-09-16T20:52:55.477+0000\",\n \"subscriberParty\" : {\n \"domain\" : \"software.tango-networks\",\n \"mobile\" : \"19465559040\",\n \"did\" : \"19465559040\",\n \"subrId\" : \"s021157\"\n },\n \"otherParty\" : {\n \"number\" : \"12145555273\"\n },\n \"message\" : \"-----mime-boundary-14AED7BD.B106ADFE\\r\\nContent-Type: text/xml; charset=utf-8\\r\\nContent-ID:![](\\\"image000000.png\\\")
This is an example POST for the offloading of an MMS origination picture message. In this example:
\nThe Tango Networks Extend subscriber's international mobile number is: 19465559040
The terminating number is: 12145555273
There is no text portion included with this MMS origination.
\nThere is a PNG image attachment that renders as:
\nJSON Field Definitions
\nSubscriberParty JSON Object
\nView More
\nOtherParty JSON Object
\nView More
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"X-API-Key"},{"key":"value","value":"{{token}}"}]},"isInherited":true,"source":{"_postman_id":"5813d06f-f2d8-41e9-aba6-d86710180a56","id":"5813d06f-f2d8-41e9-aba6-d86710180a56","name":"Tango Networks Message Copy API","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"5e38cf8e-cf41-47b6-9c3e-58c7fefa160d"},{"name":"MMS Origination - Group Message","id":"8fb5cf48-5147-4c7d-84a3-1df1e69cef06","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"smsEvent\" : [ {\n \"direction\" : \"mo\",\n \"startTime\" : \"2024-09-19T19:25:26.104+0000\",\n \"subscriberParty\" : {\n \"domain\" : \"software.tango-networks\",\n \"mobile\" : \"19465559040\",\n \"did\" : \"19465559040\",\n \"subrId\" : \"s021157\"\n },\n \"otherParty\" : {\n \"number\" : \"19455559041\"\n },\n \"message\" : \"-----mime-boundary-A1CD5413.CAA2C6D4\\r\\nContent-Type: text/xml; charset=utf-8\\r\\nContent-ID:This is an example POST for the offloading of an MMS origination picture message. In this example:
\nThe Tango Networks Extend subscriber's international mobile number is: 19465559040
The list of recipents for this Group MMS message are: 19455559041, 12145555273, 14699202123
The text portion in this Group MMS origination is: Group MMS message origination 1. π€
There are no media attachments for this Group MMS message.
\nJSON Field Definitions
\nSubscriberParty JSON Object
\nView More
\nOtherParty JSON Object
\nView More
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"X-API-Key"},{"key":"value","value":"{{token}}"}]},"isInherited":true,"source":{"_postman_id":"5813d06f-f2d8-41e9-aba6-d86710180a56","id":"5813d06f-f2d8-41e9-aba6-d86710180a56","name":"Tango Networks Message Copy API","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"8fb5cf48-5147-4c7d-84a3-1df1e69cef06"},{"name":"MMS Termination","id":"aa560a25-0292-4bf6-8b84-54d49d3509a2","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"smsEvent\" : [ {\n \"direction\" : \"mt\",\n \"startTime\" : \"2024-09-18T14:56:00.961+0000\",\n \"subscriberParty\" : {\n \"domain\" : \"software.tango-networks\",\n \"mobile\" : \"19465559040\",\n \"did\" : \"19465559040\",\n \"subrId\" : \"s021157\"\n },\n \"otherParty\" : {\n \"number\" : \"12145555273\"\n },\n \"message\" : \"-----mime-boundary-5BB6D873.17AB5334\\r\\nContent-Type: text/xml; charset=utf-8\\r\\nContent-ID:![](\\\"image000001.png\\\")
This is an example POST for the offloading of an MMS termination message. In this example:
\nThe Tango Networks Extend subscriber's international mobile number is: 19465559040
The originating number is: 12145555273
The text portion included with this MMS termination is: Do you want to get some lunch?
There is also a PNG image attachment that renders as:
\nJSON Field Definitions
\nSubscriberParty JSON Object
\nView More
\nOtherParty JSON Object
\nView More
\n","auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"X-API-Key"},{"key":"value","value":"{{token}}"}]},"isInherited":true,"source":{"_postman_id":"5813d06f-f2d8-41e9-aba6-d86710180a56","id":"5813d06f-f2d8-41e9-aba6-d86710180a56","name":"Tango Networks Message Copy API","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"aa560a25-0292-4bf6-8b84-54d49d3509a2"}],"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"X-API-Key"},{"key":"value","value":"{{token}}"}]}},"event":[{"listen":"prerequest","script":{"type":"text/javascript","exec":[""],"id":"a47cf1b6-9280-44c5-8045-befb7355921f"}},{"listen":"test","script":{"type":"text/javascript","exec":[""],"id":"88d8e457-11a6-4403-81b2-3e2ea2221501"}}],"variable":[{"key":"baseUrl","value":"https://farming-simulator.pstmn.io"}]}