Problems connecting to operators MMSC

Problems connecting to operators MMSC SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Problems connecting to operators MMSC « Previous || Next »
Author Message
Shimon
New member
Username: Daffy

Post Number: 1
Registered: 06-2004
Posted on Wednesday, June 02, 2004 - 04:33 pm:   

When connecting to an operators MMSC I should use either absolute or relative path for posting.

Example:
POST /mm7 HTTP/1.1
Host: mmsc.xxx.com

or

POST http://mmsc.xxx.com/mm7 HTTP/1.1

I should connect at port 8090 which is listening for MM7 http connections.

When setting this up I have been using the "MMSC Routing" tab and using MM7 to route messages to VASP. In "Server address" I put http://mmsc.xxx.com:8090/mm7
This will give me errors like: (debug from operator)


--> 0 mums1://node=mms1/http=xxx-HTTP-8090
POST /mm7 HTTP/1.0
Authorization: Basic SU5GT1NZUzo=
Host: mmsc.xxx.com:8090
SOAPAction: ""
Content-Length: 1327
Content-Type: multipart/related; boundary="---mime-boundary-481CA7A8.F0721C29---"; type="text/xml"; start="<mm7_msg>"
Connection: close

and in the end

The requested URI is not found on the server

I think its because of the port number in the "Host" header. The application should connect to the operators MMSC on port 8090 but I don't think it should be in the headers. Is there any other way to configure this or have I missed something?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2803
Registered: 10-2002
Posted on Thursday, June 10, 2004 - 05:13 pm:   

Hi Shimon,

It is normal for the port number to be in the "Host:" header.

At least if you look at HTTP requests that are generated by Internet Explorer, you will find that the "Host:" header includes a port number when connecting to a server on a non-default port.

Regarding relative vs. absolute paths, standard behaviour is to use an absolute path only when connecting to a proxy server. When connecting directly to a content server, a relative path is used.

I suspect that you don't have the correct URL for the post.

-bn

Login Login / Register Logout Logout Search Last 30 Days Topics Topics