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
CSeq issues with CANCEL after INVITE #918
Comments
Can you paste here the parameters you set for tm module? |
I have default settings from for tm:
-Gregg |
Can you test with laster master branch? |
After installing from package, it works better but there are some issues still: U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 |
A new patch was pushed. Try again with latest master branch. |
Now the CSeq is correct, however I do see repeated CANCELs and 487s from the peer just as in #870 This means that it does cancel the call and these extra messages back and forth do not cause any end-user side effects: U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 U x.x.x.50:5060 -> 85.14.79.130:6050 U 85.14.79.130:6050 -> x.x.x.50:5060 |
Would it be because the operator sends 487 before 200 (shouldn't it be 200 OK for CANCEL first then 487 as last message). #870 seems to have similar call flow. |
Attach also thekamailio log messages from syslog file with debug=3 in kamailio.cfg. |
I may have a lead to troubleshoot this further. Hopefully I will get the time for it later today, if not, tomorrow. |
I pushed another patch in master. Can you try again with latest version? |
Works for me now! Thanks guys, you are the best ;) |
OK, I am closing this item. Thanks for troubleshooting assistance and testing. |
Hi,
I have a provider that requires proxy auth for all outgoing calls so I create the following config:
Based on this authentication happens correctly however when canceling the call from the caller side, incorrect CSeq value is sent to the PSTN trunk:
Since I'm new to Kamailio, I figured I must be doing something wrong but don't seem to find any working example anywhere....
-G
The text was updated successfully, but these errors were encountered: