| Unable to send MMS with only CC recipients (via EAIF) |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Lite Support ⬆ Archive through September 20, 2012 ⬆ |
◄ ► |
| Author | Message | |||
| Jason Scrod New member Username: Captainscrod Post Number: 1 Registered: 06-2012 |
Hello, I'm attempting to send an MMS via EAIF that only contains CC recipients. NowSMS Lite receives the payload that I am posting, but it refuses to send it because it cannot find the recipients: 18:47:54:048 [10] ThreadProcessConnection: Got application/vnd.wap.mms-message 18:47:54:048 [10] ThreadProcessConnection: Got m-send-req 18:47:54:048 [10] ThreadProcessConnection: Found VASP user definition user1 18:47:54:048 [10] ThreadProcessConnection: VASP password ok for user1 18:47:54:048 [10] ThreadProcessConnection: No valid recipients! 18:47:54:049 [10] ProcessRead: Winsock:ioctlsocket reports end of socket 18:47:54:049 [10] ThreadProcessConnection: Processing Complete 18:47:54:049 [10] InternalProcessConnection: Thread ended It works properly when I set the TO or BCC fields. Is this a bug in NowSMS Lite? Thanks, Jason | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3991 Registered: 08-2008 |
Hi Jason, It has been awhile since I worked with EAIF. I'm at a disadvantage, because I can't see the payload you are posting. Only including CC recipients is odd, but it is acceptable. How exactly are you specifying these recipients in your payload? There is no "X-Nokia-MMSC" header for CC recipients (at least through EAIF v3.1 which is the latest release of that specification that I can find), so CC recipients need to be in the MMS message itself (not an HTTP header). If an "X-Nokia-MMSC-To" HTTP header is present, any TO/CC headers present in the MMS message itself are considered "display only". It's a little confusing, but here's what the Nokia EAIF spec says:
-- Des NowSMS Support | |||
| Jason Scrod New member Username: Captainscrod Post Number: 2 Registered: 06-2012 |
Hi Des, Thanks for the reply. The CC recipient is set in the actual message payload. I started investigating using EAIF because I needed a way to send my own MMS payload + have one or more CC recipients. The NowSMS Lite web interface allows you to specify your own payload, but it doesn't allow you to set CC recipients (only TO). Is there a better way that I can do this other than using EAIF? I would be happy to send you the payload if you can give me your email address. Thanks, Jason | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3995 Registered: 08-2008 |
Hi Jason, OK ... I've run some tests, and I can't get CC recipients to work using this interface either. We are investigating further. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3996 Registered: 08-2008 |
Hi Jason, Here is a temporary update to address this (it hasn't gone through complete testing yet). http://www.nowsms.com/download/lite20120615.zip This version will also allow CC/BCC recipients from the web interface. CC:/BCC: recipients are accepted in the "Additional Headers" (MMSHeaders) parameter, one recipient per line. For example: CC: +447777777777 CC: +447777777778 The Phone Number/To header is not required. -- Des NowSMS Support | |||
| Jason Scrod New member Username: Captainscrod Post Number: 3 Registered: 06-2012 |
Hi Des, Thanks for posting the update! I tried it out today and here are my findings: 1. EAIF: one or more CC recipients works! 2. Web Interface: one CC recipient via the additional headers field works. Adding multiple CC recipients as you indicated (separate CC headers... not a single header that is comma separated) results in the message being sent to only one recipient. It appears to only send to the last recipient listed. 3. When NowSMS Lite receives a message that was sent to multiple recipients (TO and/or CC), the .hdr file does not include the header info for the other recipients. Is there a way to save the incoming .mms payload so I can inspect the header data myself? Thanks, Jason | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3999 Registered: 08-2008 |
Hi Jason, I'm not having any problem posting to multiple CC recipients via the web browser. I must be doing something different. I've tried different browsers. Most of my tests are 3 CC: entries and no TO: entry. ("Phone Number" parameter left blank.) That said, there is a potential issue if a message is addressed to more than 5 recipients. This is a somewhat arbitrary limit. In the early days of MMS, we had a problem with a particular operator MMSC that would reject messages addressed to more than 5 recipients. So, when submitting via a modem, we break messages addressed to more than 5 recipients into blocks with a max of 5 recipients. We probably should revisit that limit, as I'd be very surprised to find that being an issue these days. And if it was, it could be adjusted for problem environments. To adjust this limit, edit VASPOUT\nowsmslite\VASP.INI, and under the [VASP] header add MaxRecips=#, where # is the number at which to separate recipient blocks.
This is a bug. We are investigating. If you enable the SMSDEBUG.LOG (I believe NowSMS Lite enables it by default), the MMS content will be logged with a hex dump in that file. -- Des NowSMS Support | |||
| Jason Scrod New member Username: Captainscrod Post Number: 4 Registered: 06-2012 |
Hi Des, Sending CC via the web interface with the fix that you posted works. I must have messed something up when I was testing it. Good to know about the 5 recipient limit. I have seen the hex dump in the logs. I was just curious if the raw payload was being dumped to the filesystem somewhere that I could easily grab it. Not a problem. The hex dump works. Hopefully the multiple recipients not being shown in the headers for received messages can be fixed in a later release. Thanks for the help and for spinning a build to fix the CC issue. That was really cool of you guys. Jason | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4003 Registered: 08-2008 |
Hi Jason, Yes, the multiple recipient issue for the received message headers will be fixed soon. Probably by the middle of next week. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4011 Registered: 08-2008 |
Hi Jason, Here's an update that addresses the inbound message parsing problem with recipient lists: http://www.nowsms.com/download/lite20120628.zip -- Des NowSMS Support | |||
| Jason Scrod New member Username: Captainscrod Post Number: 5 Registered: 06-2012 |
Hi Des, This is great! Thanks for posting the fix. I tested it out and I am able to successfully see the incoming recipients now. Thanks again for all the help. Jason | |||
