In 1.5.0 this is no longer (necessarily) a custom MMSC. So you could add
something like this:
group = mmsc
type = mm1
mm1-sms-on-command = lynx -dump
mm1-sms-off-command = lynx -dump
incoming-port = 13014
mmsc-url = http://mms.orange.pl
mm1-http-proxy = 192.168.6.104:8080
mm1-gprs-on-command = /usr/local/mbuni/sbin/start-mms-gprs
mm1-gprs-pid-command = "cat /var/run/ppp-mms.pid|head -1"
On Apr 15, 2011, at 21:45, Piotr Isajew wrote:
> As for mmsc settings, here are mine:
> custom-settings = "smsc-on=lynx -dump
> those work well for Orange, and similar ones work with P4.
> I use CVS versions for kannel & mbuni (but mbuni recently
> advanced to next release, so it's better to start with it).
> Also note, that kannel is only relevant if you want to receive
> mms messages or send push notifications to mobile phones. For
> sending mms messages you don't need running kannel. You only need
> it's gwlib to compile mbuni.
> I had no chance to play with Huawei, but I can tell that Option
> modems work without problems.
> On Fri, Apr 15, 2011 at 08:25:34PM +0200, Stanisław Czech wrote:
>>> I haven't upgrade to current stable yet, so I don't know if my
>>> comment will be appropriate for you, however, I think in mmsc
>>> section you should uncomment custom settings, and provide setting
>>> for port (i.e. port=8976). That's the port on which MM1 module
>>> will listen for incoming notifications, and perhaps lack of this
>>> setting makes it impossible for notify thread to start.
>> I did. It was commented since I wanted to know if it makes any
>> difference. With and without custom settings parameter the same error
>> What kind of version setup is known to be the most stable/proven
>> (kannel/mbuni) ? Maybe you could suggest any known to work combination
>> of mm1 modem and kannel/mbuni version that is available on polish
>> Stanislaw Czech
>> NOWATEL Sp. z o.o.
>> Users mailing list
> Users mailing list
Users mailing list