Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce
Post Number: 1500
Registered: 10-2002
| | Posted on Wednesday, December 31, 2003 - 08:54 pm: | |
A patch has been released for the Now SMS/MMS Gateway v5.0.
The patch is available for download at http://www.nowsms.com/download/NowSMS5-Patch4.zip.
This patch addresses specific problems encountered in the v5.0 release, which are detailed below. This patch is cumulative, so patch 4 includes all of the fixes included in the previous patches.
Patch 4: December 30, 2003
- SMPP: Fix for "Address Range" configuration parameter not being passed to the SMPP bind.
- Fix for problem connecting to WAP gateway over GPRS in some configurations where WAP gateway redirects are used (most notably with O2 UK).
- Improve SMS receiving support to address a problem receiving binary SMS messages with the Nokia 30. For more information, see http://support.nowsms.com/discus/messages/485/1477.html.
- Improve SMS receiving support to address a problem receiving SMS messages using the Eagletec GSM/GPRS CF Card.
- MMS/Multimedia WAP Push: Add configuration parameter to delete dynamically generated links (such as those used when sending MMS or Multimedia WAP Push) after they are accessed. To enable this feature, edit MMSC.INI, and under the [MMSC] section header, add ExpireDynamicLinks=##, where ## is the number of minutes after the link is first accessed before it should be automatically deleted.
- Fix for MMS Accounting callbacks not being called when MMS message is routed to a VASP.
- MM4: Configuration setting added for routing MM4 acknowledgements to the proper SMTP host. The configuration dialogs now allow a setting for MM4 Ack's to be routed via a defined MM4 MMSC Outbound Route.
- Fix for "X-Mms-Read-reply" header not being maintained through an MM4 connection.
- When routing MMS to SMTP, honor delivery report and read reply flags to attempt to request same in the resulting SMTP message.
- MMSC: Add MMSC.INI configuration setting, under [MMSC] section header, DebugLogDirectory=d:\path\ can be used to set the path for the MMSCDEBUG.LOG.
- MMSC: Fix for logging problems when a user account defined under "SMS Users" submits MMS messages via SMTP.
- MM7: Update XML schema reference to REL5-MM7-1-2 from REL5-MM7-1-0.
- WAP Multimedia Push: Fix for a problem with URL links to multimedia content files that include a space in the filename.
- Content Adaptation was not properly downloading User Agent profiles for "Profile:" headers that included quotes around the URL, such as the Alcatel OT535.
- MM7: Fix for XML name space error in MM7 messages generated by the gateway. We were following MM7 examples in 3GPP TS 23.140 version 5.4.0, but there was an XML name space error that was corrected by later versions of the specification.
- MMS connections to operator MMSC over GPRS/WAP: Improvements in receive logic to better overcome from transmission error retries.
- MM4: If an Ack is requested, bu tthe X-Mms-Originator-System header is not defined, send the Ack to the Sender address.
Patch 3: November 19, 2003
- Add the ability to route MMS messages to different outbound "MMSC Routing" defintions, based upon the sender address specified in the MMS message (similar to how this already works for routing SMS messages). When routing an MMS message, NowSMS will look for a match between the sender address in the message, and the default sender address defined for any "MMSC Routing" definitions. When a match is found, the MMS message will be routed outbound via the specified "MMSC Routing".
- Add a configuration setting to enable SMS over GPRS on a per modem basis.
- When testing the connection to an HTTP SMSC, do not generate a GET request, only verify that it is possible to connect to the server.
- When sending out concatenated SMS messages, use care to ensure that all segments of a message get routed through the same SMSC connection.
- 2-way SMS: If command returns a blank response, do not send a reply message via SMS.
- MMS connections to operator MMSC over GPRS/WAP: Fix for bug that did not like any leading "0" digits within an IP address (e.g., 213.48.20.10 would work, but 213.048.020.010 would fail).
- Added SMSGW.INI configuration parameter, under section header that defines an SMPP connection. The setting LongSMSAlt=Yes enables alternate encoding logic for submitting long text messages. If you are connecting to an SMPP based SMSC, and receive garbage messages when sending long text messages, enable this setting.
- Add configuration parameter support for forcing messages routed through an MM7 "MMSC Routing" connection to either mm7_submit.REQ or mm7_deliver.REQ format. (By default, the message type defaults to the message type that was set in the message that was received by the gateway. E.g., if an MMS message was received over a GSM/GPRS modem connection, and routed out via MM7, the message would be in mm7_deliver.REQ format. If a message was submitted to NowSMS for delivery, and routed out via MM7, the message would be in mm7_submit.REQ format.) To force all messages routed out via an MM7 connection to mm7_submit.REQ format, edit VASPOUT\vaspname\VASP.INI, and under the [VASP] section header, add mm7SubmitReq=Yes. Similarly, to force messages to to mm7_deliver.REQ format, edit VASPOUT\vaspname\VASP.INI, and under the [VASP] section header, add mm7DeliverReq=Yes.
Patch 2: November 1, 2003
- SMS Gateway was not properly encoding the Euro symbol. Messages that included a Euro character were being sent out using Unicode encoding when this was not necessary.
- Fix for MM1/EAIF "MMSC VASP" account parsing. VASP name would appear corrupted in the log files.
- Update MMSCTYPE.INI to define a default MIME type for the ".dm" extension as "application/vnd.oma.drm.message".
- MM4/SMTP Receiver: Allow MM4/SMTP receiver to properly handle "application/vnd.oma.drm.message" content.
- MM7 Receiver: Fix bug that prevented messages that included binary content with embedded NULL characters from being processed. When including binary content in an MM7 message, it is recommended that you include a "Content-Length:" header in any body parts that include binary content.
- Fix for a problem where text of inbound received messages could be truncated if an "@" character appeared on an 8 character boundary.
- The following MM4 headers were not properly encoded as "quoted strings": X-Mms-Transaction-ID and X-Mms-Message-ID.
- Fix for MM1/EAIF "MMSC VASP" account requiring a username and password. (Account name as IP address was not working properly for MM1 or EAIF connections to the NowSMS gateway.)
- Fix for MMS send/receive over GPRS not properly recognising "Network:" connections (like used by the Sierra Wireless Aircard 750) on non-English versions of Windows.
- When receiving messages via SMTP, support SMTP content where SMIL files reference other content pieces by "Content-id:" references.
- Fix for routing to SMS connection based upon recipient address masks not working properly in some configurations.
- "2-way SMS": Add support for "command to execute" definition of "mailto:@@SMSPREFIX@@". This command is used to facilitate SMS to e-mail gateway functionality. If the first text of the SMS message is an e-mail address, then the message is forwarded to this address via e-mail.
- Fix for problems processing extremely long SMS messages through the "2-way" command facility.
- Add function to configuration interface for clearing the event log.
- Additional parameters supported for setting TON and NPI values. The following parameters can now be specified in SMSGW.INI, under either a section header titled [SMPP] (to apply for all SMPP SMSC connections), or under the individual section header for a particular SMPP SMSC connection (e.g., [SMPP - ip.address:port] section):
SourceTON=
SourceNPI=
DestTON=
DestNPI=
BindTON=
BindNPI=
If these values are not set, the default behaviour is as follows:
SourceTON = 1 when the sender address for a submitted message is in international format (first character is "+"), SourceTON = 0 when the sender address is not in international format (first character is not "+"), SourceTON = 5 when the sender address is alphanumeric.
SourceNPI = 0 when the sender address is blank or alphanumeric format. SourceNPI = 1 in all other conditions.
DestTON = 1 when the recipient address for a message is in international format (first character is "+"), DestTON = 0 when the recipient address is not in international format (first character is not "+").
DestNPI = 1
BindTON = 0
BindNPI = 0
Patch 1: October 17, 2003
- Fix for problem in MMSC where a Samsung P400 was not able to send a message via the MMSC. When specifying the "To" recipient, the P800 includes character set information which the MMSC was interpreting incorrectly.
- Fix for MM7 VASP interface recipient parsing. Previous versions expected multiple recipients to be specified under a single <To>, <Cc> or <Bcc> element (all 3 elements could exist, but if multiple "To" recipients existed, it was expected that they would all occur within a single <To> element). This fix now supports multiple occurrences of these elements. An example of the problem can be found at: http://support.nowsms.com/discus/messages/485/842.html
- Fix for MM7 VASP interface having a problem with messages that included more than 200 to 300 recipients.
- Fix for problem with "MMSC VASP" configuration dialog. The configuration dialog would not properly enable the "Route via MM7" option for processing received messages (at least one external MM7 link must be defined in the "MMSC Routing" table for this option to be enabled).
|
Search
