Hi again,
___
kannel.conf
group = smsc
smsc-id = moj
smsc = at
port = 1
modemtype = huawei_e220_00
device = /dev/ttyUSB0
sms-center = +48601000310
my-number = +48663837206
connect-allow-ip = 127.0.0.1;192.168.*.*
When you send MMS to the modem, you should see an incoming SMS in Kannel's
logs. This contains the notification. One would have to see the logs (both
kannel and mbuni) to understand what's going on.
On Apr 18, 2011, at 10:32, Stanisław Czech wrote:
Hi again,
On 2011-04-18, at 09:32, Stanisław Czech wrote:
I have no problems sending and recieving sms, and sending MMS but i
can't recieve any MMS. Does anyone have some clues where there can be
a problem? smsbox see's nothing when I send mms from a mobile to the mbuni's
modem.
In kannel.conf I
First thing to do is to make kannel to see an incoming mms
notification (wap-push) and dispatch it via the proper service to mbuni.
If you don't see ANY incoming message in kannel, that could mean one of two:
- something is broken in the delivery chain before kannel (you can
check this by
On 2011-04-18, at 10:20, Stanisław Czech wrote:
First thing to do is to make kannel to see an incoming mms
notification (wap-push) and dispatch it via the proper service to mbuni.
If you don't see ANY incoming message in kannel, that could mean one of two:
- something is broken in the
Welcome,
2011-04-18 07:18:55 [9017] [4] INFO: Starting to service Nowa
wiadomosc multimedialna od +48 na http://foto.plus.pl MMS_id:
haslo: xxx from Centrum MMS to +48x
This means I got sms msg that I have a new mulitmedia msg that I can
download form the
Maybe there is some secret knowledge needed for making Huawei modem work with
this. I don't know :-(
On 2011-04-18, at 11:20, Stanisław Czech wrote:
It seems Huawei is incapable of recieving MMS. Is there a way to check
it to be sure?
I found on other forums:
I don't think there is a secret. Receipt of the notification is *purely* via
SMS. Which means that Mbuni hasn't even kicked in yet. Basically MMS reception
at the network works like this: The operator MMSC checks (HLR, whatever) if
receiving subscriber's device is MMS-capable. If not,
On 2011-04-18, at 11:55, Paul Bagyenda wrote:
I don't think there is a secret. Receipt of the notification is *purely*
via SMS. Which means that Mbuni hasn't even kicked in yet. Basically MMS
reception at the network works like this: The operator MMSC checks (HLR,
whatever) if receiving
Hi,
I don't think there is a secret. Receipt of the notification is
*purely* via SMS. Which means that Mbuni hasn't even kicked in yet.
Basically MMS reception at the network works like this: The operator
MMSC checks (HLR, whatever) if receiving subscriber's device is
MMS-capable. If not,
I can only say, that it (505) works for me, but I'm using it on different
network, so if it's an operator related issue, it may happen you will have the
same problem with Option.
P.
On 2011-04-18, at 12:11, Stanisław Czech wrote:
Nevertheless could someone confirm that Option Icon
modems
Hi,
I can only say, that it (505) works for me, but I'm using it on
different network, so if it's an operator related issue, it may
happen you will have the same problem with Option.
As I remember you used Orange and P4 sim's. I also have such sims so I
will be able to test it with these
In 1.5.0 this is no longer (necessarily) a custom MMSC. So you could add
something like this:
group = mmsc
id=modem
type = mm1
mm1-sms-on-command = lynx -dump
'http://localhost:13000/start-smsc?password=barsmsc=modemsmsc'
mm1-sms-off-command = lynx -dump
In 1.5.0 this is no longer (necessarily) a custom MMSC. So you could add
something like this:
group = mmsc
id=modem
type = mm1
mm1-sms-on-command = lynx -dump
'http://localhost:13000/start-smsc?password=barsmsc=modemsmsc'
mm1-sms-off-command = lynx -dump
Thanks !
2011/4/17 Stanisław Czech s.cz...@nowatel.com
In 1.5.0 this is no longer (necessarily) a custom MMSC. So you could add
something like this:
group = mmsc
id=modem
type = mm1
mm1-sms-on-command = lynx -dump
'http://localhost:13000/start-smsc?password=barsmsc=modemsmsc'
Welcome,
Would be helpful yes.
I still did not get this config too.
Thats a pity. I tried and got the same result as you did:
2011-04-15 15:23:11 [29837] [7] DEBUG: Queued to thread 2 for
/var/spool/mbuni/mmsbox_outgoing/1/9l/qf3489.1.x837.54, sendt=1302873790,
tnow=1302873791
2011-04-15
looks like one of mm1 threads not being started... That would
rather be due to some of ports being blocked by some other app
than because of modem-specific problem. Check your MM1 config for
port conflicts.
Regards,
Piotr
On Fri, Apr 15, 2011 at 03:39:26PM +0200, Stanisław Czech wrote:
Hi,
looks like one of mm1 threads not being started... That would
rather be due to some of ports being blocked by some other app
than because of modem-specific problem. Check your MM1 config for
port conflicts.
I can't see any port conflicts, neither I have any port used by other app.
I
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,
As for mmsc settings, here are mine:
custom-settings = smsc-on=lynx -dump
'http://localhost:13000/start-smsc?password=barsmsc=modemsmsc';smsc-off=lynx
-dump
'http://localhost:13000/stop-smsc?password=barsmsc=modemsmsc';gprs-on=/usr/local/mbuni/sbin/start-mms-gprs;gprs-pid=cat
Hi,
After browsing few hours through various posts and sites I didn't find
complete setup for Huawei modems (E220 or other). Does anyone have such working
configuration (including pppd configurations etc) ?
I know Emmanuel was looking for such configs a while ago.
That would help a lot of guys
Would be helpful yes.
I still did not get this config too.
BR
Emmanuel
2011/4/14 Stanisław Czech s.cz...@nowatel.com
Hi,
After browsing few hours through various posts and sites I didn't find
complete setup for Huawei modems (E220 or other). Does anyone have such
working
configuration
22 matches
Mail list logo
