| X-nokia-mmsc-message-id sent with MMS message routed via EAIF? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| anonymous Unregistered guest |
Hi Folks, Does the current version of NowSMS/MMS send the HTTP header "x-nokia-mmsc-message-id" when it routes an MMS message out over EAIF? I'm currently running v5.51 (b20040922) and the header isn't present - it's preventing me from using NowSMS as a substitute for a live Nokia MMSC during testing  Many Thanks, D http://www.textnode.com | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4520 Registered: 10-2002 |
Hi D, When you configure an outbound EAIF connection, there is an option to specify whether the connection is to a VASP or to an MMSC. The default configuration is "to MMSC", in which case if we included an "x-nokia-mmsc-message-id" header, the MMSC might complain. But it is a different story when routing a message to a VASP, where the VASP may expect this header to be present. It looks like this was added in v5.51b. You can find links to that version under the "What's New" section of the web site. Here's the info on that particular change: * MMSC Routing - EAIF Connections - Add "Connection Type" attribute to specify whether the connection is "To VASP" or "To MMSC". When connecting to a VASP, the following headers will be included: "x-nokia-mmsc-from:", "x-nokia-mmsc-message-id:", "x-nokia-mmsc-to:" and "x-nokia-mmsc-version:". These headers are not included when routing a message to an MMSC (the MMSC will parse the values from the actual message). | |||
| D Unregistered guest |
Thanks Bryce, we're upgrading now. | |||
| D Unregistered guest |
Hi Bryce, I'm not sure if this is expected, but after the upgrade, the extra headers didn't appear in the messages (with either VASP or MMSC options set) until I removed the existing routing entry and re-created it. Best Regards, D http://www.textnode.com | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4530 Registered: 10-2002 |
Hi D, I can't imagine why the headers wouldn't be there without removing/re-creating the route. The configuration option sets an INI file option (VASPOUT\vaspname\VASP.INI) which gets checked before each message transmission via that route. (mm7DeliverReq=Yes is the setting ... a bit confusing for an EAIF connection, but we had previously defined this To MMSC/To VASP setting for MM7 connections only, so we used the same named configuration setting for EAIF.) I'll run some tests, but I'm glad you were able to make it work. -bn | |||
