OK, so I found the problem with omit-empty not working. FYI
I was just bouncing off a fake http loopback that was returning 500 to the service request. Turns out that any with any response other then 200 or 202, the smsbox immediately inject "Could not fetch content, sorry." in the body content. Then the omit-empty rule is ignored as the content is no longer empty. Cleanup up my loopback a bit and works fine now. Thx again guys. Brian ________________________________ From: Brian McCavour <[email protected]> To: Juan Luis Gómez Correa <[email protected]>; Rene Kluwen <[email protected]>; "[email protected]" <[email protected]> Sent: Tuesday, January 15, 2013 4:08:08 PM Subject: Re: block sms-service response to bearerbox Ah clever, that worked. I'll still need to find a way to make omit-empty work though, for the case where sometimes its needed and sometimes not. Thanks a lot guys. ________________________________ From: Juan Luis Gómez Correa <[email protected]> To: Brian McCavour <[email protected]>; Rene Kluwen <[email protected]>; "[email protected]" <[email protected]> Sent: Tuesday, January 15, 2013 3:54:56 PM Subject: Re: block sms-service response to bearerbox Try with max-messages=0 From: Brian McCavour <[email protected]> Reply-To: Brian McCavour <[email protected]> Date: Tuesday, January 15, 2013 3:52 PM To: Rene Kluwen <[email protected]>, "[email protected]" <[email protected]> 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 <[email protected]> To: 'Brian McCavour' <[email protected]>; [email protected] 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:[email protected] [mailto:[email protected]] On Behalf Of Brian McCavour Sent: dinsdag 15 januari 2013 21:16 To: [email protected] 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
