| Comverse WAP 1.1 and nowsms MMSC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| oren |
does any one know about problems with nowsms 4.2 ans Comverse WAP GW 1.1 ??? i'm having some trubles with my GX-10 and GD-87 and this is the wap gw i'm using. 10x, Oren | |||
| Bryce Norwood - NowSMS Support |
Is it possible to try a different WAP gateway? I normally wouldn't expect a WAP gateway to be a problem (unless the gateway does not support SAR - segmentation and reassembly correctly ... but that is not really a compatibility issue between the gateway and the MMSC, that is a compatibility issue between the gateway and the mobile device). The only WAP gateway specific issue that we've experienced was that earlier versions of our MMSC returned an "HTTP 204 No Content" response to the "m-notifyresp-ind" message sent from client to MMSC after an MMS message is retrieved. When a WAP gateway tries to encode the "204 No Content" message, the problem is that the WSP PDU that the WAP gateway generates has to have a "Content-type" field. With no content or content type, how should this be encoded? It is not clear from the WAP specifications. Anyway, the Panasonic GD87 did not like the way many gateways encoded this WSP PDU reply, and claimed the WSP PDU was corrupt. We made a change to the MMSC to change this particular response. I guess the next step that I'd recommend is to try to determine if the WAP gateway is a factor. Is it possible to try another WAP gateway? Maybe even try ours at www.wap3gx.com? | |||
