Same TLV Value for 2 Different Aggregators

Same TLV Value for 2 Different Aggregators SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through January 22, 2009 » Same TLV Value for 2 Different Aggregators « Previous || Next »
Author Message
Volodymyr Mandrychenko
New member
Username: Vmandrychenko

Post Number: 7
Registered: 09-2007
Posted on Friday, November 28, 2008 - 07:30 pm:   

Hello,

We are using Now Sms 2008. We may be connecting to 2 different aggregators for US and Canada. There is a possibility that both will use same tlv values with different meanings.

Can you tell me how to configure this under now sms.

I have already tried to move [SMPPOptions] section under each SMPP connection section [SMPP - 10.40.20.34:5000]. Example:

[SMPP - Host1:4444]
RouteName=Connection1
SMPPVersion=v3.4
UserName=username
Password=pass
[SMPPOptions]
operator=1402,Integer,
tariff=1403,Integer,
sessionid=1404,String,
servicedesc=1405,String,

[SMPP - Host2:5555]
RouteName=Connection2
SMPPVersion=v3.4
UserName=smppclient
Password=client123
[SMPPOptions]
operator=1402,String, <-- different type adn value from above
tariff=1403,String, <-- different type adn value from above
sessionid=1404,String,
servicedesc=1405,String,


Above scenario does not seem to work. Now sms randomly picks up either 1 set of setting or the other, regardless of RouteName.

Is there any way to make this scenario work?

PS: I will have 2 binds for the same shortcode that is why I use SMSCRoute/RouteName. Canadian carriers will use connection1 and us carriers will use connection2.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 276
Registered: 08-2008
Posted on Monday, December 01, 2008 - 04:16 pm:   

Hi,

Unfortunately, there's no support for this type of situation.

It's a known limitation that thankfully we do not encounter very often.

Two [SMPPOptions] sections will definitely not work. As you have experienced, these will be seen as a single section, and if there are duplicate option names, one of them will be selected randomly.

That said, there is a way to handle this for outbound messaging (MT), just not for inbound messaging (MO).

You could do this:

[SMPPOptions]
operator=1402,Integer,
tariff=1403,Integer,
sessionid=1404,String,
servicedesc=1405,String,
CDNoperator=1402,String,
CDNtariff=1403,String,

This would require that you use a different option name when submitting to the other service provider. (They would likely have different values that you would need to specify anyway, so this may not be a problem.)

That would work fine for the outbound messaging.

However, for the inbound messaging (messages received from the service provider), NowSMS would be confused parsing these values.

--
Des
NowSMS Support

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