It is so complicated? I dont understand why it wasnt implemented from the begining...

Yes it is solved...

Dear Aleksandr,

for the record, I have writen to iridium support almost every week without response from anybody - till yesterday. I sent the required data on February 8th 2017! I would like to ask you (as CTO) for supervising of this proces.

Thank you

Miro

Dear Aleksander,

what does it mean - NOT A BUG? What are your proposals for solution this issue?

Thank you

Hi Dmitry,

How could I contact you through private message. I dont want to send you the data from wireshark through public comunication?

Miro

Hello Dmitry,

Do you have some news?

Hi Dmitry,

yes the problem is only on iOS.

The error with codecs was reported by intercom.

We used the same client, but on windows we don't have a problem with the comunication.

It is possible to use the old SIP module in Iridium Pro until you will find out the solution?

And the comunication from intrcom to iOS client not working, but the comunication from iOSclient to intercom is working.

And the comunication from intrcom to iOS client not working, but the comunication from iOSclient to intercom is working.

Hi Dmitry,

yes the problem is only on iOS.

The error with codecs was reported by intercom.

We used the same client, but on windows we don't have a problem with the comunication.

It is possible to use the old SIP module in Iridium Pro until you will find out the solution?

Hi Oksana,

I agreed with Theo. It has to be a basic feature of KNX import. Now we have to import and manualy edit commands and feedbacks for more than 1500 datapoints :(

Also filtering or sorting by group addresses would be nice option.

Best Regards

Miro