Receiving MMS service point/Mobile Dialog we can test with?

[Mike Blackstock]

Hi,

Is there a shared MMS service point or can I configure Mobile Dialog to test posting to our Multimedia Board component?  Not sure which one to try nowadays.

Thanks,
Mike Blackstock

--
Mike Blackstock
http://www.cs.ubc.ca/~michael

[Jim Udall]

There is a shared Service Point named ‘MAGIC MMS’.  If you preface your SMS to that SP with the discriminator ‘magic’, the message will be routed to that SP.

 

Alternately, if you send an MMS to that SP you should make sure your subject reads ‘magic’.  Similar routing will occur.

 

The telephone # associated with that SP is 778-320-6873

 

Jim

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.10.12/1909 - Release Date: 1/22/2009 7:08 AM

[Mike Blackstock]

Thanks Jim - we gave that a try without luck, but I'm still not sure it's not a problem at my end.  I'll keep digging.

One thing I did notice is that when I create a new Mobile Dialog instance, the only Messaging Interface for me available is MAGIC MMS with keyword prefix:magic.

I assume that Mobile Dialog will be getting those SMS and MMS messages if I create an instance of it.  Will the other components registered for MAGIC MMS callbacks on the keyword "magic" still get the message?

I haven't had much success with using the Service Point directly so I decided to try using it through Mobile Dialog by setting the "*" keyword callback manually.

I created a Mobile Dialog instance using MAGIC MMS and set the '*' keyword to point to our RESTBroker relay URL.
I sent the SMS message 'magic 161 blah' 

My app gets the SMS and does the "right thing".  woot!

I check the Mobile Dialog "Statistics" screen, and I see our message.  nice.

Next I try sending an MMS from a telus phone.  Nothing. Nothing in the MD "Statistics" screen, and oddly, there are two entries in the log for each SMS I sent previously now (same Date/Time, number, message, response).  huh?

I try an MMS from a Rogers account.  Nothing.

I'm going to look through the service point logs now.

Mike

On Thu, Jan 22, 2009 at 3:45 PM, Jim Udall <jim....@quickmobile.com> wrote:

There is a shared Service Point named 'MAGIC MMS'.  If you preface your SMS to that SP with the discriminator 'magic', the message will be routed to that SP.

 

Alternately, if you send an MMS to that SP you should make sure your subject reads 'magic'.  Similar routing will occur.

 

The telephone # associated with that SP is 778-320-6873

 

Jim

 

From: muse3-p...@googlegroups.com [mailto:muse3-p...@googlegroups.com] On Behalf Of Mike Blackstock
Sent: Thursday, January 22, 2009 3:39 PM
To: muse3-p...@googlegroups.com
Subject: Receiving MMS service point/Mobile Dialog we can test with?

 

Hi,

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.10.12/1909 - Release Date: 1/22/2009 7:08 AM

--
Mike Blackstock
http://www.mblackstock.com

[Clay Howey]

I think we need to move the MAGIC SIM to a different modem bank. Currently we have only one modem bank where MMS works, and there is one SAT and two Public Dreams installed in it. We can swap out one of the Public Dreams SIMs for the MAGIC SIM...

Cheers, Clay


Mike Blackstock <mikebla...@gmail.com>

Mike Blackstock <mikebla...@gmail.com> Sent by: muse3-p...@googlegroups.com Jan 22, 2009 04:39 PM Please respond to muse3-p...@googlegroups.com

To muse3-p...@googlegroups.com cc Subject Re: Receiving MMS service point/Mobile Dialog we can test with?

[Jim Udall]

/var/log/qm.log is a good log to look at.  These are the platform logs that (among other things) routes messages.  /var/log/Celtius.log is the log for the actually MMS gateway – which is marginally useful sometimes.

 

Poring thru qm.log:  I see the following significant events from yesterday:

1.        A number of inbound MMS messages were received on the interface associated with 778-320-6873.  These started around 4:00pm yesterday.  The first one I notice came fro 604-813-1586 and there was no subject.  The routing for that interface says “if there is no matched disrminator for this message, then the default Service Point for the message is “MMS and SMS’ associated with the user ‘veejay’.  I don’t know exactly who ‘veejay’ is, but undoubtedly I setup his Service Point like that.  In short… you would not receive the message.

2.       Around 4:30, I receive and MMS with ‘MAGIC 161 test’ in the subject.  This was matched to your service point ‘MAGIC MMS’ and routed to a Mobile Dialog you have on that service point.

3.       Looking at the Mobile Dialog logs (/var/log/diaog.log) I see it received the message and invoked your callback: http://camaro.mobilemuse.ca/~magic/rbrelay/receive.php?Channel=mblackstock.sms.in.  BTW, this is invoked for SMS as well as MMS and in both cases, you’re responding with an invalid XML response.  For SMS I get back simply ‘OK’ – which of course is not a valid XML stream.  For MMS, the response is text reading: ‘Couldn't move uploaded file.’

4.       A number of other MMS messages were received.  However, the subject lines contained things like:

a.       161 test

b.      Fw: Magic 161 test

 

In short, things are working as they should within both the MMS gateway and the platform.  However, you have some configuration/user/programming errors that are preventing anything wonderful from happening.

 

If you configure a Mobile Dialog and attach it to a Service Point, then any previous application using that Service Point will lose it (silently).

Version: 8.0.176 / Virus Database: 270.10.12/1911 - Release Date: 1/23/2009 7:28 AM

[Jim Udall]

Let’s not do that for the time being.  I’m not sure exactly what Magic is using their SIM for but being where it is, it has the distinct advantage of being able to send SMS to Bell/Telus customers – which may or may not be needed by them.  Let them decide if they want to gain MMS on that SIM at the cost of losing outbound SMS to Telus/Bell phones.  For the time being, they can use the shared MMS service point.

 

Jim

[Mike Blackstock]

Thanks Jim!

Mike

On Fri, Jan 23, 2009 at 8:52 AM, Jim Udall <jim....@quickmobile.com> wrote:

/var/log/qm.log is a good log to look at.  These are the platform logs that (among other things) routes messages.  /var/log/Celtius.log is the log for the actually MMS gateway – which is marginally useful sometimes.

 

Poring thru qm.log:  I see the following significant events from yesterday:

1.        A number of inbound MMS messages were received on the interface associated with 778-320-6873.  These started around 4:00pm yesterday.  The first one I notice came fro 604-813-1586 and there was no subject.  The routing for that interface says "if there is no matched disrminator for this message, then the default Service Point for the message is "MMS and SMS' associated with the user 'veejay'.  I don't know exactly who 'veejay' is, but undoubtedly I setup his Service Point like that.  In short… you would not receive the message.

2.       Around 4:30, I receive and MMS with 'MAGIC 161 test' in the subject.  This was matched to your service point 'MAGIC MMS' and routed to a Mobile Dialog you have on that service point.

3.       Looking at the Mobile Dialog logs (/var/log/diaog.log) I see it received the message and invoked your callback: http://camaro.mobilemuse.ca/~magic/rbrelay/receive.php?Channel=mblackstock.sms.in.  BTW, this is invoked for SMS as well as MMS and in both cases, you're responding with an invalid XML response.  For SMS I get back simply 'OK' – which of course is not a valid XML stream.  For MMS, the response is text reading: 'Couldn't move uploaded file.'

4.       A number of other MMS messages were received.  However, the subject lines contained things like:

a.       161 test

b.      Fw: Magic 161 test

 

In short, things are working as they should within both the MMS gateway and the platform.  However, you have some configuration/user/programming errors that are preventing anything wonderful from happening.

 

If you configure a Mobile Dialog and attach it to a Service Point, then any previous application using that Service Point will lose it (silently).

 

Jim

 

From: muse3-p...@googlegroups.com [mailto:muse3-p...@googlegroups.com] On Behalf Of Mike Blackstock

Sent: Thursday, January 22, 2009 4:39 PM
To: muse3-p...@googlegroups.com

Subject: Re: Receiving MMS service point/Mobile Dialog we can test with?

Version: 8.0.176 / Virus Database: 270.10.12/1911 - Release Date: 1/23/2009 7:28 AM

[Mike Blackstock]

Thanks again for the help Jim.

Big Screen: Multimedia Board now displays MMS photos contributed by
end users again. I think this *may* fit the bill for the Fearless
folks.

To try it out, I set up a multimedia board instance at this URL:

http://camaro.mobilemuse.ca:8080/ScreenWidgets/display/Multimedia_Board.jsp?channel=mblackstock.Multimedia_Board.1

Then send MMS photos to this number: 778-320-6873
with the subject:
magic 161 its me!

The photo will appear on the message board along with the subject and
the user's name if their number is registered with our Screen Widgets
system (otherwise it indicates "Anonymous").

Note that if several people have this URL up at the same time, one of
them may miss the message since we assume one screen per screen
identifier (161).

Feel free to contact me if you have questions about this.

Mike

On Fri, Jan 23, 2009 at 10:46 AM, Mike Blackstock
<mikebla...@gmail.com> wrote:
>
> Thanks Jim!
>
> Mike
>
> On Fri, Jan 23, 2009 at 8:52 AM, Jim Udall <jim....@quickmobile.com> wrote:
>>
>> /var/log/qm.log is a good log to look at. These are the platform logs that (among other things) routes messages. /var/log/Celtius.log is the log for the actually MMS gateway – which is marginally useful sometimes.
>>
>>
>>
>> Poring thru qm.log: I see the following significant events from yesterday:
>>

>> 1. A number of inbound MMS messages were received on the interface associated with http://camaro.mobilemuse.ca:8080/ScreenWidgets/display/Multimedia_Board.jsp?channel=mblackstock.Multimedia_Board.1. These started around 4:00pm yesterday. The first one I notice came fro 604-813-1586 and there was no subject. The routing for that interface says "if there is no matched disrminator for this message, then the default Service Point for the message is "MMS and SMS' associated with the user 'veejay'. I don't know exactly who 'veejay' is, but undoubtedly I setup his Service Point like that. In short… you would not receive the message.