search

opend-connect / openD

The openD framework for DECT ULE
https://stackforce.github.io/opend-doc/index.html
Apache License 2.0
33 stars 13 forks source link

Basic call example (legacy DECT) - second call setup from FP fails #46

Closed barelsky closed 5 years ago

barelsky commented 5 years ago

When setting up a successfull call, either iniated by FP or PP, releasing it from either FP or PP everything works fine. Hwoever after a release of the first (or next) successfull caal a next setup intitaed from FP (so by "r 1") fails. This has been tested on release 1.0.4, Dialog HW. Basic call example.

p-weber commented 5 years ago

I tested it on our site. I could not find any problem here. I can release a call and setup the call from FP to the same PP again without any problems. What do you mean by "or next" successful call? A second call from the PP? So, the problem occurs only at a second call from the FP? br Patrick

barelsky commented 5 years ago

Yes the problem occurs after one or more successfull call setup and releases (PP controlled) and then start a next call from FP by "r 1". It looks like the call is setup correctly see logging below: image ..but after this it is uncontrollable

p-weber commented 5 years ago

I can confirm this can be reproduced at our side with the exact call order below. Call setup PP -> FP, call release PP -> FP, call setup FP -> PP (error) I guess, by the combination of two examples from Dialog we use here two different variables of "ConEi". It's fixed by 0e80ce5