Re: REPOST : Problem with keepalive feature of emi2 and receive-port configuration

On a related topic, I thought I would ask the group if
they collectively or individually cared about this.

Our company connects to the EMI smsc at TIM, Italy's
largest provider.  (They serve about 22 million cellphones)

This SMSC is a bit brain-damaged, since TIM won't allow a direct
connection to the EMI protocol, they only allow an emulation
for their own security and throttling purposes.  
And their emulation doesn't accept type 31 messages at all,
in fact they shut the thing down.

Their peculiar usage is to use a message 60 (restart) instead as a 
keepalive.  To accomodate them, we need to change the kannel
code manually every time we get a new version, so we are sending
60 instead of 31.

Since this module is being changed continually anyway, does
anyone like/hate the idea of making the keepalive message 
configurable?

Thanks,
Steve