You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever CPE will try to connect to talaria, it will be sending the metadata parameters in convey headers and talaria will decode the convey header and persist it in memory. now the problem is there in parodus or talaria because parodus will be sending the key and talaria is expecting another key.
Here is a detailed view of the problem
Here parodus will be building convey header. with these all keys.
Hello Team,
Whenever CPE will try to connect to talaria, it will be sending the metadata parameters in convey headers and talaria will decode the convey header and persist it in memory. now the problem is there in parodus or talaria because parodus will be sending the key and talaria is expecting another key.
Here is a detailed view of the problem
Here parodus will be building convey header. with these all keys.
and in talaria we are expecting a few other fields.
now there is a mismatch between the fields. we need to fix it either in parodus or in talaria.
cc: @schmidtw
The text was updated successfully, but these errors were encountered: