| Eaif - no x-nokia-mms-message-id being sent when routing via Eaif |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Jet Unregistered guest |
Folks, I've set up mmsc routing to route mms messages out via Eaif. My understanding is that an mmsc should send the http header 'x-nokia-mms-message-id' to a VAS, so that the VAS can ack/nack the message asynchronously. Please tell me I'm wrong or mad :-) Many Thanks, Jet | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3646 Registered: 10-2002 |
Hi Jet, We made some modifications to our EAIF interface in order to be compatible with the Nokia APIs, which expect this header (and some others) to be set when a message is routed from MMSC to a VAS. There is a patch that can be applied to v5.51 which includes this update, where basically when you define an EAIF connection, you tell us whether the connection is to an MMSC or to a VASP, and the headers are slightly different when routing to a VASP. http://www.nowsms.com/download/20040924.zip -bn | |||
