×

Discussion Board

Results 1 to 2 of 2
  1. #1
    Registered User
    Join Date
    Jan 2006
    Location
    Grenoble, France
    Posts
    3

    MMS SDK : missing transaction id header

    Hello,

    I am curently using the NMSS SDK 1.5 for sending and receiving MMS with the MM7 protocole (on a MMS Gateway).

    When I try to send a MMS, the MMS sending succed, but I always have an error specifying : "missing transaction id header". As this error occur after the MMS sending, I can receive the MMS on my mobile phone.

    When I try to receive a MMS, the same error occure, but this time it is on the begining of the transmission and it faille the transmission. So I Can't see a part of the incomming MMS.
    This error appened when I try to reply to an incomming message on my mobile as well as when I make a new one.


    I have launched the debug logging and here is one of the repports :
    09:49:51,550 [INFO] com.nokia.mobile.services.driver.mms.mm7.MMSSender: missing Content-Id attribute, setting it to id_1
    09:49:51,550 [INFO] com.nokia.mobile.services.driver.mms.mm7.MMSSender: missing Content-Transfer-Encoding attribute, setting it to binary
    09:49:56,925 [ERROR] com.nokia.mobile.services.driver.mms.mm7.MMSSender: remote call failed
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
    faultSubcode:
    faultString: missing transaction id header
    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}stackTrace: AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
    faultSubcode:
    faultString: missing transaction id header
    faultActor:
    faultNode:
    faultDetail:

    missing transaction id header
    at com.nokia.mobile.services.driver.mms.mm7.TransactionIDHandler.getTransactionID(TransactionIDHandler.java:87)
    at com.nokia.mobile.services.driver.mms.mm7.TransactionIDHandler.invoke(TransactionIDHandler.java:61)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:193)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
    at org.apache.axis.client.Call.invoke(Call.java:2553)
    at org.apache.axis.client.Call.invoke(Call.java:2248)
    at org.apache.axis.client.Call.invoke(Call.java:2171)
    at org.apache.axis.client.Call.invoke(Call.java:1691)
    at com.nokia.mobile.services.driver.mms.mm7.w2j.MMSServiceSOAPBindingStub.submit(MMSServiceSOAPBindingStub.java:407)
    at com.nokia.mobile.services.driver.mms.mm7.MMSSender.send(MMSSender.java:266)
    at com.nokia.mobile.services.driver.mms.mm7.MM7Engine.send(MM7Engine.java:321)
    at MMS.SendMMS.Send(SendMMS.java:176)

    I also have the SOAP request from Orange :
    - Requete SOAP :

    <?xml version="1.0" encoding="UTF-8"?>

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

    <soapenv:Header>

    <ns1:TransactionID soapenv:mustUnderstand="1" xsi:type="xsd:string" xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">597154EB74DFB70FBF1C5DEC33B3F47F</ns1:TransactionID>
    </soapenv:Header>
    <soapenv:Body>
    <SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
    <MM7Version>5.3.0</MM7Version>
    <SenderIdentification>
    <VASPID>mmsorangevasp</VASPID>
    <VASID>80050</VASID>
    <SenderAddress>
    <RFC2822Address displayOnly="false">opp@orangefrance.com</RFC2822Address>
    </SenderAddress>
    </SenderIdentification>
    <Recipients>
    <To>
    <Number displayOnly="false">350388248010</Number>
    </To>
    </Recipients>
    <MessageClass>Informational</MessageClass>
    <DeliveryReport>true</DeliveryReport>
    <ReadReply>false</ReadReply>
    <Priority>Normal</Priority>
    <Subject>MMS Vidéo</Subject>
    <DistributionIndicator>true</DistributionIndicator>
    <Content allowAdaptations="false" href="cid:BA80981D589E6F46C14F80958544B6DF"/>
    </SubmitReq>
    </soapenv:Body>
    </soapenv:Envelope>

    It may come from my MM7.properties file, but I can't find what is wrong 'especially for the incomming messages).

    Here are the only lines I am using in the .PROPERTIES file :
    mmsc.Factory.Implementation=com.nokia.mobile.services.driver.mms.mm7.MM7DriverFactory

    mmsc.Engine.MM7.VASPID=QQuintesens20983
    mmsc.Engine.MM7.VASID=<>
    mmsc.Engine.mode=originating_terminating
    mmsc.Engine.MMSCURL=http://***:***@"MMS Gateway IP"
    mmsc.Engine.auth.preemptive=true
    mmsc.Engine.axis.server.port=80
    mmsc.Engine.axis.max.concurrent.requests=-1
    mmsc.Engine.dropMultipart=false
    mmsc.Engine.proxy.host="MMS Gateway IP"
    mmsc.Engine.proxy.port=80
    mmsc.Engine.ssl.enabled=false


    mmsc.Message.FROM=20983/TYPE=PLMN
    mmsc.Message.TOAddress=+33679632592/TYPE=PLMN
    mmsc.Message.Subject=Quintesens test msg
    mmsc.Message.Priority=Normal
    mmsc.Message.DeliveryReport=false
    mmsc.Message.ReadReport=false
    mmsc.Message.MessageClass=Auto

    mmsc.Message.Header.X-MM7-ReplyCharging=false
    mmsc.Message.Header.X-MM7-ReplyChargingSize=0
    mmsc.Message.Header.X-MM7-ReplyDeadline=P90D
    mmsc.Message.Header.X-MM7-ChargedParty=
    mmsc.Message.Header.X-MM7-AllowAdaptations=true
    mmsc.Message.Header.X-MM7-DistributionIndicator=
    mmsc.content-handler.class.text=com.nokia.mobile.services.api.mms.util.MMSTextHandlerImpl
    mmsc.content-handler.content-type.text.0=text/*
    mmsc.content-handler.content-type.text.1=application/smil
    mmsc.content-handler.class.default=com.nokia.mobile.services.api.mms.util.MMSDefaultHandlerImpl


    mmsc.Factory.file-extension.txt=text/plain
    mmsc.Factory.file-extension.smil=application/smil

    Thank you for all of you that wil try to help me (and even more for those who find the solution of my problem
    Last edited by vincent.czerniak; 2006-01-24 at 15:16.

  2. #2
    Registered User
    Join Date
    Jan 2006
    Location
    Grenoble, France
    Posts
    3

    Re: MMS SDK : missing transaction id header

    Anybody have ever had to deal with this problem ?

    That's annoying.

Similar Threads

  1. SyncML Client APIs missing from Series 60 SDK 2.0
    By otsov in forum Symbian Tools & SDKs
    Replies: 0
    Last Post: 2004-04-08, 09:49
  2. MMS SDK in C/C++
    By uvatbc in forum Multimodecards
    Replies: 0
    Last Post: 2003-12-30, 15:35
  3. Transaction Id in the MMS Library
    By cmingoia in forum General Messaging
    Replies: 1
    Last Post: 2002-09-17, 10:56
  4. Viewing MMS with Symbian SDK
    By alarkin77 in forum Symbian Tools & SDKs
    Replies: 0
    Last Post: 2002-05-31, 09:40
  5. Replies: 1
    Last Post: 1970-01-01, 02:00

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×