Routing Problem

Routing Problem SearchSearch
Author Message
Ali Shahbour
New member
Username: Shahbour

Post Number: 12
Registered: 10-2005
Posted on Thursday, October 19, 2006 - 01:37 pm:   

Hello, i have two SMPP connection and on both i can receive and send one of them is MTC and the other is MBLOX.

MTC is checked as support any outbound message traffic.

MBLOX i didn't check the support any outbound message traffic but i added in the preferred SMSC connection 44 and then i tried +44, also the SenderAddress is 60070

i tried to send a message using http with 60070 as senderaddress adn to 44... UK, but it didn't go through the MBLOX where i wanted it to go.

Should i do any thing more please update me

MedSalimALI
Frequent Contributor
Username: Salim

Post Number: 104
Registered: 04-2005
Posted on Friday, October 20, 2006 - 07:19 pm:   

Hi Ali,

Whenever you desabled an outbound message, the SMPP account linked on it cannot be used to send SMS.
So you need to enable it, and then as you are able to send via MTC account, also you can define a Sender address 60070 in MBLOX account to be used to avoid conflit.
NowSMS check the Default sender address to choose an account in sending message SMS/MMS, so you will not get any conflit. if NowSMS didn't find a default sender address, it will use the +44...+44565 to define the outbound enabled facilities...
Bryce will give more details, just to share our experience until he come....

salim....
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6710
Registered: 10-2002
Posted on Friday, October 20, 2006 - 09:36 pm:   

Hi Ali,

One common point of confusion ... make sure that in the "Preferred SMSC Connection" list you have "44*" and "+44*" (instead of just "44" or "+44").

If you defined "Default Sender Address" for this SMSC connection as "60070", then any messages that you submitted via HTTP with "&Sender=60070" in the URL request should have been submitted via this interface. If they were not, then I would like to see an SMSDEBUG.LOG that shows you submitting the message via HTTP ... that way, I can see if something needs to be changed in the way the HTTP request is being formatted. (Enable the SMSDEBUG.LOG on the "Serial #" page of the configuration dialog.)

-bn