| VASP outgoing port? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Kevin O'Farrell Unregistered guest |
Bryce, Is there anyway to change the port number for a vasp connection. I have the MMSC on two servers running on port 8081 but the VASP connection appears (from the debug file) to connection on 80. Is there any way I can change this? | |||
| Kevin O'Farrell Unregistered guest |
I added :8081 to the Ip address in the MMSC Routing tab and it seemed to work. However the mmsc debug file shows the following error - 10:36:34:664 [7] ThreadProcessVASPQ: Outbound route xxxxxxxxxxx: setting retry for 41B5D3A0.mms xx:xx:xx:xx [7] InetServerConnect: Connected to xx.xx.xx.xx (xx.xx.xx.xx:8081) 10:38:36:780 [7] ThreadProcessVASPQ: POST / HTTP/1.1 Authorization: Basic bW1zOmlybDQwNzY= Host: xx.xx.xx.xx:8081 SOAPAction: "" Content-Length: 7281 Content-Type: multipart/related; boundary="---mime-boundary-51AD5846.754E6F47---"; type="text/xml"; start="<mm7_msg>" Connection: close 10:38:36:780 [7] ThreadProcessVASPQ: -----mime-boundary-51AD5846.754E6F47--- 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-MM7-1-2" env:mustUnderstand="1"> 20041208103836-20537C05@bigsystem </mm7:TransactionID> </env:Header> <env:Body> <DeliverReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"> <MM7Version>5.3.0</MM7Version> <Recipients> <To> <Number>0877437361</Number> </To> </Recipients> <Priority>Normal</Priority> <Subject>Multimedia Message</Subject> <Content href="cid:mms_cid"/> </DeliverReq> </env:Body> </env:Envelope> -----mime-boundary-51AD5846.754E6F47--- Content-Type: multipart/related; type="application/smil"; start="<287573462>"; boundary="---mime-boundary-498E5108.72108D89---" Content-ID: <mms_cid> -----mime-boundary-498E5108.72108D89--- Content-Type: image/jpeg; name="Image_07.jpg" Content-location: Image_07.jpg Content-Transfer-Encoding: base64 /9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0aHBwg ..... FqbuxSpUnfTf6Ogz/9k= -----mime-boundary-498E5108.72108D89--- Content-Type: application/smil; charset=utf-8; name="pres.smil" Content-ID: <287573462> <smil> <head> <layout> <root-layout width="176" height="208"/> <region id="Image" width="160" height="120" top="5" left="8" fit="meet"/> </layout> </head> <body> <par dur="5000ms"> <img region="Image" src="Image_07.jpg"/> </par> </body> </smil> -----mime-boundary-498E5108.72108D89----- -----mime-boundary-51AD5846.754E6F47----- 10:38:37:972 [7] HttpResponseWait: Ok 10:38:37:972 [7] ThreadProcessVASPQ: mm7 - got unknown response 10:38:37:972 [7] ThreadProcessVASPQ: HTTP/1.0 500 Internal Error Content-Type: text/html Connection: close Date: Wed, 08 Dec 2004 10:53:10 GMT Expires: Wed, 08 Dec 2004 10:53:10 GMT <HTML><HEAD><TITLE> Unknown Request </TITLE></HEAD><BODY><H1> Unknown request: content type is unknown </H1></BODY></HTML> 10:38:38:002 [7] ThreadProcessVASPQ: Outbound route xxxxxxxxxx: setting retry for 41B5D3A0.mms | |||
| Kevin O'Farrell Unregistered guest |
Any update on this? We're stuck until we can get a solution. I've also tried MM1 and while it successfully delivers the remote NoWSMS server reports "no find alias file for mms". | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3824 Registered: 10-2002 |
Add /mm7 to the URL ... that tells the MMSC that it is processing an MM7 connection. Otherwise, it assumes that it is processing an MM1 connection. | |||
