The forum Type & Typography seems appropriate to discuss OpenType font design issues.
When asking there, better make sure to show the same characters in your left and right images, so the rendering problem stands out. (Or possibly the vast differences in your current images exactly describe your problem.)
If Microsoft's Kalinga works correctly in InDesign (note to others: it doesn't come anymore with Windows 10, you need Windows 8 or older) then there are no hidden features involved. A quick glance at its feature code shows it contains a set of common Indi-related features: Above-Base, Akhands, Below-Base, Halant, Nukta, Post-base and Reph, all gathered under a single 'ory2' language tag. But, as I cannot spot the differences in your two images, I can't suggest which, if any, feature is misbehaving in InDesign.
Ah - Afterthought Alter.
InDesign does not enable many of the more advanced OpenType features by default. You may want to make sure the behavior you describe still persists with the World-Ready Composer, which handles "support for “complex script" languages, such as Arabic and Hebrew" (and many others).
Thank you for your reply.
Formation of conjuncts in our fonts are correct with Winword as show in the image (Winword section). With same font these conjuncts are not formed as shown in InDesign section of image.
We have added all available tables (Above-Base, Akhands, Below-Base, Halant, Nukta, Post-base and Reph) in our font, but that does not work as expected.
Moreover, if we do not add any tables in the font, there are some glyphs replacement that are already available.
N + nukta = ଡ+଼ =ଡ଼
Ch + nukta is not available which is also not available in Kalinga.
(Conjuncts not form when ତ, ନ, ବ, ଭ, ମ, ଯ, ୟ, ର, ଲ, ଳ at second position characters)
This glyph replacement should not happen without any rule in the font table. That’s why we suspect there are some additions done in the rendering engine specific to Kalinga font.