| Connectivity to operator MMSC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hi, We are a customer of NowSMS,and we are connecting to an operator MMSC by defining a routing ruke in MMSC routing section [MMSC Running on Port 8080]. But when i send an MMS from the web interface i get the following in the output log ------------------- 15:58:17:750 [7] ThreadProcessVASPQ: Outbound route XXXX: setting retry for 30133AC0.MMS 16:01:32:828 [7] InetServerConnect: Connected to XXX.XX.XXXX.XX (XXX.XXXX.XXX.XXX:XXXX) 16:01:32:828 [7] ThreadProcessVASPQ: POST /mm7 HTTP/1.1 Host: XX.XX.XX.XX:XXX SOAPAction: "" Content-Length: 1351 Content-Type: multipart/related; boundary="---mime-boundary-D2EEA61C.AC99799D---"; type="text/xml"; start="<mm7_msg>" Connection: close 16:01:32:828 [7] ThreadProcessVASPQ: -----mime-boundary-D2EEA61C.AC99799D--- Content-Type: text/xml; charset=utf-8 Content-ID: <mm7_msg> <?xml version="1.0" ?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-M M7-1-2" env:mustUnderstand="1"> 20050513160132-386D6D5B@XXXXX.XXX </mm7:TransactionID> </env:Header> <env: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> </SenderIdentification> <Recipients> <To> <Number>XXXXXXX</Number> </To> </Recipients> <Priority>Normal</Priority> <DeliveryReport>False</DeliveryReport> <ReadReply>False</ReadReply> <Subject>Test</Subject> <Content href="cid:mms_cid"/> </SubmitReq> </env:Body> </env:Envelope> -----mime-boundary-D2EEA61C.AC99799D--- Content-Type: multipart/mixed; boundary="---mime-boundary-D54D77DE.B83630DF---" Content-ID: <mms_cid> -----mime-boundary-D54D77DE.B83630DF--- Content-Type: text/plain Content-ID: <427F23A8.txt> Content-location: 427F23A8.txt Test -----mime-boundary-D54D77DE.B83630DF----- -----mime-boundary-D2EEA61C.AC99799D----- 16:01:32:921 [7] HttpResponseWait: Ok 16:01:32:921 [7] ThreadProcessVASPQ: mm7 - got unknown response 16:01:32:921 [7] ThreadProcessVASPQ: HTTP/1.1 404 Not Found Server: Resin/2.1.6 Cache-Control: no-cache Expires: Thu, 01 Dec 1994 16:00:00 GMT Content-Type: text/html Content-Length: 165 Date: Fri, 13 May 2005 07:59:52 GMT <title>404 Not Found</title> <h1>404 Not Found</h1> /mm7 was not found on this server. <p /><hr /> <small> Resin 2.1.6 (built Fri Nov 8 08:18:18 PST 2002) </small> 16:01:32:921 [7] ThreadProcessVASPQ: Outbound route XXX: setting retry for 79BB8C56.MMS -------------------- The MMSC guy claims he is getting only upto the section type="text/xml"; start="<mm7_msg>". Does the Connection: close section mean anything Pls advise. Regards | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4518 Registered: 10-2002 |
The server is returning an HTTP "404" error, indicating that "/mm7" is not a valid URL on the server. So I don't think that it is an issue that the MMSC is only receiving part of the mesage. Instead, I think you don't have the correct URL for connecting to the MMSC. I often see this "Server: Resin/x.x.x" response when people are connecting to an Ericsson MMSC. And you probably need a URL like "/servlets/messagerouter" to connect. (And in this case, you also would need to specify "Ericsson MM7" as the type instead of regular "MM7".) Regarding "Connection: close", that is just an HTTP header that we specify to tell the server that we intend to close the connection after we receive the server's response. -bn | |||
