MMS XML parameters | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
Author | Message | ||||
Waleed Unregistered guest |
Dear Bryce, I am trying to connect NOWSMS on the operator MMSC, and they said that NOWSMS is not compitable with their MMS services since i could not send and recieve MMS. After long trace, they said NOWSMS should support 3 additional parameters: ChargedParty ,ChargedPartyID ,LinkID to make the service running. Would you please help me, and let me know how can add these parameters. Thanks Waleed | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5213 Registered: 10-2002 |
Hi Waleed, I need more detail about how you need to have these parameters set. "Linked ID" is only used if you are replying to a message. And I do not understand how this would be required. We could add parameters for "Charged Party" and "Charged Party ID", but you would need to be able to configure the appropriate values to be included in these fields. Do you know how your operator wants these parameters set? Would they be set the same for every message, or do they need to be set on a per message basis? Are you sure that this is the problem? I'd be interested in seeing an MMSCDEBUG.LOG that shows current connection attempts to see if the response from the MMSC gives any clues. -bn | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5214 Registered: 10-2002 |
Waleed, On second thought, let's go ahead and try out their theory. I've uploaded an update to http://www.nowsms.com/download/min.zip. And it includes the ability to add additional MM7 XML element/value pairs, as described below: * MMSC/MM7 Outbound Route: Add configuration support for additional XML elements in the MM7 submit request. To add additional XML elements to the MM7 submit request, edit VASPOUT\vaspname\VASP.INI. Create a section titled [AddtionalSettings], and then include the XML name/value pairs in INI file format. For example, name=value under the [AdditionalSettings] header would add <name>value</name> to the MM7 submit XML. So, if you know what values to use for "ChargedParty" and "Charged PartyID", you could include this in the VASP.INI: [AdditionalSettings] ChargedParty=xxxxx ChargedPartyID=xxxxx -bn | ||||
Hussam Dahbour New member Username: Hussam83 Post Number: 4 Registered: 08-2005 |
Bryce, Can we change the structur of XML Schema, I need to but the prt: <SenderAddress><Number>99809</Number></SenderAddress> outside the tag <SenderIdentification> Is that possible, and if it possible how we can do it? Thanks Hussam Dahbour | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5219 Registered: 10-2002 |
Hi Hussam, We don't have the flexibility to easily make that type of adjustment in the XML, as unfortunately, this type of interface doesn't lend itself well to the use of customisable templates. Every MM7 schema that has been published by 3GPP has the "SenderAddress" field within the "SenderIdentification" tag. If you are interfacing with an MMSC that has different requirements, then I would like to see any technical documentation that you have regarding the MM7 interface for this MMSC. (Or examples that have been provided.) We have implemented configuration options for MMSCs that implemented their own non-standard versions of MM7 (such as Ericsson and AnnyWay). And we could do that again, but I'd like to see more detailed information about what is required, because usually the adjustments required to interoperate with MMSCs that failed to realise that the 3GPP had actually published an MM7 standard can be a bit invovled. -bn | ||||
Hussam Dahbour New member Username: Hussam83 Post Number: 5 Registered: 08-2005 |
Bryce, I need to put the service code outside the <userIdentification> tag which is standard in 3GPP The operator I am connected to wants that. NOWSMS: <SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-3"> <MM7Version>6.7.0</MM7Version> <SenderIdentification> <VASPID>900000</VASPID> <VASID>0099</VASID> <ServiceCode>809</ServiceCode> <SenderAddress><Number>99809</Number></SenderAddress> </SenderIdentification> <Recipients> <To> <Number>962788002349</Number> </To> </Recipients> <Priority>Normal</Priority> <DeliveryReport>True</DeliveryReport> <ReadReply>True</ReadReply> <Subject>test</Subject> <Content href="cid:mms_cid"/> </SubmitReq> 3GPP: <SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"> <MM7Version>5.6.0</MM7Version> <SenderIdentification> <VASPID>TNN</VASPID> <VASID>News</VASID> </SenderIdentification> <Recipients> <To> <Number>7255441234</Number> </To> </Recipients> <ServiceCode>gold-sp33-im42</ServiceCode> <LinkedID>mms00016666</LinkedID> <MessageClass>Informational</MessageClass> <TimeStamp>2002-01-02T09:30:47-05:00</TimeStamp> <DeliveryReport>true</DeliveryReport> <Priority>Normal</Priority> <Subject>News for today</Subject> <ChargedParty>Sender</ChargedParty> <DistributionIndicator>true</DistributionIndicator> <Content href="cid:SaturnPics-01020930@news.tnn.com" allowAdaptations="true"/> </SubmitReq> | ||||
Waleed Unregistered guest |
Dear Bryce, Thanks alot for your support, sorry if i am posting too much ;) The operator MMSC is HUAWEI, and its on 3gpp standard. I have tryed to update VASP.ini with additional setting but errors 4004 and 4007 comes. ( AUTHORITY Faliure and Field 'Sender' must be filled )... Kindly, Find below their XML standardm and attached success MMS sending log from extenal application they are using: <env:Body> <SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"> <MM7Version>5.6.0</MM7Version> <SenderIdentification> <VASPID>TNN</VASPID> <VASID>News</VASID> </SenderIdentification> <Recipients> <To> <Number>7255441234</Number> <RFC2822Address displayOnly="true">7255442222@OMMS.com</RFC2822Address> </To> <Cc> <Number>7255443333</Number> </Cc> <Bcc> <RFC2822Address>7255444444@OMMS.com</RFC2822Address> </Bcc> </Recipients> <ServiceCode>gold-sp33-im42</ServiceCode> <LinkedID>mms00016666</LinkedID> <MessageClass>Informational</MessageClass> <TimeStamp>2002-01-02T09:30:47-05:00</TimeStamp> <EarliestDeliveryTime>2002-01-02T09:30:47-05:00</EarliestDeliveryTime> <ExpiryDate>P90D</ExpiryDate> <DeliveryReport>true</DeliveryReport> <Priority>Normal</Priority> <Subject>News for today</Subject> <ContentClass>video-rich</ContentClass> <DRMContent>true</DRMContent> <ChargedParty>Sender</ChargedParty> <DistributionIndicator>true</DistributionIndicator> <Content href="cid:SaturnPics-01020930@news.tnn.com" allowAdaptations="true"/> </SubmitReq> </env:Body>
| ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5228 Registered: 10-2002 |
Hussam, Thank you. That clarifies the matter. NowSMS is not following the MM7 schema correctly for the "ServiceCode" element. I will post a patch to correct this problem shortly. -bn | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5229 Registered: 10-2002 |
Hussam, Thanks again for the clarification. An update to fix this "ServiceCode" element placement is available for download at http://www.nowsms.com/download/min.zip. -bn | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5230 Registered: 10-2002 |
Hi Waleed, Don't worry about posting too much. I just want to try to keep the postings organised so that they are not in multiple threads ... as that makes it too difficult to troubleshoot and determine what has been tried, and what has not been tried. I think Hussam identified the problem above. When a "ServiceCode" is specified, we were not encoding it properly in the XML. See the update referenced in the message above, and this will correct the "ServiceCode" problem which might resolve your troubles. -bn | ||||
Hussam Dahbour New member Username: Hussam83 Post Number: 6 Registered: 08-2005 |
Tahnk you Bryce I will test the new patch and update you with results. | ||||
Waleed Unregistered guest |
Dear Bryce, Man, Thanx alot for you .. You are really great.. The patch solved Sending MMS probelm, It works fine now. Thanks again Waleed | ||||
Hussam Dahbour New member Username: Hussam83 Post Number: 7 Registered: 08-2005 |
Bryce, It is working Thank you very much. | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5231 Registered: 10-2002 |
Woohoo! |