Trigger SMS via SOA / UMS does not receive the sender address from the sdpmessagingdriver-smpp driver configuration settings

Question

Description:

• We use the sdpmessagingdriver-smpp driver hosted on the SOA server to send SMS messages.
• We configured the SMPP driver properties to "Sender Address" & "Default Sender Address".
• When we try to send an SMS, it crashes with the error message "Invalid Source Address".

After some investigation, we found that the sender address in the submit_sm request is null, which causes the "Invalid Source Address" problem. Now the question is, why is the sender address empty in the send request if it is already configured in the SMPP driver configuration settings? Do I need to configure the sender address somewhere else? Is there any configuration file for setting this parameter

REFERENCE SCREENS:

SMPP driver configuration:

• You can see that the sender address and the default sender address are provided in the configuration.

Message Status (SMS Failure Log):

• The screenshot below shows failed SMS messages with an empty sender address.

Backend Error Log:

[2017-10-17T10: 33: 16.806 + 05: 30] [WLS_SOA] [ERROR] [SDP-25700] [oracle.sdp.messaging.driver.smpp] [tid: Workmanager :, Version: 0, Scheduled = false , Started = false, Wait time: 0 ms \ n] [userId: OracleSystemUser] [ecid: 49d20b62a8084325: -5336381e: 15f247fea2f: -8000-000000000001c322,0] [APP: usermessagingdriver-smpp] An unexpected exception was detected. [[oracle.sdp.messaging.driver.DriverException: Invalid source address [a] in oracle.sdpinternal.messaging.driver.smpp.SMPPDriver.send (SMPPDriver.java:1073) in oracle.sdpinternal.messaging.driver.smpp. SMPPDriver.send (SMPPDriver.java:3268) in oracle.sdpinternal.messaging.driver.smpp.SMPPDriver.send (SMPPDriver.java:2849) in oracle.sdpinternal.messaging.driver.smpp.SMPPDriver.send (SMPPDriverjava 2724) in oracle.sdpinternal.messaging.driver.smpp.SMPPManagedConnection.send (SMPPManagedConnection.java:95) in oracle.sdpinternal.messaging.driver.DriverConnectionImpl.send (DriverConnectionImpl.java:41) in oracle.sdpinis.patcher.patcher .DriverDispatcherBean.onMessage (DriverDispatcherBean.java:296) at sun.reflect.GeneratedMethodAccessor1629.invoke (unknown source) in sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.ava .java: 606) in com.bea.core.repackage d.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection (AopUtils.java{10) in com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint (ReflectiveMethodbevcore.vocation.vocation repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed (ReflectiveMethodInvocation.java:149) at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke (ExposeInvocationInterceptor.javabe repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed (ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed (DelegatingIntroductionInterceptor.java13be.java13be.core13) repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke (DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed (Reflective MethodInvocation.java:171) in com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke (JdkDynamicAopProxy.java:204) on com.sun.proxy. $ Proxy532.onMessage (Unknown source) in oracle.sdpinternal.messaging.dispatcher.DriverDispatcherBean_xfokw2_MDOImpl .__ WL_invoke (Unknown Source) in weblogic.ejb.container.internal.MDOMethodInvokerlist.svn. .dispatcher.DriverDispatcherBean_xfokw2_MDOImpl.onMessage (Unknown Source) in oracle.sdpinternal.messaging.jmsmessagereceiver.ResourceAdapterImpl $ RaMessageListener.onMessage (ResourceAdapterImpl.java:167) werme.suer.messer in weblogic.work.j2ee.J2EEWorkManager $ WorkWithListener.run (J2EEWorkManager.java:184) in weblogic.work.DaemonWorkThread.run (DaemonWorkThread.java:30)]] [2017-10-17T10: 33: 16.807 + 05: 30 ] [WLS_SOA] [NOTICE] [SDP-26003] [oracle.sdp.messaging.driver.dispatcher] [tid: Workmanager :, Version: 0, Scheduled = false, Started = false, Wait time: 0 ms \ n] [ userId: OracleSystemU ser] [ecid: 49d20b62a8084325: -5336381e: 15f247fea2f: -8000-000000000001c322,0] [APP: usermessagingdriver-smpp] The dispatcher sent a message with the identifier: eb50c4cdc0a800ab12d5fbbdbbbdba46.

Answer 1

We found out and solved this problem. Here is his resolution. Maybe this can help someone else and save their precious time.

The SMPP driver configured in the Oracle EM console has an error due to which the source address and source address are always zero by default, even if you pass it from the driver configurations.

This was due to the multiple source address in the SMSC, and our system was transmitting a null value in the "Source Address" field. Because of this, the SMSC was not able to recognize the correct source address and throw an "Invalid Source" Address "exception.

If a single / static source address is configured in the SMSC, you can pass null values, and the SMSC will automatically recognize the source address.

Answer 2

I am facing the same problem but cannot understand your solution. Can you clarify this?