This sounds similar to a problem I experienced setting up an MMSC
outside the network operator's VAS network.
Here in South Africa the phones are configured by the operators to
retrieve MMS via an 'MMS Proxy' access point which is constrained to
the RADIUS/VAS network on which additional headers are available. This
is NOT the same access point ('WAP Gateway') that is used for internet
browsing, and in fact cannot be used to reach the internet at large.
Question: can you hit your MMSC via the web browser on the phone
whilst using the MMS access point? I cannot hit mine. I have to
reconfigure the phone's MMS client to use the 'WAP' access point
before I can hit the MMSC - and then without RADIUS-sourced headers
identifying the handset.
In order to host a public MMSC under such conditions (in ZA) one has
to have the MMSC hosted on the Secure Network Operator's
infrastructure (RADIUS/VAS network). If you can reconfigure the
handsets you can conduct tests against a 'public' MMSC.
Regards,
James.
On 10/1/07, P. A. Bagyenda <[EMAIL PROTECTED]> wrote:
>
>
> On Oct 01, 2007, at 17:07, Theis Borg wrote:
>
> Thanks for the quick reply Paul.
>
> The two checks:
>
> 1. Tried to do the interference test on the companys flatscreen TV – no
> interference available when sending an SMS to myself. Will test at home
> where I have available interference :-)
>
> Yes they don't react. CRTs do.
>
>
> 2. Yes – my phone is setup to point at my server. The phone must be
> connected to the MMSC – otherwise I would not be able to send the MMS into
> the system – right?
>
>
> Indeed. Apologies. I didn't understand.
>
> The project startet with me going to make the services only, then it evolved
> to include the VAS as well. Unfortunately our customer is _very_ slow to
> create the connection between their MMSC and our VAS. So we tried with an
> other customer. Same story – weeks went by. So I decided that our company
> needs our own MMSC so we can demo our products for potential customers. The
> idea is that when the customer at some point opens up for the connection we
> will simply point their MMSC to our VAS. Sothats why I have the full setup
> with MMSC and VAS.
>
> One thing at a time. My first test will not include the VAS – just a simple
> test that the MMSC works and that we can send and receive MMS'es. Test two
> will include the VAS and the services.
>
> I hope I will be back with an answer on the interference test tonight.
> Again: thanks for your help.
>
>
> That indeed is the first test: To see if your phone is receiving any SMS.
>
> Be sure as well that you have concatenate = true set in your send-sms-user
> config of Kannel. This is a common cause of problems: MMS notifications will
> typically consist of 2 or more concatenated SMS, which Kannel must split
> right.
>
>
> q:o) Theis
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul
> Bagyenda
> Sent: 1. oktober 2007 15:27
> To: Theis Borg
> Cc: [email protected]
> Subject: Re: [Users] Problem with setup of mbuni
>
> Hi,
>
> Sounds like your phone may not be receiving the notification, or your phone
> has not been configured to talk to the Mbuni MMSC. To check if your phone is
> receiving the notification, you want to check if it shows any activity (one
> crude way is to have it near a radio or TV and watch out for any
> interference on the radio/TV consistent with a phone transacting with the
> network). For the second step, you need to check that your phone's MMSC
> address is the HTTP URL of the mbuni MMSC, not that of your operator.
>
> The other area you need to be clear on is whether you want to run your own
> MMSC (seems like that's what you've done) or merely want a VAS GW for
> sending/receiving messages from your existing operator. A bit confusing at
> first I know, but with help clarity can be achieved!
>
> Paul.
>
> On 10/1/07, Theis Borg < [EMAIL PROTECTED]> wrote:
>
>
> Hi all.
>
>
>
> I'm trying to setup a complete solution with kannel, MMSC, VAS and services.
> Installation of packages went fine. Kannel is connected to operator and can
> send SMSes.
>
>
>
> My first test is now to post an MMS to myself.
>
>
>
> Sending the MMS looks fine – the mmsproxy/mmsrelay catches the MMS and tells
> the Kannel to push out a notification that a MMS is ready for download. The
> smsbox/bearerbox receives the notification message and pushes it to the
> phone:
>
>
>
> 2007-10-01 13:58:05 [19197] [2] DEBUG: HTTP: Creating HTTPClient for
> `127.0.0.1'.
>
> 2007-10-01 13:58:05 [19197] [2] DEBUG: HTTP: Created HTTPClient area
> 0x814f088.
>
> 2007-10-01 13:58:05 [19197] [3] INFO: smsbox: Got HTTP request
> </cgi-bin/sendsms> from <127.0.0.1>
>
> 2007-10-01 13:58:05 [19197] [3] INFO: sendsms used by <tdc>
>
> 2007-10-01 13:58:05 [19197] [3] INFO: sendsms sender:<tdc:10505> (127.0.0.1)
> to:<004529492804> msg:<ESC^F^C¾¯204214202230-qf9884.3.x983.31>
>
> 2007-10-01 13:58:05 [19197] [3] DEBUG: Stored UUID
> 89ab22dc-2ce8-4484-8d24-3278949e2e90
>
> 2007-10-01 13:58:05 [19197] [3] DEBUG: message length 131, sending 1
> messages
>
> 2007-10-01 13:58:05 [19197] [3] DEBUG: Status: 202 Answer: <Sent.>
>
> 2007-10-01 13:58:05 [19197] [3] DEBUG: Delayed reply - wait for bearerbox
>
> 2007-10-01 13:58:05 [19197] [0] DEBUG: Got ACK (0) of
> 89ab22dc-2ce8-4484-8d24-3278949e2e90
>
> 2007-10-01 13:58:05 [19197] [0] DEBUG: HTTP: Resetting HTTPClient for
> `127.0.0.1'.
>
>
>
> And then nothing happens...
>
>
>
> Anyone else have the same problem? How can I debug what went wrong?
>
>
>
> Hope you guys can help an mbuni newbie...
>
>
>
> BR
>
>
>
> q:o) Theis
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.mbuni.org/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.mbuni.org/mailman/listinfo/users
>
>
--
Regards,
James
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
