| M-delivery-ind contains wrong Message-Id |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Dziugas Baltrunas |
Hi, if MM1 sender sends MMS message which is later is routed to MM4 and then delivered, sender gets MMS m-delivery-ind over MM1 containing Message-ID which is not the same as one received in M-send-conf. The problem is that the after the change below NowMMS started replacing slashes to dots for MM4 connections, but it looks like remapping before sending m-delivery-ind over MM1 has been forgotten. Is there any workaround for this problem (for example, MessageIDPatch=No inside [VASP])? Most of the phones expect Message-ID to be the same, therefore if it is different, phone does not recognize is as a delivery receipt. Thanks, Džiugas 2007-04-11: * MMSC/MM4: Because of problems with some MMSCs refusing to accept the "/" character in MMS message-id and transaction-id values for MM4 connections, NowSMS has changed its message id format for MM4 connections to replace the "/" character with a "." character. The previously added MessageIDPatch=Yes parameter is no longer necessary. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2663 Registered: 08-2008 |
Hi Džiugas, Confirmed. This does not seem to be working properly. Read receipts that come in via MM4 seem to be translated properly, but delivery notifications do not (unless both sides of the MM4 connection are NowSMS). I don't think there is a work-around, but engineering is working on this as a priority issue. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2671 Registered: 08-2008 |
Hi Džiugas, An update to fix this problem has been posted in the following link: http://www.nowsms.com/update-patch-2010-11-26 -- Des NowSMS Support | |||
