Inconsistency in fabric state change event

[pallab-gain]

It seems there is inconsistency on how the library is pushing "OnIceGatheringChange", or febric state change events to server.

Use case -

1. Start web demo app with a room ( example "test-4" )
2. Start csio android demo app with room "test-4"
3. Both are connect, and a webrtc session has established.

Expected -

I should see data is pushing to server in "fabric/statechange" endpoint for mentioned ICE states.

• Gathering
• Checking
• Complete
• Connected
• Closed

and, other states mentioned here Fabric state change event.

But, I can only see Closed state is pushing, and something Connected state is pushing. Although, library is consuming all those events. Can you please check, and verify whether other states are pushing to endpoint or not ?

My android session logcat for reference ( I append extra "reportEvent" for debugging purpose. In your text editor, you can filter using "reportEvent", or "CsioRTCLibrary", or "CsioRTC" )

[zoonooz]

Hi @pallab-gain thank you for the details you provided. I have checked that and most of the events are skipped due to connectionID is not available at that time.

If you look at EventManager.kt line 44-53, in order to process the events, connectionID is needed and it is the combination of hash of IP + port of source and destination. Those info will be available only when the connection has been established (fabric setup)

[zoonooz]

This is the log of the skipped events

09-26 15:54:26.897 14819-14850/io.callstats.demo I/EventManagerImpl: Skip sending event : OnSignalingChange(state=HAVE_REMOTE_OFFER)
09-26 15:54:26.898 14819-14850/io.callstats.demo I/EventManagerImpl: Skip sending event : io.callstats.OnAddStream@2f5dd6b
09-26 15:54:27.266 14819-14850/io.callstats.demo I/EventManagerImpl: Skip sending event : OnSignalingChange(state=STABLE)
09-26 15:54:27.287 14819-14850/io.callstats.demo I/EventManagerImpl: Skip sending event : OnIceGatheringChange(state=GATHERING)
09-26 15:54:27.512 14819-14850/io.callstats.demo I/EventManagerImpl: Skip sending event : OnIceConnectionChange(state=CHECKING)
09-26 15:54:27.524 14819-14850/io.callstats.demo I/EventManagerImpl: Skip sending event : OnIceGatheringChange(state=COMPLETE)

Any idea how could I send these without connectionID @karthikbr82

[karthikbr82]

This can be done two ways,

1. the events can be cached and sent once you have the connectionID
2. Change the logic of generating connectionID, it can be some random number and some how you have to associate it with peer connection.

[zoonooz]

@karthikbr82

1. it might works, but if peer connection failed and have to redo gathering + checking again, those event might be sent using old connectionID
2. This can be hard to associate as we still using the same peer connection object but connection inside can be changed.

how about using 2. but instead of finding the way to associate wth peer connection object which ip+port inside can be changed over time, we create random number and use it as connectionID until ice connection change to failed then recreate?

[karthikbr82]

No we cannot have two different connection IDs it messes up our dashboard visualisation and aggregations.

[zoonooz]

Then I think I misunderstood the concept of your connectionID 🤦
Are you saying one peer connection one connection ID ?

If yes then I think the docs is a bit misleading.

FYI : Currently I am using connected ice candidate pair to generate connectionID

[zoonooz]

Now those events should be sent by the lib.

Apart from connectionID documentation example, please note that in the REST document integration step 2 mentions that "Any message can be sent from this point onwards" after Fabric setup message is sent which also made me misunderstood and block those events.