MMSC Routing via MM7 Default Routing Option

MMSC Routing via MM7 Default Routing Option SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through June 21, 2007 » MMSC Routing via MM7 Default Routing Option « Previous || Next »
Author Message
DJ Khan
New member
Username: Dkhanmam

Post Number: 4
Registered: 01-2007
Posted on Sunday, February 04, 2007 - 02:00 am:   

Hi:

I have mm7 application where I am routing inbound MMS messages via mm7. I've noticed that when I use the "To VASP (deliver format)" Connection Type option, the MSISDN of the MMS originator is not being passed on.

However, when I used "Default" Connection Type I am seeing "SENDER-INFO".

The documentation is not clear - what is the difference in messaging handling between default and "To VASP" ?


Thank you !
MedSalimALI
Frequent Contributor
Username: Salim

Post Number: 114
Registered: 04-2005
Posted on Sunday, February 04, 2007 - 11:40 am:   

Hello Dj Khan,

The good way of routing MMS via mm7, is the "To MMSC (Submit format)" into operator MMSC....

However Malcom or Bryce will give you more details, but I was wanted to say that either you act as MMSC or MM7 to operator MMSC, you should note that "default" is the choice of NowSMS in case you didn't setup any default connection type...
can you give details to whome you are routing to...

Salim
DJ Khan
New member
Username: Dkhanmam

Post Number: 5
Registered: 01-2007
Posted on Sunday, February 04, 2007 - 03:23 pm:   

Users send MMS to my short code. This message needs to be routed to my app via mm7 and I would like to see who is sending it. Thus I need the sender info. For some reason the only way to get it is to enable the Default option.
Malcolm - Now Support
Moderator
Username: Malcolm

Post Number: 166
Registered: 12-2006
Posted on Monday, February 05, 2007 - 05:23 pm:   

I have not seen this problem. "Allow Sender Address Override" is checked, correct?

-Malcolm
DJ Khan
New member
Username: Dkhanmam

Post Number: 6
Registered: 01-2007
Posted on Tuesday, February 06, 2007 - 10:39 pm:   

Yes - "allow override" is selected.

I am also filtering on incoming short-code to ensure that proper application receives corrects short code request.
Malcolm - Now Support
Moderator
Username: Malcolm

Post Number: 173
Registered: 12-2006
Posted on Wednesday, February 07, 2007 - 11:17 pm:   

How are the messages coming in to NowSMS? What protocol is NowSMS using to receive from the MMSC?

Is your VASP using standard MM7, or one of the non-standard options?

I suspect we need to see an MMSCDEBUG.LOG showing the message coming in from the MMSC and then getting routed to your VASP.
MedSalimALI
Frequent Contributor
Username: Salim

Post Number: 115
Registered: 04-2005
Posted on Sunday, February 11, 2007 - 09:06 am:   

Dj Khan,

Malcom is right, there will need more clear details, and the only way is to enable the MMSCDEBUG log...

I am susppecting an uncompatibility in the routing itself, either misunderstanding protocol, or misconfiguring...

Are you receiving MMS via MM7 standard ? and are you routing VASP by MM7 too?

Regards,
Salim

Login Login / Register Logout Logout Search Last 30 Days Topics Topics