Routing Based on Sender Id

Routing Based on Sender Id SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 07, 2008 » Routing Based on Sender Id « Previous || Next »
Author Message
KB commodity
New member
Username: Kbcomex

Post Number: 1
Registered: 12-2007
Posted on Wednesday, December 19, 2007 - 06:09 am:   

Sir:

Can you let me know whether routing based on Sender id is possible & how?

I have more than 10,000 Sender Id & using four SMSC

Three SMSC requires Sender Id authentication & one SMSC is dymanic

I want unregistered Sender id to be routed through Dynamic SMSC whereas other to be routed through other SMSC which requires sender Id to be registered

kb
KB commodity
New member
Username: Kbcomex

Post Number: 2
Registered: 12-2007
Posted on Thursday, December 27, 2007 - 03:16 am:   

Sir:

Waiting for a reply from your end

kb
KB commodity
New member
Username: Kbcomex

Post Number: 3
Registered: 12-2007
Posted on Wednesday, January 02, 2008 - 10:59 am:   

Sir\Madam:

Pls answer my query

kb
KB commodity
New member
Username: Kbcomex

Post Number: 4
Registered: 12-2007
Posted on Wednesday, January 30, 2008 - 09:22 am:   

Sir:

I am connecting to SMSC with two different port 1 & 2.

Port 1 as Transimitter & Port 2 as receiver. Now, I am connected & SMS are going & Delivery Reports are coming.

No, the problem is Now SMS is not forwarding Reprts to SMPP Clients.

What change shld I make in configuration so that Nowsms can forward Delivery reports to SMPP Clients.

kb
ashot shahbazian
Frequent Contributor
Username: Animatele

Post Number: 62
Registered: 06-2004
Posted on Tuesday, February 26, 2008 - 06:00 pm:   

enable tracksmppreceipts=yes setting

Well the easiest one is using TRX if the SMSC allows it.

If you are pooling the DLR off a bind that is essentially different (different port number) from your TX this setting alone won't work. try reading on the forum/specs about using different port settings in SMSC definition.

If you have only one or a few customers - you chould set the DLR to forward to respective user conntecions by specifying 2-way commands specific to the parrten (source/dest numbers) of each user message thread.

another solution - if you are behind a cisco router try configuring a "Reverse NAT" scenario - which is regardless of the port number you use from behind the Cisco to a particular IP address the Cisco would connect to one or the other port numbers you have for this SMSC. Hence, if the SMSC rejects RX connects at the port intended for TX and vice versa the server would eventually connect to both - while inside (in NowSMS) you are going to configure 2 concurrent connections - one TX and one RX to the same port number (that'll solve the problem of DLR not routing downstream)

I could ask our engineers if there's a simpler way of aliasing a port number or IP:port combination, e.g. setting up a proxy server of sorts in Windows?

...

I'd be curious how you'd solved it, please email me ashot.shahbazian@animatele.com
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7529
Registered: 10-2002
Posted on Wednesday, February 27, 2008 - 08:11 pm:   

The delivery reports should be routed automatically ... unless there is something unusual about their formatting. (NowSMS 2007 introduced a bug for one type of format that was not present in NowSMS 2006. That problem is now corrected in NowSMS 2008.)

It would help to see some details about the delivery receipts that you are seeing.

If you can setup a test system ... enable the SMSDEBUG.LOG in NowSMS ... submit a message and receive back a delivery report ... then post the details of the SMPP transaction from the resulting SMPPDEBUG.LOG file, then we'll get a clearer picture of your configuration and what might be happening.

-bn
douglas antonio
New member
Username: Douglasby

Post Number: 3
Registered: 02-2007
Posted on Thursday, March 27, 2008 - 01:12 pm:   

Dear Sir,
I still waiting for help.

Regards.

douglas

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