Re: [PATCH 1/4] DTD changes for mms, prepaid, wap

[Marcel Holtmann <marcel holtmann org>]

Hi Dan,

> > >>>>> The only tricky part is that in some cases some providers use the same
> > >>>>> APN for Internet access and MMS. We could just list the context twice in
> > >>>>> that case or have a list of types per context.
> > >>>> I am not sure what's the best way here, i.e. list of types vs listing the APN 
> > >>>> twice. Any suggestions?
> > >>> the final decision is up to Dan here. I am fine with having the same APN
> > >>> multiple times with different types.
> > >> That's fine with me too; though it would require an update of client
> > >> software to filter them out.
> > > I lied, I'd prefer single APNs and allow multiple types/plans for those
> > > APNs via attributes if we can, ie:
> > >
> > > <apn name="wap.foobar" type="prepaid postpaid" plan="wap internet">
> > >     ...
> > > </apn>
> > >
> > 
> > I'm not sure what these properties are going to be used for, but for wap
> > (and probably also MMS) APNs, you often need to use a proxy. Shouldn't
> > those settings be included here also then for it to be useful?
> 
> Yes.  And while we're at it, default SMSCs and stuff like that.

actually the SMSC is the only one that provider still provision properly
on their SIM cards these days. Reading them from the SIM card is as good
as having them in the database.

Regards

Marcel