| Bugs in BETA 2 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Bryce Norwood - NowSMS Support |
Here's a list of bugs that we have found so far in the v5.0 beta 2 release: 1.) If you have a "Default Route" defined on the "MMSC Routing" page of the configuration dialog, the web interface will ignore this setting when you send an MMS message. To work around this bug, edit the MMSC Routing definition for the desired default route and add "*" to the "Route messages to this account for recipient" field. 2.) Problems connecting to some operator WAP gateways (for MM1 sending, or for receiving messages from an operator connection). This problem was observed on Vodacom in South Africa and Westel in Hungary. An updated MMSWAP.DLL for beta 2 is available at www.nowsms.com/download/mmswap.zip. 3.) Inbound MM7 message submissions result in a corrupt MMS message being sent out when the latest version of the Openwave MM7 Java libraries are used. This problem could also occur with any MM7 submissions that include a "Content-Disposition" header in the multipart MIME data. (An updated MMSC.EXE for beta 2 is available to correct this problem, please e-mail nowsms@now.co.uk if you need this update.) | |||
| Bryce Norwood - NowSMS Support |
4.) Outbound MM7 connections initiated by the gateway (MM7 connections defined on the "MMSC Routing" page) do not include a "Host:" header, causing a problem if the destination web server is a multi-homed host. (An updated MMSC.EXE for beta 2 is available to correct this problem, please e-mail nowsms@now.co.uk if you need this update.) | |||
| Bryce Norwood - NowSMS Support |
5.) Defining an "MMSC Routing", where the routing is defined to "Convert to a Multimedia WAP Push" is not working properly. (An updated MMSC.EXE for beta 2 is available to correct this problem, please e-mail nowsms@now.co.uk if you need this update.) | |||
| Bryce Norwood - NowSMS Support |
6.) Problems with OMA settings, especially when using the IMSI as a network PIN. See this thread for details: http://support.nowsms.com/discus/messages/485/493.html | |||
| Bryce Norwood - NowSMS Support |
7.) "To:" headers are not properly constructed when routing via MM4 interface (/TYPE=PLMN not included in phone number). See this thread for details: http://support.nowsms.com/discus/messages/485/720.html 8.) If the MMSC is bound to a specific IP address, outbound VASP connections (MM7, MM4, EAIF) could originate from any IP address bound to the PC, not just the one specified for the MMSC. See this thread for details: http://support.nowsms.com/discus/messages/485/722.html | |||
| Bryce Norwood - NowSMS Support |
9.) "Multimedia WAP Push" message corrupts messages that include "[" or "]" characters in text fields. See this thread for details: http://support.nowsms.com/discus/messages/1/721.html | |||
