On Tue, 2014-12-02 at 17:07, ha...@aeon.pk wrote:
> A good question! :-)
>
> I did use 63, as I am using it since quite some time (and it works).
> However on your alert, I checked the userguide to see that 63 should not be
> a combination at all. But I am pretty sure that I read it somewhere else
A good question! :-)
I did use 63, as I am using it since quite some time (and it works).
However on your alert, I checked the userguide to see that 63 should not be
a combination at all. But I am pretty sure that I read it somewhere else,
that's why I started using it. It would be something like
>with DLR mask 63
did you mean 31 ?
2014-12-01 23:34 GMT+03:00 ha...@aeon.pk :
> Resolved.
>
> In connection 'group = smsc', add line 'msg-id-type = 0x01' to fix the
> issue.
>
> On Tue, Dec 2, 2014 at 12:04 AM, ha...@aeon.pk wrote:
>
>> Hi,
>>
>> I have 2 SMSC connections. I am sending the sam
Resolved.
In connection 'group = smsc', add line 'msg-id-type = 0x01' to fix the
issue.
On Tue, Dec 2, 2014 at 12:04 AM, ha...@aeon.pk wrote:
> Hi,
>
> I have 2 SMSC connections. I am sending the same message with DLR mask 63
> (to get all possible delivery states). One SMSC connection is givin
Hi,
I have 2 SMSC connections. I am sending the same message with DLR mask 63
(to get all possible delivery states). One SMSC connection is giving me
submission-to-SMSC DLR and then DELIVERED DLR, both appearing in kannel
traffic logs. The other connection is only giving me submission-to-SMSC
DLR,
