-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scenario Pauses Considered Detrimental #26
Comments
Part of the problem here is that the pauses break when you are expecting to receive a BYE. If you are expecting to send a BYE then it's critical to retain the pauses. |
benlangfeld
referenced
this issue
in vindir/adhearsion-versus
Dec 19, 2013
This depends on #53. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently when sippy_cup is building a UAC scenario where the server side submits the BYE it inserts pauses into the compiled scenario to match the rtp pauses created. This is actually detrimental to runtime execution of the sipp scenario because at load variations in timing can cause the scenario to be in the middle of a forced pause when the BYE is received. Since we are simply waiting for a BYE as far as the SIP flow is concerned, this isn't the ideal behavior of sippy_cup.
At a glance, I'd assume we may want to either automatically strip the pauses generated for RTP actions in UAC scenarios during this time or even better make them switchable in case the desired behavior really is to force the pause.
Thoughts?
The text was updated successfully, but these errors were encountered: