Re: MM7 optional parameters

Hi Paul,

Starting point will be: mmlib/mms_mm7soap.c, right?

We need to do "premium rated mobile terminating" messages.  So, a VASP
will submit a message for a subscriber and wants to charge the
subscriber a certain amount for this MMS.  The mentioned fields looks
like the correct ones to use for this... or do you have a better way
of doing it?


On 10/19/06, Paul Bagyenda <bagyenda@xxxxxxxxxxx> wrote:
> Hi Deon,
>
>   Service Code is supported (CVS at least), however the other
> optional parameters are not (haven't had need for them myself). I
> suppose we need to find a generalised way to support these ...
>
> On Oct 18, 2006, at 13:22, Deon van der Merwe wrote:
>
> > Hi,
> >
> > What support is there in Mbuni for the optional MM7 parameters
> > relating to billing?  They are listed below.  Anyone else had a need
> > for using them?
> >
> > Service code
> >   Optional    Information supplied by the VASP which may be included in
> > charging information.  The syntax and semantics of the content of this
> > information are out of the scope of this specification.
> >
> > Charged Party
> >   Optional    An indication which party is expected to be charged for an
> > MM submitted by the VASP, e.g. the sending, receiving, both parties
> > third party or neither.
> >
> > Charged Party ID
> >   Optional    The address of the third party which is expected to pay
> > for the MM
> >
> > _______________________________________________
> > Users mailing list
> > Users@xxxxxxxxx
> > http://mbuni.org/mailman/listinfo/users_mbuni.org
>
>
> _______________________________________________
> Users mailing list
> Users@xxxxxxxxx
> http://mbuni.org/mailman/listinfo/users_mbuni.org
>