| M-Send.conf header in VASP |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hello! When I'm accepting incoming MMS from operator's MMSC using VASP in NowSMS, I need to send back to operator's MMSC in M-Send.conf "x-nokia-mmsc-charged-party" and "Recipient x-nokia-mms-charging" headers. How I can do this? Thanks! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4670 Registered: 10-2002 |
Hi, I need more detail to answer your question. Basically, I don't understand the message flow, because those headers would not be included in an M-Send.conf response. But they could be in an M-Send.req for a message that you submit to the operator. So, perhaps I am missing something, and if so, I'd like to get more detail on the logical transaction flow, so that I can understand. The "x-nokia-mmsc-charged-party" header can be set to "recipient" by checking "Use Reverse Charging" when you define an outbound EAIF connection. (It would apply to all messages sent via that connection ... this means that you would need to have two separate outbound MMSC connections defined if you sometimes send recipient charged, and sometimes sender charged. You could select which outbound route is used by associating a different sender address with each ... so when you send from an address that matches the reverse charging route, this header gets inserted.) Other headers, such as "x-nokia-mmsc-charging", which can specify a charging code, can only be configured by manually editing the configuration files. See the following thread for an explanation of how this extra header can be configured: http://support.nowsms.com/discus/messages/485/8051.html But in both cases, my understanding is that both of these headers can only be applied to outbound message sending. They would not be included in an m-send.conf response to receipt of an inbound message. -bn | |||
