Mixed enviormnet with new and old phones (new MMSC install)

Mixed enviormnet with new and old phones (new MMSC install) SearchSearch
Author Message
John Lancelot
New member
Username: Jlancelotgmailcom

Post Number: 1
Registered: 05-2009
Posted on Monday, May 04, 2009 - 08:16 pm:   

I was able to setup the MMSC with our GPRS network only with the nowsms 2008 version.

The config I send via OMA

<wap-provisioningdoc>

<characteristic type="BOOTSTRAP">
<parm name="NAME" value="mms.awc"/>
<parm name="PROXY-ID" value="mms.awc_Proxy"/>
</characteristic>

<characteristic type="NAPDEF">
<parm name="NAME" value="mms.awc"/>
<parm name="NAPID" value="mms.awc_NAPID"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAP-ADDRESS" value="awc"/>
<parm name="NAP-ADDRTYPE" value="APN"/>
</characteristic>

<characteristic type="PXLOGICAL">
<parm name="NAME" value="mms.awc"/>
<parm name="PROXY-ID" value="mms.awc_Proxy"/>
<parm name="STARTPAGE" value="http://mms.alaskawireless.com/mms=mms"/>

<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="mms.awc_PhProxy"/>
<parm name="PXADDR" value="209.165.145.118"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="mms.awc_NAPID"/>

<characteristic type="PORT">
<parm name="PORTNBR" value="80"/>
</characteristic>
</characteristic>
</characteristic>

<characteristic type="APPLICATION">
<parm name="APPID" value="w2"/>
<parm name="NAME" value="mms.awc"/>
<parm name="TO-PROXY" value="mms.awc_Proxy"/>

<characteristic type="RESOURCE">
<parm name="NAME" value="mms.awc"/>
<parm name="URI" value="http://mms.alaskawireless.com/mms=mms"/>
<parm name="STARTPAGE"/>
</characteristic>
</characteristic>

<characteristic type="APPLICATION">
<parm name="APPID" value="w4"/>
<parm name="NAME" value="mms.awc"/>
<parm name="TO-PROXY" value="mms.awc_Proxy"/>
<parm name="ADDR" value="http://mms.alaskawireless.com"/>
</characteristic>
</wap-provisioningdoc>

This works fine to send and receive MMS between Nokia E71 and E50 without any issues. But when I use the older model phones such as Nokia 6010 etc... with the below OMA settings or above OMA settings it doesn't work

<CHARACTERISTIC-LIST>

<CHARACTERISTIC TYPE="ADDRESS">
<PARM NAME="BEARER" VALUE="GPRS"/>
<PARM NAME="PROXY" VALUE="209.165.145.118"/>
<PARM NAME="PORT" VALUE="80"/>
<PARM NAME="GPRS_ACCESSPOINTNAME" VALUE="awc"/>
<PARM NAME="PPP_AUTHTYPE" VALUE="PAP"/>
<PARM NAME="ISP_NAME" VALUE="mms.awc"/>
</CHARACTERISTIC>
<CHARACTERISTIC TYPE="URL" VALUE="http://mms.alaskawireless.com/mms=mms"/>
<CHARACTERISTIC TYPE="MMSURL" VALUE="http://mms.alaskawireless.com"/>

<CHARACTERISTIC TYPE="NAME">
<PARM NAME="NAME" VALUE="mms.awc"/>
</CHARACTERISTIC>

<CHARACTERISTIC TYPE="BOOKMARK">
<PARM NAME="NAME" VALUE="mms.awc"/>
<PARM NAME="URL" VALUE="http://mms.alaskawireless.com/mms=mms"/>
</CHARACTERISTIC>
</CHARACTERISTIC-LIST>

I can see a wireshark trace at my GPRS/NowSMS that these old phones are requesting WTP+WSP connections at UDP 9201. I did not see any options under the APN settings in the phone to change the WAP port. Where as the new phones did request HTTP to the NowSMS. is there any way I can force the phones or the NowSMS and take care of these old phone situation? Or do I need to have a separate wap gateway as well?

Now, I have only installed the NowSMS2008 as the Internal MMSC. I don't have any WAP gateway and was planning not use one but make everything work with the NowSMS2008 version. How's it possible?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 734
Registered: 08-2008
Posted on Monday, May 04, 2009 - 08:28 pm:   

Hi John,

If the phones are talking WTP+WSP, then that requires a WAP gateway ... there's no real way to get around that.

Generally speaking, if the phone doesn't let you change the port (or it only gives options like connection-oriented, connection-less, secure), then that sounds like WTP+WSP is the only option.

Even in the W-HTTP/W-TCP environment, the NowSMS MMSC does rely on the WAP gateway for providing the sender MSISDN. (More details on this here: http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm)

NowWAP is pretty simple to setup for that purpose ... the only difficult part is configuring your access servers to route the RADIUS accounting information to NowWAP.

--
Des
NowSMS Support
John Lancelot
New member
Username: Jlancelotgmailcom

Post Number: 2
Registered: 05-2009
Posted on Monday, May 04, 2009 - 08:34 pm:   

Des, that was a fast response. Appreciate that.

One last question on this thread.

Can both NowSMS and NowWAP can be collocated on a same machine with only one IP address.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 736
Registered: 08-2008
Posted on Monday, May 04, 2009 - 08:47 pm:   

Hi John,

Every once in awhile I get lucky with good timing on a response. I wish that could be more frequent.

The same machine for NowWAP and NowSMS is not a problem, as long as you're not planning on thousands of concurrent transactions.

To allow you to have some future flexibility, we usually recommend that you don't tie both to the same IP address ... at least not in your published settings.

You can still use a single IP address, but your published settings for the MMSC should use a host name instead of an IP address. This gives you more future flexibility if you need to reconfigure.

As I read my explanation, it sounds a little confusing.

The WAP gateway generally needs to be referred to by its IP address, so the settings will refer to it by IP address.

But for the MMSC, refer to it by a host name in its URL (just like in your provisioning settings above).

That way, if you do have a future need to separate the two, it is not as difficult.

--
Des
NowSMS Support