So I found it in the code. Seems that you're right in that empty response +
omit-empty = true is all that's required....
I'm not sure why it doesn't work for me, but ill debug it and see.
Thanks.
/*
* Empty message? Two alternatives have to be handled:
* a) it's a HTTP sms-service reply: either ignore it or
* substitute the "empty" warning defined
* b) it's a sendsms HTTP interface call: leave the message empty
*/
if (octstr_len(msg->sms.msgdata) == 0 && msg->sms.sms_type == mt_reply) {
if (trans != NULL && urltrans_omit_empty(trans))
return 0;
else
msg->sms.msgdata = octstr_duplicate(reply_emptymessage);
}
________________________________
From: Brian McCavour <bmccav...@yahoo.com>
To: Rene Kluwen <rene.klu...@chimit.nl>; "users@kannel.org" <users@kannel.org>
Sent: Tuesday, January 15, 2013 3:52:18 PM
Subject: Re: block sms-service response to bearerbox
That's what I tried first, but I then get a msg sent to bearerbox with "Could
not fetch content, sorry."
Is there anther flag I'm missing in the bearebox or something?
________________________________
From: Rene Kluwen <rene.klu...@chimit.nl>
To: 'Brian McCavour' <bmccav...@yahoo.com>; users@kannel.org
Sent: Tuesday, January 15, 2013 3:39:28 PM
Subject: RE: block sms-service response to bearerbox
If you send an empty response in step 6, you can prevent Kannel from sending a
response sms by setting up
omit-empty = true in group = sms-service.
From:users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of
Brian McCavour
Sent: dinsdag 15 januari 2013 21:16
To: users@kannel.org
Subject: block sms-service response to bearerbox
Hi,
I just configured MO routing for the first time (using a http smsc and 2
smsboxes)
I am wonderig if there is a way to prevent responses from sms-service from
being sent back through the bearerbox.
Basically I am seeing (not sure about 1-2 of the ack orders but in general...):
1 - request to smsc
2 - smsc sends to smsbox
3 - smsbox send ack back to smsc
4 - smsbox sends sms-service request out
5 - service sends response to smsbox
6 - smsbox sends body or default text to smsc
7 - smsc sends ack to smsbox
8 - smsc sned-url pushes reponse
For some srvices though, there should be no sms sent based on the response.
So these steps 6,7,8 should be prevented.
Is there a clean way to do this through configuration, or do I just setup a
catchall url (dummy send-url in the smsc) for these ?
Thanks,
Brian
