| Connecting to operator MMSC to (Only) send MMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 07, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Amr Qanadilo New member Username: Amqanadilo Post Number: 1 Registered: 01-2009 |
Dear Sir or Madam; I have downloaded the trial nowsms and i have been reading through its documentation and i still have a question.... i have an account for the MMSC from the operator and the question is .... do i need a GPRS model to send MMS if am connecting to the operator MMSC? if not, what are the Tab in the gateway should i use to connect? Another question would be " can i use the web interface to send MMS to the operatros MMSC, and can use it to send 20,0000 MMS? Thanks for your help | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 365 Registered: 08-2008 |
The answer depends on what type of account you have. Is it an MM7 connection? (If yes, then you do not need a GPRS modem for this. You can leave the "SMSC" list blank, and ignore the warnings about no SMSCs being defined.) Please provide more detail. -- Des NowSMS Support | |||
| Amr Qanadilo New member Username: Amqanadilo Post Number: 2 Registered: 01-2009 |
Deaer Des; Thank you for your feedback. To answer your question. Yes, i do have MM7 account with the operator MMSC, and i want only to send MMS not to receive. in this case which Tab should i use to enter the MMSC information of the operator- knowing that i dont want to use nowsms as mmsc-. Now after i connect to the MMS center, how can i make sure it is working, usinbg the web interface? another question can i use the interface to send 5000 MMS using the web interface or do i need to go into some sort fo programming Thanks for your help Best Regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 377 Registered: 08-2008 |
Hi Amr, Go to the "MMSC Routing" page. Add a new route that has the details for your operator MMSC connection. Note that terminology can vary quite a bit between different vendors, so if you get confused, let us know what parameters your operator has given you, and we can help translate their terminology to ours. After you define this route, on the same "MMSC Routing" page, in the "Default Route" field, make sure that this MM7 route is selected as the default. This tells NowSMS to route all messages via your MM7 connection. Start both the SMS and MMSC services. The SMS service provides the web interface capabilities, and the MMSC service handles both direct delivery MMSC activities and external MMS routing activities. Chances are that your first MM7 attempt will fail. This is because MM7 has far more parameters and different ways these parameters can be specified than is the case for SMS related protocols. So if it doesn't work, enable the "MMSCDEBUG.LOG", via a setting that can be found on the "Serial #" page of the configuration dialog. Try sending another MMS message, and then send us the MMSCDEBUG.LOG, and we can help troubleshoot it. (You can either post it in reply here, or e-mail it to nowsms@nowsms.com with "Attention: Des" in the subject line of your message. If you e-mail the file, please also post some info here so that I know to look for the e-mail.) If you will also be receiving MMS messages from the operator, then they will need to be able to connect back to your NowSMS server for them to deliver messages. To enable this, you need to define an "MMSC VASP" account on your system for the operator. Have them connect to the MMSC HTTP Port number on your NowSMS server with the following URL: http://ip:port/mm7/account=password, where "account" and "password" are what you have setup in the "MMSC VASP" account on your server. -- Des NowSMS Support | |||
| Sajid Ahmed New member Username: Sajid Post Number: 16 Registered: 10-2008 |
Hi Des, As you said we need only "MMSC Routing" to accomplish mm7 type of connection to send mms?Can you please elaborate ,whether we need "MMSC VASP" account details in order to send mms? its because of contradicting (confuse by me )with this link http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Submitting_MMS_Messages_MM7.htm Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 396 Registered: 08-2008 |
Hi Sajid, First some informative cross-reference. Someone else posted a question about making an MM7 connection, and I posted more detail about it here: http://support.nowsms.com/discus/messages/12/24725.html The explanation there is more detailed than the explanation that I offered above.
With the above said, I think your question is different. Let me see if I can clarify. In many ways, NowSMS is like a swiss army knife of messaging protocols. NowSMS implements some protocols as a client, so that it can connect to other SMSCs and MMSCs to send messages. NowSMS implements some protocols as a server, so that other pieces of client software can connect to NowSMS, using NowSMS as a gateway/conduit for message delivery. And for some protocols, NowSMS implements these protocols as both a client and a server. That can be particularly confusing because for some people the protocol is being used by NowSMS to connect to a messaging service provider. For others, they are using this protocol from their application to interface with NowSMS. In the case of MM7, this is often the protocol that is used for interfacing with an operator MMSC. When you are using MM7 to interface with an operator MMSC, you define an "MMSC Routing" definition to define how NowSMS submits messages outbound to the MMSC (in the SMS world, this would be called MT). Optionally, you define an "MMSC VASP" account to allow the operator to deliver messages inbound back to NowSMS (in the SMS world, this would be called MO). If you are interfacing with NowSMS using MM7, then you define an "MMSC VASP" account an account that your application will use for submitting messages to NowSMS (in this instance, they would be MT). And if you will be receiving messages back via MM7, you define an "MMSC Routing" account that specifies how NowSMS will deliver messages back to your application. -- Des NowSMS Support | |||
| Sajid Ahmed New member Username: Sajid Post Number: 17 Registered: 10-2008 |
Hi Des, Thanks for your quick reply. In "MMSC Routing" tab when i click Add button and select mm7 to route messages to vasp. lets assume i got connected by proper url and other parameters.connection type should be "To MMSC". This is how we are connected to operator mmsc to deliver mms.please correct if i am wrong! Now assuming i am connected to operator mmsc configuring "MMSC Routing" now i will send mms file i.e .mms from nowsms/mms web interface. if i wanna achieve this programatically(sending of message) how? Can i directly add binary and post it as showm in the link? http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Submitting_MMS_Messages_MM7.htm "To post to the Now SMS/MMS Gateway via MM7, you must connect to the HTTP port configured for the MMSC on the "MMSC" page of the configuration dialog. And you must perform an HTTP POST of the MM7 content to a URI of "/mm7", which is how the gateway knows that the VASP intends to submit in the MM7 format" As describe in link i will adding binary content as define in xml and doing post message to invoke URI. "If you are interfacing with NowSMS using MM7, then you define an "MMSC VASP" account an account that your application will use for submitting messages to NowSMS (in this instance, they would be MT). And if you will be receiving messages back via MM7, you define an "MMSC Routing" account that specifies how NowSMS will deliver messages back to your application" Des its like when we need to send only mms through operator mmsc we no need to bother about "MMSC VASP" tab but the Route message to VASP is mm7 means operators VASP account not our "MMSC VASP"tab.when we want mms from operator mmsc to our application then only we use "MMSC VASP"tab. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ------------------------------------------------------- Do i need to add to the gateway in specific directory or mmsc server.as when i send mms through webUI using direct mmsc of nowsms i mean not operator mmsc its nowsms mmsc bypass operator mmsc then all .mms are in directory "C:\Program Files\NowSMS\MMSCDATA\20090127\11" and so on.As per documented here nowsms/mms will act as direct delivery of mms and it will create dynamic URL which is send to end user phone and later using the link its retrieved. in the case of operator mmsc "# Send the message through the operator MMSC. NowSMS supports all of the major MMS related protocols, including MM7, MM4, MM1 and EAIF for this purpose. But most frequently, what we see is the use of MM1 where NowSMS makes a GPRS connection over a GSM/GPRS modem, connects to the operator WAP gateway that is designated for MMS usage by the operator, and submits the message to the operator MMSC via the WAP gateway over the GPRS connection. " Question: In over case its not mm1 its mm7 so can you please explain in this perspective? -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ------------------------------------------------------- Please correct me and help me to understand the concept. Thanks Sajid | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 399 Registered: 08-2008 |
That sounds ok.
There are several different protocols that you can use. You can certainly use MM7 to submit messages to NowSMS. If you are going to use MM7, define an "MMSC VASP" account in NowSMS. When you post to NowSMS, use a post URL of http://server:port/mm7/account=password (you can leave out /account=password if you supply an Authorization: header with HTTP Basic Authentication instead). For information on the protocols that you can use, here's a good link: http://support.nowsms.com/discus/messages/1/830.html ... or refer to page 160 of the manual, which is a bit more detailed than the info on the web. If all of this is a bit overwhelming, take a look at the command line script described at the following link: http://blog.nowsms.com/2007/07/sending-mms-from-command-line.html That's the easiest way to submit an MMS message to NowSMS, as you don't have to mess with submitting files over HTTP, you can just send them through a simple command line utility. (Note that this script does not submit messages through an "MMSC VASP" account. It submits via an "SMS Users" account. The script uses a username and password of "test", which you can change by manually editing the script.)
Sending only requires: "MMSC Routing" definition for connection to operator. "MMSC VASP" definition for your application to submit messages into NowSMS (if using MM7, MM4 or MM1/EAIF). If also receiving messages: "MMSC VASP" definition for operator to deliver messages back to your NowSMS system. "MMSC Routing" definition for routing messages to your application ... if you are not using the file-based interface for processing received messages. Note: For receiving MMS messages in your own application, the easiest API is PHP based, and is described here: http://www.nowsms.com/support/bulletins/tb-nowsms-016.htm
No special directories or remote access to your NowSMS server required. The full content of the MMS message is posted over MM7 to the mobile operator.
MM1 over a GPRS modem is more for lower volume messaging. A GSM/GPRS/3G modem is a modem that operates on the mobile network. It takes a SIM card just like a mobile phone, and basically it looks like a mobile phone to the network. NowSMS can send and receive SMS and MMS messages over this type of modem ... basically the same way that a phone would if the SIM card was in a mobile phone. -- Des NowSMS Support | |||
| Sajid Ahmed New member Username: Sajid Post Number: 18 Registered: 10-2008 |
Hi Des, From the link which is given below i am clear about various approaches and protocols which can be used to send MMS messages to the Now SMS/MMS Gateway.Thanks a lot! http://support.nowsms.com/discus/messages/1/830.html ################################################################################ ################ I just wanna know the flow of events in only mm7 perspective please dont explain other approaches as i am getting confused i need only mm7. ************************************************************************** "what we see is the use of MM1 where NowSMS makes a GPRS connection over a GSM/GPRS modem, connects to the operator WAP gateway that is designated for MMS usage by the operator, and submits the message to the operator MMSC via the WAP gateway over the GPRS connection" ************************************************************************** Sajid : Above description is for mm1 i was asking you about mm7 in same way how the work flow happens if its mm7. ################################################################################ ################ Des: The full content of the MMS message is posted over MM7 to the mobile operator. ------------------------------------------------------------ Sajid : full content-- Is this depends upon operator or nowsms/mms gateway as describe in the link.if its as describe in the link then why two boundaries and what does each element and attributes means? Here what would be the content which need to be posted and how? Can we find elaborate explanation of each element and attributes of xml? Right now i don't want to talk about receiving of mms.just need to concentrate on sending part.so as per my understandings we need both "MMSC VASP" and "MMSC Routing" information or account from operator.only having "MMSC Routing" wont be enough ? ################################################################################ ################ Des: Sending only requires: "MMSC Routing" definition for connection to operator. "MMSC VASP" definition for your application to submit messages into NowSMS (if using MM7, MM4 or MM1/EAIF). -------------------------------------------------------------- Sajid: As said only mm7 protocal so i need to gather information from the operator about only "MMSC Routing"? and how about "MMSC VASP" information which i need to have ? from where do i get it? from operator or where my application ? if i set this then what xml need to be posted and how? ################################################################################ ################ My requirement is. I will need to create an application which will use mm7 protocal only to connect operator mmsc to send mms by using nowsms/mms gateway as middleware. so i have .mms files. Now how i can send mms message programatically need to add binary in xml? Do i need to invoke any webservice? Do i need to create raw soap and post to URL(which URL define by us or given by operator)? Is there any WSDL to which i can write my client program? What xml i need to form and what does each attribute and element refers to? The xml formed will be specific to nowsms/mms gateway as we are using it as middleware to reach operator mmsc or the xml will be vender(operator)specific. Do we need to ask operator for the format of xml which need to be poasted? To which link we will post the xml and how? Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 403 Registered: 08-2008 |
Hi Sajid, I'm sorry, but I really just don't understand your questions. Or they are questions that are beyond the scope of what I can answer without writing a book. My personal opinion is that the best way to learn something is to start trying to do it, then ask questions when you get stuck. If you want more information on the MM7 format, then you should download the 3GPP TS 23.140 specification. You can find this at: http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/ That site has an archive of all versions of the specification. I'd recommend the "-530" version, which is a good baseline ... the first really stable version of the specification which included MM7. My suggestion to you would be to configure NowSMS for the MM7 connection to the mobile operator. Send some test messages from the web interface of NowSMS. Try using the command line script to send some MMS messages. If you're familiar with PHP, there is also a PHP script for submitting an MMS message through NowSMS at http://blog.nowsms.com/2008/11/nowsms-php-example-send-mms-message.html. If you want to learn MM7, then the specification will answer questions about the XML schema and format. -- Des NowSMS Support | |||
| Sajid Ahmed New member Username: Sajid Post Number: 19 Registered: 10-2008 |
Hi Des, Sorry to trouble you and thanks for the info. I was really trying to get how nowsms/mms gateway functions. My questions are about what i need to get (expect) from my operator and how to configure nowsms/mms gateway to operator mmsc with parameters provided by operator( MMSC VASP and MMSC Routing here messed up ). It would be nice of you if you could go through it once again. I am waiting for MM7 Account with the operator MMSC. once i get account details i need to know how to configure it to nowsms/mms gateway. I am ready to test php script,webinterface but wanna first link my operator mmsc so all above questions... Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 405 Registered: 08-2008 |
Hi Sajid, Ok ... I'm sorry ... now I understand ... you are waiting on your operator, so you can't try anything until they get back to you. I wrote up an article for our tech support blog going through all of this. Unfortunately, my boss doesn't want to publish it on the blog until next week. So here's the rough draft ... the final should post on http://blog.nowsms.com either Monday or Tuesday of next week. === While NowSMS can function as an MMSC for direct MMS message delivery, this is not an option for most content providers, as most mobile operators block MMS message delivery from any MMSCs other than the mobile operator. In these situations, it is necessary to submit all MMS messages via an operator MMSC, or a service provider with operator MMSC connectivity. (For more information on how MMS works, and how external MMSC message delivery is blocked by a mobile operator, please see http://www.nowsms.com/howmmsworks.htm.) The following protocols are frequently used for submiting messages via an operator MMSC: MM1 - This is the protocol that mobile phones use for sending and receiving MMS messages. NowSMS has the ability to send and receive MMS messages using MM1 over a GPRS/EDGE/3G modem connected to an operator network, using the same protocols as the MMS client in a mobile phone. This capability is dicussed in more detail at http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Connecting_to_operator_MMSC.htm. EAIF - This is a variation of the MM1 protocol defined by Nokia. It does not require a GPRS modem, as connections to the mobile operator MMSC occur directly over TCP/IP with an HTTP-based protocol. A few mobile operators with existing Nokia MMSC installations prefer to use the EAIF, but it is expected that they will be migrating to the more standard MM7 protocol. MM4 - This is an SMTP based protocol that is normally used by mobile operator for interconnecting their MMSCs. It is unusual for a content provider to interface with a mobile operator using MM4, but it is possible. More information on configuring NowSMS for interoperator MM4 connections can be found in the following article: http://blog.nowsms.com/2008/06/mmsc-mm4-interconnection-basics.html MM7 - This is the MMS protocol that has been designed explicitly for the purpose of content providers interfacing with a mobile operator MMSC. The MM7 protocol uses SOAP-based XML transactions over HTTP. A simple example of an MM7 message submission can be found at the following link: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Submitting_MMS_Messages_MM7.htm For detailed information on the MM7 protocol, refer to the 3GPP TS 23.140 specification, which defines the overall MMS architcture, and the detailed technical realisation of the MM7 protocol. Different versions of the 3GPP TS 23.140 specification can be found at http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/. 23140-530.zip is a good version to start with, as it is what we consider to be the first "stable" definition of MM7, which is Release 5, Version 1.2. (Note: There are a few operator MMSCs that use earlier MM7 implementations, and there are some subtle differences in the XML schemas for different MM7 releases.) Configuring NowSMS for an MM7 Connection to a Mobile Operator With that brief introduction out of the way, let's look at the specifics of configuring NowSMS to connect to a mobile operator with MM7. In the SMS world, the SMPP protocol is most frequently used for high volume SMS content delivery. Since many MMS content providers are existing SMS content providers, it may help to point out some significant ways in which MM7 differs from SMPP. With SMPP, it is almost always the content provider that originates the SMPP connection. The SMPP connection is a persistent, always active connection. SMS messages can be sent and received over the same connection. MM7 is an HTTP-based protocol. Connections are not persistent, but instead are initiated on demand, as required (HTTP keep-alive sockets are used to avoid re-connection overhead if many messages are being submitted in bulk). When a content provider has a message to send, it initiates a new connection (unless a keep-alive connection is available) to the mobile operator to submit the message. When the mobile operator has a message to deliver to the content provider, the mobile operator initiates a connection to the content provider. To establish an MM7 connection to a mobile operator or service provider for sending MMS messages, the following information is required at a minimum: MM7 Server URL: This will be a complete URL string, such as http://host.name:port/servlets/mm7receiver. (In some cases, only http://host.name:port/ will be required, but often there is additional path information required in the URL in order to activate the correct application at the provider.) Any required account information: Frequently your provider will specify VASPID, VASID and/or Service Code values that you will need to use. You may also be assigned a short code. Other helpful information: If they can tell you the vendor of their MMSC, this can be helpful in determining the correct protocol versions to be used. It also helps if they can tell you the MM7 version number and schema that they support. Unfortunately, frequently this information is not available to you, and a successful configuration will require some trial and error. Additionally, the mobile operator will most likely need to know your IP address so that they can open their firewall to allow you to connect to their system. In most instances, you will be identified/authorised based upon your IP address. You define an MM7 connection under the "MMSC Routing" section of NowSMS. On that screen, press the "Add" button to add a new MM7 connection. "Account Name" and "Account Description" are internal account names used only within NowSMS, so you can use any values here. "Default Sender Address" refers to the sender address that will be applied to messages that you send out. You can set a default value for this sender address here, which would normally be your short code. If "Allow Sender Address Override" is UNchecked, this means that all messages you send out will have the "Default Sender Address" applied as the sender address. If it is checked, then this means that you can specify different sender addresses when you send out messages. "Route Messages to VASP via" should be "MM7", since that is the protocol being used. "Server Address" refers to the path on their server to which you should submit messages using MM7. This is the MM7 Server URL that we referred to earlier. "Login Name" and "Password" refer to a username and password that can be sent to the server when you submit messages. If these parameters are set, NowSMS will send these parameters with "HTTP Basic Authentication" (e.g., "Authorization: Basic" header). Note that in our experience, very few providers actually use this for user identification, instead authenticating based upon your IP address and "VASP ID", "VAS ID" and/or "Service Code" values. It is not unusual for several of these fields to be left blank. If your provider has given you "VASP ID", "VAS ID" and/or "Service Code" values to use, then normally the "Login Name" and "Password" fields are left blank. Set "Connection Type" to be "To MMSC (submit format)", as you will be submitting MMS messages to the provider for outbound delivery. (The "Default" would also work, but it is safer to be explicit with this setting.) The remaining settings can probably be left at their defaults, unless the provider has given you information about their preferred MM7 version or schema. If the operator is using an Ericsson or LogicaCMG MMSC, it may be necessary to specify one of the "Non-Standard MM7 Variations" defined for these manufacturers. (Hopefully these vendors have adapted their products to use the standard MM7 protocol, but past releases have used MM7-like protocols that do not match the schemas defined by the 3GPP.) Press "Ok" to save the settings, and then when you get back to the "MMSC Routing" screen, select this route as the "Default Route" and press "Apply" to save. Now ... any messages that you submit via NowSMS will be routed via this MM7 connection. At this point, it's a good idea to go to the NowSMS web interface and try sending an MMS message. Before you do that, enable the "MMSCDEBUG.LOG" on the "Serial #" page of the NowSMS configuration dialog. Because there are so many different MM7 protocol versions and options, and confusion over MM7 Server URLs, there is a good chance that your first message sending attempt will not be successful. After you submit a message, the "MMSCDEBUG.LOG" will contain details about any message sending attempts. We can further analyse this information to make suggestions regarding configuration options. For assistance, please post a message on the NowSMS Discussion Board. Note that the above only covers sending MMS messages through your provider. It does not cover how you receive MMS messages from your provider. To receive MMS messages from the service provider, you will need to take the following steps: Recall from the discussion above, that the service provider actually initiates a connection to your NowSMS system to deliver MMS messages (or even delivery receipts). To enable such a connection to occur, it is necessary to define an account on the "MMSC VASP" page of the NowSMS configuration dialog. This defines an account on your system that your service provider will use when connecting to your system. They will then connect to you (delivering received messages via MM7) using the following URL format: http://host.name:port/mm7/account=password "host.name" is the IP address or host name of your NowSMS server. "port" is the "HTTP port" on the "MMSC" page of the configuration dialog". "account" is the "MMSC VASP" account name, and "password" is the password associated with that account. For more information on how to process any received MMS messages, please see http://www.nowsms.com/documentation/ProductDocumentation/2_way_mms_support.htm. Also, there is an ability to route received messages to a PHP script, which is described at the following link: http://www.nowsms.com/support/bulletins/tb-nowsms-016.htm -- Des NowSMS Support | |||
| Sajid Ahmed New member Username: Sajid Post Number: 20 Registered: 10-2008 |
Hi Des, Thanks a lot for brief explanation . I am waiting for the final post on http://blog.nowsms.com . Please update me on this post. I am having few more questions which i have posted with this mail and hope this would be considerable in the final post. Being a webservice developer here my understanding is. mm7 so SOAP-based XML transactions over HTTP,then we will be having WSDL publish by operator and we can write a java client/ .Net any language as its interoperable to invoke the service directly with out any middleware. Is this possible to ask operator to expose there WSDL?will they do this? I was trying to know whether mobile operator after providing mmsc information.Can we make call to there services directly(with out now/sms/mms as middleware) in some predefined xml format(by moblie operator) to send mms? My understanding for this is: For sms delivery we use nowsms/mms product so that we wont bother about smpp etc and we just do http call and nowsms/mms take care of all. I think (As said Because there are so many different MM7 protocol versions and options, and confusion over MM7 Server URLs) gateway will help us to send mms in xml format which is uderstandable by the mobile operator so we prefer to use nowsms/mms as middleware. Please correct me for my understanding for above lines. http://www2.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_ content/Submitting_MMS_Messages_MM7.htm The example in above link for mm7 specific to nowsms/mms gateway? boundary="NextPart_000_0028_01C19839.84698430" and boundary="StoryParts-74526-8432-2002-77645" are the two boundaries and no description of elements and attributes in the example. I hope this will be covered in blog. I am going through the 23140-530.doc for mm7 protocol understandings hope this will help me for what i am looking for. At this point, it's a good idea to go to the NowSMS webinterface and try sending an MMS message. Yes,bro i would like to do this to confirm whether we are having reliable connection with operator mmsc to deliver mms. But the webinterface will be using Now SMS/MMS Proprietary URL Submission via HTTP GET or POST and same with the php script too. No example to do this with mm7 call. Here comes in to picture of "MMSC VASP" which could be define by us on gateway to call by our application. Please correct me for my understanding for above lines. How to accomplish the same in gateway settings as well example to to send the mms to this url. Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 409 Registered: 08-2008 |
Hi Sajid, I do not work with WSDL, so I don't know if there is a WSDL for MM7. I can tell you that there is no reference to WSDL in the 3GPP MMS specifications.
The example is copied out of one of the 3GPP TS 23.140 specifications. We may have removed some fields to simplify the example, but other than that it is copied directly from the specifications.
Right, we don't have any script examples that generate MM7. MM7 is more complex and has more configuration options. I'm sorry, but I don't understand the rest of your questions. -- Des NowSMS Support | |||
