Incoming sms using Webhook.

[vil]

Dear team,

Deployed a 3cx server on the Digital Ocean cloud server.
Took a trial subscription to 3cx.pro.
Our company has its own SMSC, which can send sms traffic using API or SMPP protocol.

3cx was able to configure it to send outgoing sms.
Here is the problem with configuring incoming sms, I have not found any manual on incoming traffic.

Can you tell me how to bring the incoming traffic?
Tried to send sms on Webhook 3cx, the message comes, but it feels as if the system does not understand how to process this type of traffic. Although in connections it is specified where to route calls and incoming traffic. As far as I understand the configuration of incoming calls and sms works on the same channel.

 

[KyriacosS_3CX]

Hi Vil,

The relevant document is:
https://www.3cx.com/docs/supported-sip-trunk-requirements/#h.9lv8vi548lbk

Best,
K.

 

[vil]

Thanks for the reply.

I managed to configure incoming sms traffic on 3sx.

Another case has arisen.
As far as I understand webhook generated by 3x should report on delivery automatically. But unfortunately when sending sms in the response is nothing, how can I get “sms delivery report”?

When sending sms to 3sx I get “204 no content” in reply. The sms is delivered to the user 3sx. But I would like to see the delivery report sent to SMSC.

 

[vil]

I see the text came in and was answered.
But the IP from which it came and to which it went is the same. Accordingly, it goes to the same place. But the reply does not come to SMSC. How can this be corrected? Please advise

 

[KyriacosS_3CX]

Hi,

I to assume the SMSC side is a custom system? Could you share some screenshots of the trunk setup page?

Thanks,
K.

 

[vil]

I use Alaris, do you need a screenshot in Alaris? Or from 3sx

 

[KyriacosS_3CX]

3CX, no idea about Alaris

 

[vil]

Attached are the settings from both platforms.

On the 3x platform the webhook was issued, which we use when requesting from alaris (POST method). Where it's mashed, everywhere it usually mentions webhook.

On the 3x platform there are no settings for incoming sms as I understand.
As API key and provider URL parameters are for outgoing sms, right?

 

[KyriacosS_3CX]

The Provider URL should be getting called for delivery report as well as outbound SMS.

 

[vil]

I have a separate trunk for outgoing,
API:
https://api.stertell.com:8002/api?u...mmand=submit&serviceType=A2P&longMessageMode=

One more question, how can I specify ANI DNIS Message in an arbitrary form? I mean it should not be attached to a template.


On Incoming:
I can try to create an inbound connection with login and password to accept reports. Is this necessary or is the problem something else?

 

[vil]

as I said before, the exchange is only on the local port lo.
I think this is the problem, that the webhook does not send the delivery report to the outside. Can you tell me how to fix the problem?

 

[KyriacosS_3CX]

The trunk where SMS come in needs a webhook defined to be able to return delivery reports.

 

[vil]

I'm not sure what you mean.

If you mean sending traffic from the SMSC to the webhook, that's what we do. We send to the webhook issued by 3xx under “SMS”.
Is that what you're talking about?

Is it possible for 3x to send a non 204 no content in response? 3CX return 204 No content, so it is impossible to determine the success/non-success of sending, and therefore the system will not expect DLR for such messages

 

[vil]

Dear team,

Do you have any news?