Re: [Users] Vodacom South Africa

2007-10-09 Thread Deon van der Merwe
Hi Ruan,

On 10/9/07, Ruan [EMAIL PROTECTED] wrote:
 Hi everybody,

 AFAIK - Vodacom South Africa does not accept HTTP posts to their MMSC.
 It has been suggested to me to bypass Kannel/Mbuni completely and make a
 WAP/WSP post directly to Vodacom via UDP with the address and port of
 the Vodacom MMSC in the binary headers of the post. I've found a script
 to do this - but it does not work.

 What I need to know is - has anybody on this list successfully used
 Mbuni/Kannel to post MMS to Vodacom via MM1? Or, alternatively - has
 anybody managed this via IP without a dedicated line running into Vodacom?


Mbuni can not do MM1 (yet).

You can use Mbuni to do MM7.  For this you will need to have a account
with Vodacom.  As far as I know you are not required to have a
dedicated line for that access.
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


Re: [Users] MM4 delivery request from

2007-09-24 Thread Deon van der Merwe
Hi Paul,

On 9/25/07, Paul Bagyenda [EMAIL PROTECTED] wrote:
 Reports and notifications are generated by the system, hence the sender. In
 practice I guess it can make a difference to some devices which use the
 'from' address to match the DLR against the original message. (They should
 more properly use the message-id).


I agree that the message-id should be enough.  One operator's MM4
interface uses it as a kind of double-check validation.

  Is it a problem? Can be changed easily I believe.


I have been scratching around, but have been unable to find the exact
place... perhaps it was just to late at night.
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


Re: [Users] Newbie needs help!

2007-06-07 Thread Deon van der Merwe

Hi Steve,

On 6/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


I'm a newbie to mbuni and I would need some help to achieve what I want to do.

In fact, I want my mobile to use a CSD connection to download MMS. I already
changed the configuration of my phone and now when it receives an MMS
notification, it uses the CSD connection to try to retrieve it, but as mbuni
isn't running yet the download of the MMS fails (the dial-in is configured and
works).


GSM operators normally has to APNs configured.  One for internet
access and the other for mms access.  The main reason behind this is
the billing model is different for the 2 contents.  Do not know where
you are doing the CSD call too, but changes of reaching your  MMSC
from it is probably slim.  It will also mean that you are paying for
the MMS retreival...



Now I would like to know what I need to use and how I should configure mbuni in
order to download a MMS that would be stored on the PC running mbuni
successfully (I have installed mbuni).


mbuni can not do this.  mbuni is a full-featured MMSC (like the one
your GSM operator is running) in order to manage all the MMS's.

mBuni can talk to other MMSC using MM4 (mmsc interconnect) and MM7
(used for machine-mms and mms-machine).  For the first one you need to
be a GSM operator.  The other one you need to be a WASP with the GSM
operator.
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


Re: [Users] Regarding MMSC

2007-06-04 Thread Deon van der Merwe

Hi Sundeep,

On 6/4/07, Sundeep Kumar Sharma [EMAIL PROTECTED] wrote:


We are developing a SMS-MMS (Value Added Service Provider) Application.

We need MMSC to test our application.

We have downloaded and installed mbuni in Linux environment

and able to run mmsrelay and mmsproxy.





We are using below link as mmsc url

http://mbuni:[EMAIL PROTECTED]:8080/eaif





but not able to connect to this site getting SOAP Exception.

Please guide for the same.

How we can use mbuni MMSC for testing our application.



Can you show us your configuration for the VASP in the mbuni config file?
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


Re: [Users] kannel cvs + mbuni cvs is possible?

2007-05-31 Thread Deon van der Merwe

Hi,

You did do a make install of kannel, right?  Where are the libs for
that location (did you change the default install dir?)  Is that dir
in your LD_CONFIG_PATH?


On 5/31/07, Délsio Cabá [EMAIL PROTECTED] wrote:

HI!

I´m trying to install mbuni cvs + kannel cvs
Kannel is working just fine but I´m unable to install mbuni
I run:
./configure --with-kannel-dir=/root
/gateway/
and I get:
.
.
.
 checking for gw-config... /root/gateway//gw-config
checking Kannel version... cvs-20070520
checking Kannel libs... -L/usr/local/lib/kannel -lgw -lwap -lgwlib -lrt
-lresolv -lnsl -lm  -lpthread -L/usr/lib -lxml2 -lz -lpthread -lm
checking Kannel includes... -I/usr/local/include/kannel -g -O2
-D_XOPEN_SOURCE=600 -D_BSD_SOURCE -I/usr/include -D_FILE_OFFSET_BITS=64
-I/usr/include/libxml2
checking for cfg_create in -lgwlib... yes
checking for wsp_headers_pack in -lwap... no
configure: error: Kannel WAP lib is required!
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users



___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


Re: Tr: RE : Re: RE : Re: [Users] start mmsc error with mbuni-1.2.0

2007-05-09 Thread Deon van der Merwe

Hi Patrick,

On 5/9/07, patrick meye [EMAIL PROTECTED] wrote:

Thanx Paul,yes i've access to that directory:

[EMAIL PROTECTED] ~]# ls -l /tmp/spool
-rw-r--r--  1 root root 0 mai  7 13:33 /tmp/spool


/tmp/spool should be a directory, and not a *file*.
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


Re: [Users] urgent

2007-05-02 Thread Deon van der Merwe

Hi,

Which MTA  are you running?

On 5/2/07, nawfat nawfat [EMAIL PROTECTED] wrote:

i have a problem with mmsfromemail
can someone show me how can i use it(syntax).

 
 Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
! Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses.


___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users



___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


Re: [Users] Newbie doubts

2007-05-01 Thread Deon van der Merwe

Hi,

On 5/1/07, Fernando Gomes [EMAIL PROTECTED] wrote:

Sorry, forgot one detail, I can't force users to change their MMSC
configuration, so they should continue to use their MMSC, I jut want to
implement the behaviour of an MMS client to receive MMS messages.


The only way of doing this is to connect to your operators MMSC using
MM7.  mbuni can do this.
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


Re: [Users] MMSC vas gateway via HTTP PROXY?

2007-03-12 Thread Deon van der Merwe

Hi Giovanni,

I do not think what you are trying to do will work...
1) when you connect to a MMSC from your phone, you are using MM1.
2) when mbuni talks to another MMSC it uses MM7.

You will need to find out from the operator on which port is the MM7 interface.

On 3/12/07, Giovanni Licata [EMAIL PROTECTED] wrote:


According my mobile phone configuration I should start a GPRS connection
using the parameters below:

*APN: tre.it
Home Page: http://10.216.59.240:10021/mmsc

Proxy: wsb.treumts.it:8799*

Establishing connection I was not able to reach directly 10.216.59.240
but only after the settings http proxy (wsb.treumts.it:8799).

Now I need to set this proxy inside mbuni configuration in order to
reach MMSC but I don't know whether it provides this feature.

To run mbuni as VAS gateway I started mmsbox from configuration below:

#mbuni.conf
group = core
log-file = /var/log/mbuni/mmsc.log
access-log = /var/log/mbuni/access.log
log-level = 0

group = mbuni
name = MMSC
hostname = localhost
...
...
...

group = mmsc (Outgoing MMS?)
id = tre_MMSC
mmsc-url = http://10.216.59.240:10021/mmsc
incoming-username =
incoming-password =
incoming-port = 10002
type = soap

group = send-mms-user
username = giovanni
password = giovanni



I hope that should solve my problem ...

Thanks in advance :)

Best Regards
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


Re: [Users] Problem running mbuni

2007-01-29 Thread Deon van der Merwe

Hi,

On 29 Jan 2007 06:13:13 -, mayank agarwal [EMAIL PROTECTED]
wrote:


2007-01-29 22:10:12 [20695] [0] ERROR: fopen failed: couldn't open
`mmsc.conf'
2007-01-29 22:10:12 [20695] [0] ERROR: System error 2: No such file or
directory




Well, you have to tell it which config to use... something like this:
 mmsproxy conf/mmsc.conf
___
Users mailing list
Users@mbuni.org
http://lists.mbuni.org/mailman/listinfo/users


[Users] MOT-V3i UserAgent problem

2006-10-25 Thread Deon van der Merwe
Hi,

We are having a little problem with the Motorola v3i.  The UserAgent
profile is loaded from:
http://motorola.handango.com/phoneconfig/v3i/Profile/v3i.rdf

From the mbuni logfile it is dumped like this.  It is missing the
Accept content as specified inthe above profile.

Anyone else had this problem?

2006-10-25 09:03:54 [30359] [257] DEBUG: Dumping profile for
MOT-V3i/08.D8.35R MIB/2.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1
2006-10-25 09:03:54 [30359] [257] DEBUG: MaxMsgSize: 102400
2006-10-25 09:03:54 [30359] [257] DEBUG: MaxRes: 640x480
2006-10-25 09:03:54 [30359] [257] DEBUG: Accept content:
2006-10-25 09:03:54 [30359] [257] DEBUG: Accept encodings:
2006-10-25 09:03:54 [30359] [257] DEBUG: Accept language: en,
2006-10-25 09:03:54 [30359] [257] DEBUG: Accept charset: utf-8,
2006-10-25 09:03:54 [30359] [257] DEBUG: Mms Version: 1.0,

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


[Users] MM7 optional parameters

2006-10-18 Thread Deon van der Merwe
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@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] MM7 optional parameters

2006-10-18 Thread Deon van der Merwe
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 [EMAIL PROTECTED] 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
OptionalInformation 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
OptionalAn 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
OptionalThe address of the third party which is expected to pay
  for the MM
 
  ___
  Users mailing list
  Users@mbuni.org
  http://mbuni.org/mailman/listinfo/users_mbuni.org


 ___
 Users mailing list
 Users@mbuni.org
 http://mbuni.org/mailman/listinfo/users_mbuni.org


___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] Send MMS only with GSM module

2006-08-30 Thread Deon van der Merwe
Hi Dirk,

On 8/30/06, Dirk van Deventer [EMAIL PROTECTED] wrote:

 Can I send a MMS with Mbuni if I only have a GSM module connected to a PC.
 I've got no other internet connection. I want to send MMS using the GSM
 module. I've set up Kannel to send sms, but also need to send mms. Is there
 anyone who has done it like this and it there anyway that I can maybe view
 you mbuni.conf file.


Mbuni is the actual MMSC.  Kannel will be able to send the MMS
notification to the other subscriber using the modem.  But you need
some kind of IP connectivity for the other subscriber to retreive that
MMS from your machine.

Or do you want to send an MMS to another subscriber using the modem
via your network provider's (like MTN, CellC, Vodacom etc.) MMSC?  In
this case Mbuni is not the correct software.

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] the mms-to-local-copy-handler parameter does not work

2006-08-30 Thread Deon van der Merwe
Hi,

What version of Mbuni are you using?  We you the latest CVS and this
works just fine for getting a copy of all mobile-to-mobile MMS.

On 8/30/06, test test [EMAIL PROTECTED] wrote:

 Hello:
 the mms-to-local-copy-handler parameter does not work, some body can help
 me.

 I have a web application that recive the MMS and shows them, this
 application receives all the messages sent to the 777, and works well.

 But, when attempt that all the messages are sent to the VASP(the same
 aplication) using mms-to-local-copy-handler, does not work. (my web
 aplication receive a mms but doesnt receive the content and the subject,
 from, to, etc headers)

 this is the configuration of vasp Groups
 WORKS WELL


 group = mms-vasp

 vasp-id = newscorp2

 type = eaif

 mmsc-username = null

 mmsc-password = null

 vasp-username = null

 vasp-password = null

 vasp-url =http://mms.dominio.com/ABCD/aplication.php

 short-code = 777
 DOES NOT WORK WELL


 group = mms-vasp

 vasp-id = resend

 type = eaif

 mmsc-username = null

 mmsc-password = null

 vasp-username = null

 vasp-password = null

  vasp-url =http://mms.dominio.com/ABCD/aplication.php

 mms-to-local-copy-handler = true






 Thanks.






 ___
 Users mailing list
 Users@mbuni.org
 http://mbuni.org/mailman/listinfo/users_mbuni.org




___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] mmsrelay cpu time

2006-07-10 Thread Deon van der Merwe
Hi Rene,

What is the value of queue-run-interval in your configuration?

On 7/10/06, Rene Kluwen [EMAIL PROTECTED] wrote:
 I have a box with mmsproxy and mmsrelay running on it.

 Even while processing no messages at all, mmsrelay is eating a lot of CPU
 time.
 What can cause this?

 Rene Kluwen
 Chimit


 ___
 Users mailing list
 Users@mbuni.org
 http://mbuni.org/mailman/listinfo/users_mbuni.org


___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] Block worm

2006-07-03 Thread Deon van der Merwe
Hi Paul,

On 7/3/06, Paul Bagyenda [EMAIL PROTECTED] wrote:
 Deon,

   This is the first time I am seeing this, but it was bound to become
 an issue!

Yes... one of those things I guess!!!

   Best place in my view is mmsc/mmsglobalsender:sendMsg(), just after
 the queue data is loaded. Some code added here would examine the
 message and optionally throw it away. Perhaps?


Will start there... thanks.

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] Compatible phones

2006-06-30 Thread Deon van der Merwe
Hi,

Updated list of phones... totals to 103 now!

http:$$extranet.sagem.com$UAProfile$891879.xml

http:$$mobileinternet.panasonicbox.com$UAprof$X500$R1.xml

http:$$motorola.handango.com$phoneconfig$E1000$Profile$E1000.rdf
http:$$motorola.handango.com$phoneconfig$V980$Profile$V980_NO_BEARER.rdf
http:$$motorola.handango.com$phoneconfig$l6$Profile$l6.rdf
http:$$motorola.handango.com$phoneconfig$l7$Profile$l7.rdf
http:$$motorola.handango.com$phoneconfig$razrv3x$Profile$razrv3x.rdf
http:$$motorola.handango.com$phoneconfig$v3$Profile$v3.rdf
http:$$motorola.handango.com$phoneconfig$v360$Profile$v360.rdf
http:$$motorola.handango.com$phoneconfig$v3i$Profile$v3i.rdf
http:$$motorola.handango.com$phoneconfig$v600$profile$v600.rdf
http:$$motorola.handango.com$phoneconfig$v600r$Profile$v600r.rdf

http:$$nds.nokia.com$uaprof$N3100r100.xml
http:$$nds.nokia.com$uaprof$N3650r100.xml
http:$$nds.nokia.com$uaprof$N5100r100.xml
http:$$nds.nokia.com$uaprof$N6100r100.xml
http:$$nds.nokia.com$uaprof$N6610r100.xml
http:$$nds.nokia.com$uaprof$N6610r200.xml
http:$$nds.nokia.com$uaprof$N6800r100.xml
http:$$nds.nokia.com$uaprof$N7210r200.xml
http:$$nds.nokia.com$uaprof$N7710r100.xml
http:$$nds.nokia.com$uaprof$N8910ir100.xml
http:$$nds1.nds.nokia.com$uaprof$N3100r100.xml
http:$$nds1.nds.nokia.com$uaprof$N3200r200.xml
http:$$nds1.nds.nokia.com$uaprof$N3220r100.xml
http:$$nds1.nds.nokia.com$uaprof$N3230r100.xml
http:$$nds1.nds.nokia.com$uaprof$N3250r100.xml
http:$$nds1.nds.nokia.com$uaprof$N5140r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6020r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6030r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6060r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6101r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6111r200.xml
http:$$nds1.nds.nokia.com$uaprof$N6170r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6220r300.xml
http:$$nds1.nds.nokia.com$uaprof$N6230ir100.xml
http:$$nds1.nds.nokia.com$uaprof$N6230ir200.xml
http:$$nds1.nds.nokia.com$uaprof$N6230ir201.xml
http:$$nds1.nds.nokia.com$uaprof$N6230ir300.xml
http:$$nds1.nds.nokia.com$uaprof$N6230ir301.xml
http:$$nds1.nds.nokia.com$uaprof$N6230r200.xml
http:$$nds1.nds.nokia.com$uaprof$N6230r300.xml
http:$$nds1.nds.nokia.com$uaprof$N6230r400.xml
http:$$nds1.nds.nokia.com$uaprof$N6260r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6270r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6600r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6610ir100.xml
http:$$nds1.nds.nokia.com$uaprof$N6630r100-VF2G.xml
http:$$nds1.nds.nokia.com$uaprof$N6630r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6670r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6680r100-VF2G.xml
http:$$nds1.nds.nokia.com$uaprof$N6680r100-VF3G.xml
http:$$nds1.nds.nokia.com$uaprof$N6680r100.xml
http:$$nds1.nds.nokia.com$uaprof$N6820r100.xml
http:$$nds1.nds.nokia.com$uaprof$N7250ir100.xml
http:$$nds1.nds.nokia.com$uaprof$N7270r100.xml
http:$$nds1.nds.nokia.com$uaprof$N7610r100.xml
http:$$nds1.nds.nokia.com$uaprof$N8800r100.xml
http:$$nds1.nds.nokia.com$uaprof$N8800r200.xml
http:$$nds1.nds.nokia.com$uaprof$N9300ir100.xml
http:$$nds1.nds.nokia.com$uaprof$N9300r100.xml
http:$$nds1.nds.nokia.com$uaprof$N9500r100.xml
http:$$nds1.nds.nokia.com$uaprof$NE61-1r100.xml
http:$$nds1.nds.nokia.com$uaprof$NN70-1r100-VF2G.xml
http:$$nds1.nds.nokia.com$uaprof$NN70-1r100.xml
http:$$nds1.nds.nokia.com$uaprof$NN80-1r100.xml
http:$$nds1.nds.nokia.com$uaprof$NN90-1r100.xml
http:$$nds1.nds.nokia.com$uaprof$NN91-1r100.xml
http:$$nds1.nds.nokia.com$uaprof$NNGQDr100.xml
http:$$nds1.nds.nokia.com$uaprof$NNGager100.xml

http:$$wap.samsungmobile.com$uaprof$SGH-D500.xml
http:$$wap.samsungmobile.com$uaprof$SGH-D600.xml
http:$$wap.samsungmobile.com$uaprof$SGH-D600E.xml
http:$$wap.samsungmobile.com$uaprof$SGH-D820.xml
http:$$wap.samsungmobile.com$uaprof$SGH-E760.xml
http:$$wap.samsungmobile.com$uaprof$SGH-E800.xml
http:$$wap.samsungmobile.com$uaprof$SGH-X460.xml
http:$$wap.samsungmobile.com$uaprof$SGH-X600.xml
http:$$wap.samsungmobile.com$uaprof$SGH-X640.xml
http:$$wap.samsungmobile.com$uaprof$d800_10.xml
http:$$wap.samsungmobile.com$uaprof$e530_10.xml
http:$$wap.samsungmobile.com$uaprof$p300_10.xml
http:$$wap.samsungmobile.com$uaprof$x450.xml
http:$$wap.samsungmobile.com$uaprof$z130_00.xml

http:$$wap.sonyericsson.com$UAprof$K700iR201.xml
http:$$wap.sonyericsson.com$UAprof$K700iR301.xml
http:$$wap.sonyericsson.com$UAprof$K750iR101.xml
http:$$wap.sonyericsson.com$UAprof$T610R401.xml
http:$$wap.sonyericsson.com$UAprof$V800R101.xml
http:$$wap.sonyericsson.com$UAprof$W800iR101.xml
http:$$wap.sonyericsson.com$UAprof$W900iR201.xml
http:$$wap.sonyericsson.com$UAprof$Z520iR101.xml
http:$$wap.sonyericssonmobile.com$UAprof$T68R201.xml
http:$$www.sonyericsson.com$UAProf$P900R101.xml
http:$$www.sonyericsson.com$UAProf$P900R102.xml
http:$$www.sonyericsson.com$UAProf$P910iR102.xml
http:$$communication-market.siemens.de$portal$UAProf$UAP.aspx?device\=S65v\=58

http:$$www-ccpp-mpd.alcatel.com$files$ALCATEL-BH4R_1.0.rdf

http:$$www.htcmms.com.tw$gen$ph20-1.0.xml

Re: [Users] send mms to foreign mmsc

2006-06-19 Thread Deon van der Merwe
Hi,On 6/19/06, jammers yann [EMAIL PROTECTED] wrote:
i need help tjis my case i have 2 pc with pc with mbuni installed and configured and bouth work well the first A accept mms with prefix 07 and for prefix 04 the mmsproxy is Bthe second B accept mms with prefix 04 and for prefix 07 the mmsproxy is A
so
when i try to send an mms from 071414 to 0414 on A in
see that all it's ok and the mms it's mime encoded and send via smtp
but the stranger thing is in the B computer maillog In B computer maillog i see something like there is no user 0414 on B computer how do i configure the smtp server on B computer in order to receive and pass the mms to mbuni 


You need to configure your email agent on computer B to use the
email2mms utility (provided with mbuni) to be executed. This
will make the email to be sent into mbuni for processing.

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] RV: the mmsproxy falls when a java application send a mms.

2006-06-16 Thread Deon van der Merwe
Hi Danny,Are you sending a MM7 message, or a MM1 message?Are you sending to the correct port number then?We are using the openwave SDK to send and it works fine...
On 6/16/06, Danny Zenzano [EMAIL PROTECTED] wrote:











Hi, 

anybody can help me?

I start mbuni, Then I send a mms from a java aplicaction but obtain this error and the MMSProxy shout down, this is the last part of the logs file of the mmsproxy:


.

.

.

2006-06-07 12:51:45 [3403] [0] INFO: HTTP: Opening server at port 1981.

2006-06-07 12:51:45 [3403] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller)

2006-06-07 12:51:45 [3403] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread)

2006-06-07 12:51:45 [3403] [0] INFO: HTTP: Opening server at port 1982.

2006-06-07 12:51:45 [3403] [0] DEBUG: Started thread 3 (mmsproxy.c:(gwthread_func_t *)mm7proxy)

2006-06-07 12:51:45 [3403] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 3403.

2006-06-07 12:51:45 [3403] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 3403.

2006-06-07 12:51:45 [3403] [3] DEBUG: Thread 3 (mmsproxy.c:(gwthread_func_t *)mm7proxy) maps to pid 3403.




2006-06-07 12:51:57 [3403] [2] DEBUG: HTTP: Creating HTTPClient for `10.20.3.7'.

2006-06-07 12:51:57 [3403] [0] PANIC: gwlib/octstr.c:2326: seems_valid_real: Assertion `ostr != NULL' failed. (Called from gwlib/octstr.c:1310:octstr_strip_nonalphanums.)


2006-06-07 12:51:57 [3403] [0] PANIC: mmsproxy [0x8079bc9]

2006-06-07 12:51:57 [3403] [0] PANIC: mmsproxy [0x8081f63]

2006-06-07 12:51:57 [3403] [0] PANIC: mmsproxy [0x807f799]

2006-06-07 12:51:57 [3403] [0] PANIC: mmsproxy [0x804b17e]

2006-06-07 12:51:57 [3403] [0] PANIC: /lib/tls/libc.so.6(__libc_start_main+0xd0) [0x402d0ea0]

2006-06-07 12:51:57 [3403] [0] PANIC: mmsproxy [0x804ae51]


I have another Mbu
ni 
Server(Old version) and the application
 works
 with this server.


Thanks.




___Users mailing listUsers@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org
___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


[Users] notify-unprovisioned usage

2006-06-12 Thread Deon van der Merwe
Hi,

(I am not in a position to test this right now, so... I'll ask the list!)

We want to generate a reference for MMS to non-MMS handset and send a
plain text SMS to the subscriber.  The subscriber can then come to our
website and use the reference to view that MMS.

When you have notify-unprovisioned = no:
- will Mbuni still accept the MMS? (it will *not* reject it)
- We have a mms-to-local-copy-handler VASP configured: will the MMS
still be sent to this VASP?  It is from here that we want to send the
text SMS with the reference.

Maybe there is a better way of doing this?

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


[Users] message expiry confusion

2006-05-29 Thread Deon van der Merwe
Hi,

I am a little confused about the way in which the message expiry works:
- default expiry set to 7 days on server
- number of notifications: 3
- backoff: 300

A subscriber now sends a message to another subscriber (with default
expiry).  The destination subscriber does not retreive the message
right away.  All 3 notifications is sent.  Subscriber still does not
retreive it.

Question then:
- does the message expire at the end of those 3 attempts?
- does the message expire after 7 days?

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


[Users] message expiry confusion

2006-05-29 Thread Deon van der Merwe
Hi,

I am a little confused about the way in which the message expiry works:
- default expiry set to 7 days on server
- number of notifications: 3
- backoff: 300

A subscriber now sends a message to another subscriber (with default
expiry).  The destination subscriber does not retreive the message
right away.  All 3 notifications is sent.  Subscriber still does not
retreive it.

Question then:
- does the message expire at the end of those 3 attempts?
- does the message expire after 7 days?

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


[Users] incorrect mmsc for subscriber

2006-05-16 Thread Deon van der Merwe
Hi,

I have started seeing this in our logs today.  Two things that happens:
- in some cases the mmsc for subscriber is detected as some HTTP header
- also the PANIC's in mmsglobalsender.

I am not sure if the 2 things are related to each other.


2006-05-16 14:05:45 [31796] [7] INFO: mmsc for defg00930 resolved
to: my.mmsc.dns
2006-05-16 14:06:19 [31798] [9] PANIC: gwlib/octstr.c:2337:
seems_valid_real: Assertion `ostr-data == NULL' failed. (Called from
mmsglobalsender.c:217:sendMsg.)
2006-05-16 14:06:19 [31798] [9] PANIC:
/usr/local/bin/mmsrelay(gw_panic+0x175) [0x8082cda]
2006-05-16 14:06:19 [31798] [9] PANIC: /usr/local/bin/mmsrelay [0x808a21e]
2006-05-16 14:06:19 [31798] [9] PANIC:
/usr/local/bin/mmsrelay(octstr_get_cstr_real+0x26) [0x80856d7]
2006-05-16 14:06:19 [31798] [9] PANIC: /usr/local/bin/mmsrelay [0x80530e1]
2006-05-16 14:06:19 [31798] [9] PANIC: /usr/local/bin/mmsrelay [0x806065b]
2006-05-16 14:06:19 [31798] [9] PANIC: /usr/local/bin/mmsrelay [0x8079478]
2006-05-16 14:06:19 [31798] [9] PANIC: /lib/libpthread.so.0 [0x401ba4eb]
2006-05-16 14:06:19 [31798] [9] PANIC: /lib/libc.so.6(__clone+0x5a) [0x403f2b0a]
2006-05-16 14:06:24 [411] [4] INFO: mmsc for abcdefgh1100 resolved
to: my.mmsc.dns
2006-05-16 14:06:55 [413] [6] INFO: mmsc for defg01100 resolved to:
X-Mms-Transaction-Id: E0F199B2B63FF9
2006-05-16 14:08:09 [448] [4] INFO: mmsc for abcdefgh1100 resolved
to: my.mmsc.dns
2006-05-16 14:08:45 [451] [7] PANIC: gwlib/octstr.c:2340:
seems_valid_real: Assertion `ostr-len + 1 = ostr-size' failed.
(Called from mmsglobalsender.c:217:sendMsg.)
2006-05-16 14:08:45 [451] [7] PANIC:
/usr/local/bin/mmsrelay(gw_panic+0x175) [0x8082cda]
2006-05-16 14:08:45 [451] [7] PANIC: /usr/local/bin/mmsrelay [0x808a261]
2006-05-16 14:08:45 [451] [7] PANIC:
/usr/local/bin/mmsrelay(octstr_get_cstr_real+0x26) [0x80856d7]
2006-05-16 14:08:45 [451] [7] PANIC: /usr/local/bin/mmsrelay [0x80530e1]
2006-05-16 14:08:45 [451] [7] PANIC: /usr/local/bin/mmsrelay [0x806065b]
2006-05-16 14:08:45 [451] [7] PANIC: /usr/local/bin/mmsrelay [0x8079478]
2006-05-16 14:08:45 [451] [7] PANIC: /lib/libpthread.so.0 [0x401ba4eb]
2006-05-16 14:08:45 [451] [7] PANIC: /lib/libc.so.6(__clone+0x5a) [0x403f2b0a]
2006-05-16 14:08:50 [526] [4] INFO: mmsc for abcdefgh1100 resolved
to: my.mmsc.dns
2006-05-16 14:08:57 [528] [6] PANIC: gwlib/octstr.c:2337:
seems_valid_real: Assertion `ostr-data == NULL' failed. (Called from
mmsglobalsender.c:217:sendMsg.)
2006-05-16 14:08:57 [528] [6] PANIC:
/usr/local/bin/mmsrelay(gw_panic+0x175) [0x8082cda]
2006-05-16 14:08:57 [528] [6] PANIC: /usr/local/bin/mmsrelay [0x808a21e]
2006-05-16 14:08:57 [528] [6] PANIC:
/usr/local/bin/mmsrelay(octstr_get_cstr_real+0x26) [0x80856d7]
2006-05-16 14:08:57 [528] [6] PANIC: /usr/local/bin/mmsrelay [0x80530e1]
2006-05-16 14:08:57 [528] [6] PANIC: /usr/local/bin/mmsrelay [0x806065b]
2006-05-16 14:08:57 [528] [6] PANIC: /usr/local/bin/mmsrelay [0x8079478]
2006-05-16 14:08:57 [528] [6] PANIC: /lib/libpthread.so.0 [0x401ba4eb]
2006-05-16 14:08:57 [528] [6] PANIC: /lib/libc.so.6(__clone+0x5a) [0x403f2b0a]
2006-05-16 14:09:02 [563] [4] INFO: mmsc for abcdefgh0930 resolved
to: my.mmsc.dns
2006-05-16 14:13:41 [565] [6] INFO: mmsc for defg03000 resolved to: HTTP/1.
2006-05-16 14:14:07 [567] [8] INFO: mmsc for abcdefgh1100 resolved
to: HTTP/1.
2006-05-16 14:36:47 [568] [9] INFO: mmsc for abcdefgh1100 resolved
to: HTTP/1.
2006-05-16 14:37:23 [570] [11] INFO: mmsc for abcdefgh3000 resolved
to: HTTP/1.
2006-05-16 14:41:30 [563] [4] INFO: mmsc for defg01100 resolved to: HTTP/1.
2006-05-16 14:47:17 [565] [6] INFO: mmsc for defg00221 resolved to: HTTP/1.
2006-05-16 14:48:11 [567] [8] INFO: mmsc for abcdefgh1100 resolved
to: HTTP/1.
2006-05-16 14:57:27 [568] [9] INFO: mmsc for defg01100 resolved to: HTTP/1.
2006-05-16 15:18:34 [570] [11] INFO: mmsc for defg70540 resolved to: HTTP/1.
2006-05-16 15:20:14 [563] [4] INFO: mmsc for defg01100 resolved to: HTTP/1.
2006-05-16 15:22:43 [565] [6] INFO: mmsc for abcdefgh0770 resolved
to: HTTP/1.
2006-05-16 15:26:06 [567] [8] INFO: mmsc for defg01858 resolved to: HTTP/1.
2006-05-16 15:26:43 [568] [9] INFO: mmsc for abcdefgh1100 resolved
to: HTTP/1.
2006-05-16 15:28:02 [570] [11] INFO: mmsc for defg01100 resolved to: HTTP/1.
2006-05-16 15:31:05 [563] [4] INFO: mmsc for defg00070 resolved to: HTTP/1.
2006-05-16 15:35:54 [565] [6] INFO: mmsc for defg00070 resolved to: HTTP/1.
2006-05-16 15:38:39 [568] [9] INFO: mmsc for abcdefgh0070 resolved
to: HTTP/1.
2006-05-16 15:43:39 [563] [4] INFO: mmsc for abcdefgh0070 resolved
to: HTTP/1.
2006-05-16 15:53:39 [567] [8] INFO: mmsc for abcdefgh0070 resolved
to: HTTP/1.
2006-05-16 16:01:08 [568] [9] INFO: mmsc for defg01100 resolved to: HTTP/1.
2006-05-16 16:08:39 [563] [4] INFO: mmsc for abcdefgh0070 resolved
to: HTTP/1.
2006-05-16 16:09:36 [565] [6] INFO: mmsc for defg70540 resolved to: HTTP/1.
2006-05-16 16:10:15 [567] [8] INFO: mmsc for defg70540 resolved to: HTTP/1.

___
Users 

[Users] x-wap-profile missing/required

2006-05-15 Thread Deon van der Merwe
Hi,

We are tracing a problem with a Motorola V3i submitting a message to
mbuni.  Thing is that the phone does not include the x-wap-profile
HTTP header.  So: the phone must be broken!!!  Reading the specs [ETSI
TS 126 234 V6.6.0 (2005-12)], it turns out (to my surprise) that the
x-wap-profile is not a required header.
quote
5.2.5 Signalling of profile information between client and server
When a PSS client or server support capability exchange it shall
support the profile information transport over both HTTP and RTSP
between client and server as defined in clause 9.1 (including its
subsections) of the WAP 2.0 UAProfspecification [40] with the
following additions:
- The x-wap-profile and x-wap-profile-diff headers may not be
present in all HTTP or RTSP request. That is, the requirement to send
this header in all requests has been relaxed.
/quote

Here is how mbuni fails:
2006-05-15 17:54:14 [23380] [0] PANIC: gwlib/octstr.c:2340:
seems_valid_real: Assertion `ostr-len + 1 = ostr-size' failed.
(Called from gwl
ib/octstr.c:1310:octstr_strip_nonalphanums.)
2006-05-15 17:54:14 [23380] [0] PANIC:
/usr/local/bin/mmsproxy(gw_panic+0x175) [0x8085dba]
2006-05-15 17:54:14 [23380] [0] PANIC: /usr/local/bin/mmsproxy [0x808d341]
2006-05-15 17:54:14 [23380] [0] PANIC:
/usr/local/bin/mmsproxy(octstr_strip_nonalphanums+0x2c) [0x808aa11]
2006-05-15 17:54:14 [23380] [0] PANIC:
/usr/local/bin/mmsproxy(main+0x24c) [0x8052afc]
2006-05-15 17:54:14 [23380] [0] PANIC:
/lib/libc.so.6(__libc_start_main+0xab) [0x4035144b]
2006-05-15 17:54:14 [23380] [0] PANIC: /usr/local/bin/mmsproxy [0x80527b1]


This is where it goes wrong:
   h.vasp = NULL;
   h.profile_url = NULL;
   h.ua = http_header_value(h.headers, octstr_imm(User-Agent));
   /* Get the profile URL and store it. Has effect of
fetching if missing. */
   if ((h.profile_url = http_header_value(h.headers,

octstr_imm(X-Wap-Profile))) == NULL)
h.profile_url = http_header_value(h.headers,
octstr_imm(Profile));
   octstr_strip_nonalphanums(h.profile_url);

So, is there any way in which we can include a default profile into
the configuration?
Or, maybe someone else has a better option/solution?

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] x-wap-profile missing/required

2006-05-15 Thread Deon van der Merwe
Hi Paul,

On 5/15/06, Paul Bagyenda [EMAIL PROTECTED] wrote:
 fixed hopefully in CVS. Please let me know.

yup- it is working.  Thanks allot Paul.

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] mbuni.conf + fake mms ? MMS file

2006-05-15 Thread Deon van der Merwe
Hi,

On 5/16/06, kartikay malhotra [EMAIL PROTECTED] wrote:
 Hi!

 I intend to use Mbuni as a gateway connected to an operator MMC. Once I
 receive MMS at my gateway, I would want to send it to a HTTP Server
 (preferably intact). There I would want to dump it in a database.

  I can handle the server and DB part. Wat I do not know:

 1. Format of incoming MMS; I mean protocol. (HTTP over TCP/IP)?
 2. How to handle that MMS?

I think that here I can help a little...  the message sent to you by
mbuni MMSC is formatter as MM7/HTTP/TCPIP.  To receive these messages,
I use the openwave SDK.  My receiver class looks somethinh like this:

  class MessageReceiver
   extends com.openwave.mms.mm7.MessageListenerAdapter {

protected com.openwave.mms.mm7.RelayConnection mReceiveConnection = null;

public MessageReceiver() {
  try {
mReceiveConnection =
com.openwave.mms.mm7.RelayConnection.createReceiver(mReceivePort,
false);
mReceiveConnection.setMessageListener(this);
  } catch (java.lang.Exception vException) {
mLogger.error(vException.getMessage(), vException);
  }
}

public com.openwave.mms.mm7.Response processDeliverRequest(
com.openwave.mms.mm7.DeliverRequest deliverRequest) {
  try {
mLogger.debug(TransactionID:  + deliverRequest.getTransactionID());
mLogger.debug(Sender:  + deliverRequest.getSender());
java.util.Vector vRecipients = deliverRequest.getRecipients();
for (int i = 0; i  vRecipients.size(); ++i) {
  mLogger.debug(recipient:  +
((com.openwave.mms.mm7.Recipient) vRecipients.get(i)).getAddress());
}
mLogger.debug(Subject:  + deliverRequest.getSubject());
javax.mail.internet.MimeBodyPart part = deliverRequest.getRawContent();
mLogger.debug(ContentType:  + part.getContentType());
mLogger.debug(Filename:  + part.getFileName());

java.lang.StringBuffer vContentBuffer = new java.lang.StringBuffer();
try {
  java.io.InputStream vContentInput = part.getInputStream();
  while (true) {
int vByte = vContentInput.read();
if (vByte == -1) {
  break;
} else {
  vContentBuffer.append((char) vByte);
}
  }
} catch (java.io.IOException vException) {
  mLogger.error(vException.getMessage(), vException);
}

int vSequence = (int) mReceiveSequence.next();
java.lang.String vContent = vContentBuffer.toString();
java.lang.String vFilename = saveFile(part.getFileName(),
vSequence, vContent);
  } catch (javax.mail.MessagingException vException) {
mLogger.error(vException.getMessage(), vException);
  } catch (com.openwave.mms.mm7.APIException vException) {
mLogger.error(vException.getLocalizedMessage() +  ( +
vException.getErrorCode() + ));
mLogger.error(vException.getMessage(), vException);
  } catch (java.lang.Exception vException) {
mLogger.error(vException.getMessage(), vException);
  }

  // create a response object and send it back to the Openwave MMSC relay
  com.openwave.mms.mm7.DeliverResponse response = new
com.openwave.mms.mm7.DeliverResponse();
  response.setStatusCode(com.openwave.mms.mm7.ErrorCode.SUCCESS);
  response.setStatusText(got it!);
  return response;
}

protected java.lang.String saveFile(
java.lang.String aFilename,
int aSequence,
java.lang.String aContent) {
  java.lang.String vFilename = mFileCacheDirectory + aSequence +
- + aFilename;
  mLogger.debug(filename for  + aFilename +  =  + vFilename);
  try {
java.io.FileWriter vWriter = new java.io.FileWriter(vFilename);
vWriter.write(aContent);
vWriter.flush();
vWriter.close();
  } catch (java.lang.Exception vException) {
mLogger.error(vException.getMessage(), vException);
  }
  return vFilename;
}
  }

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


[Users] MSISDN for WAP2 subscribers

2006-05-12 Thread Deon van der Merwe
Hi,

For WAP1 devices resolving requests from IP address to MSISDN is done
nicely by Kannel.  For WAP2 devices there is a little gap...  we would
like to share the following 2 scripts that we use to resolve IP's to
MSISDN for WAP2 devices on a Mbuni installation.

- the first script is used in the mbuni config as the mbuni detokenize
shell.  Config is something like this:
  detokenizer-library = /usr/local/lib/mbuni/libmmsc_detokenize_shell.so
  detokenizer-module-parameters = /home/mbuni/bin/detokenizer
- the second is used inside squid to add the msisdn into the URL.
Squid config looks something like this:
  redirect_program /usr/local/bin/msisdn-from-radius
  acl msisdn_domains dstdomain my.mmsc.dns.name
  redirector_access allow msisdn_domains

So: perhaps it is of use to some other people as well...




#!/bin/bash
# If the request is coming from the localhost, the client is making the
# request via the local proxy (SQUID).  So then we get the MSISDN out of
# the URL.
# For other direct connections, it gets the MSISDN from our server that gets
# the radius accounting messages from the GGSN.
# http://www.truteq.co.za

DATE=`date`
MSISDN=
if [ $2 == 127.0.0.1 ]
then
  MSISDN=`echo $1 | awk -F'=' '{print $2}'`
else
  MSISDN=`echo $2 | nc 192.168.100.10 50163`
fi
echo $DATE $0 $1 $2 $3 = $MSISDN  /var/log/mbuni/detokenizer.log
echo $MSISDN





#!/bin/bash
# A little squid url redirect module.  It will append the MSISDN to the URL
# provided.  It gets the MSISDN from our server that gets the radius
# accounting messages from the GGSN.
# http://www.truteq.co.za
# TODO:
#   Currently not checking if there is already ? in the URL

while read line  # For as many lines as the input file has...
do
  DATE=`date`
  URL=`echo $line | awk '{print $1}'`
  IP_ADDRESS=`echo $line | awk '{print $2}' | awk -F'/' '{print $1}'`
  MSISDN=`echo $IP_ADDRESS | nc 192.168.100.10 50163`
  echo $DATE $line: $IP_ADDRESS = $MSISDN  /var/log/squid/msisdn.log
  echo $URLmsisdn=$MSISDN
done
exit 0

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] Nokia 9300 issues

2006-05-11 Thread Deon van der Merwe
Hi,

After allot of wonder support from Paul, the problem was not with
mbuni but rather with my kannel setup.  The last config line in the
sendsms-user group was missing:
group = sendsms-user
username = foo
password = bar
max-messages = 10
concatenation = true


On 5/5/06, Paul Bagyenda [EMAIL PROTECTED] wrote:
 Hi,

 If I understand correctly, the phone can send the message fine but
 cannot retrieve a message. The most like cause is a bad URL. Can you
 send me (privately if you prefer it) the logs (including Kannel logs)
 so I can see what's going on?

 On May 04, 2006, at 20:26, Deon van der Merwe wrote:

  Hi All,
 
  Having started testing on a live site today... some issues with the
  client's phones.  In particular with the Nokia9300.  The phone can
  send to the MMSC just fine.  The problem comes in with the retreive
  from the phone.
 
  We have seen 2 types of responses by the MMSC:
  1) The phone makes the post with the correct ref, and that is it.
  From the tcpdump:
  ==
  POST / HTTP/1.1
  Host: mms
  Accept: application/vnd.oma.drm.message, */*,
  application/vnd.wap.mms-message, application/vnd.wap.sic
  Accept-Charset: utf-8
  Accept-Encoding: gzip,deflate
  Accept-Language: en
  User-Agent: Nokia9300/05.22 Series80/2.0 Profile/MIDP-2.0
  Configuration/CLDC-1.1
  Content-Length: 42
  Content-Type: application/vnd.wap.mms-message
  x-wap-profile: http://nds1.nds.nokia.com/uaprof/N9300r100.xml;
 
  [EMAIL PROTECTED]/1.1 200 OK
  Server: Kannel/1.4.0
  Content-Length: 8
  Pragma: no-cache
  Cache-Control: no-cache
  Content-Type: text/plain
  Received
  ==
  2) We see the post request come in from the phone, and mbuni replies
  with a Status: Rejected (0x82)
 
  Has anyone else used this phone?
  WHere can I find out more about the reject responses?
 
  ___
  Users mailing list
  Users@mbuni.org
  http://mbuni.org/mailman/listinfo/users_mbuni.org


 ___
 Users mailing list
 Users@mbuni.org
 http://mbuni.org/mailman/listinfo/users_mbuni.org


___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


Re: [Users] Support for legacy phones

2006-05-06 Thread Deon van der Merwe
Hi Dziugas

On 4/27/06, Dziugas Baltrunas [EMAIL PROTECTED] wrote:
 Hi,

 for initial start, please see mms-notify-text option in user guide.
 This is, however, just an option to write informational message. For
 better legacy support you could define one mms-vasp with
 mms-to-local-copy-handler set to true for storing all MMS to a single
 storage obviously reachable via Web/WAP interface. Knowing necessary
 message parameters you can send SMS or WAP Push message for the user
 containing the URL (or ID) where he/she can view the message. This can
 be done by the scripts, triggered by prov-server-notify-script or
 prov-server-sub-status-script.


Thanks allot... I am working on a setup like this.

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


[Users] Nokia 9300 issues

2006-05-05 Thread Deon van der Merwe
Hi All,

Having started testing on a live site today... some issues with the
client's phones.  In particular with the Nokia9300.  The phone can
send to the MMSC just fine.  The problem comes in with the retreive
from the phone.

We have seen 2 types of responses by the MMSC:
1) The phone makes the post with the correct ref, and that is it. 
From the tcpdump:
==
POST / HTTP/1.1
Host: mms
Accept: application/vnd.oma.drm.message, */*,
application/vnd.wap.mms-message, application/vnd.wap.sic
Accept-Charset: utf-8
Accept-Encoding: gzip,deflate
Accept-Language: en
User-Agent: Nokia9300/05.22 Series80/2.0 Profile/MIDP-2.0 Configuration/CLDC-1.1
Content-Length: 42
Content-Type: application/vnd.wap.mms-message
x-wap-profile: http://nds1.nds.nokia.com/uaprof/N9300r100.xml;

[EMAIL PROTECTED]/1.1 200 OK
Server: Kannel/1.4.0
Content-Length: 8
Pragma: no-cache
Cache-Control: no-cache
Content-Type: text/plain
Received
==
2) We see the post request come in from the phone, and mbuni replies
with a Status: Rejected (0x82)

Has anyone else used this phone?
WHere can I find out more about the reject responses?

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org


[Users] Support for legacy phones

2006-04-18 Thread Deon van der Merwe
Hi,

What is the general ideas used for supporting phones that does not
have MMS capabilities.  Subscriber A sends to subscriber B, but B's
phone does not have support for MMS.  Can (and how) mbuni send a plain
text SMS to subscriber B with a URL that can be retreived by some
other means?

If there is no support for it currently: where is the best place to
start adding something like this?

___
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org