Using logic similar to the Onsip.org config file i'm doing call forward no-answer using a TM timer, when the call is forwarded OSER sends a cancel to the original client which responds with a "200 OK". OSER doesn't seem to process this 200 ok, generating an error and resending the CANCEL message.
Running OSER in debug level 5 shows that OSER was not able to match the "200 OK" to the CANCEL message
Below is a trace of exchange, the following error is recorded in the debug log -- get_hdr_field: cseq <CSeq>: <102> <CANCEL> header field type 5, name=<CSeq>, body=<102 CANCEL> DEBUG: t_reply_matching: hash 44785 label 1883536846 branch 0 DEBUG: t_reply_matching: no matching transaction exists DEBUG: t_reply_matching: failure to match a transaction DEBUG: t_check: msg id=3 global id=3 T end=(nil) .... ERROR: forward_reply: no 2nd via found in reply --
# U OSER_PROXY:15061 -> SIP_UAC:5060 CANCEL sip:200110005333@192.168.99.240:5060 SIP/2.0. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. Call-ID: c818cfaf-edd9443f@192.168.99.66. To: sip:200110005333@OSER_PROXY:15061. CSeq: 102 CANCEL. Content-Length: 0. .
# U SIP_UAC:5060 -> OSER_PROXY:15061 SIP/2.0 200 OK. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. To: sip:200110005333@OSER_PROXY:15061;tag=00055e7cd6f33c1a551406a2-75f29afe. Call-ID: c818cfaf-edd9443f@192.168.99.66. CSeq: 102 CANCEL. Server: Cisco-CP7960G/7.5. Content-Length: 0. .
Maybe this is also introduced by the CSeq optimations? (Just a guess)
klaus
Tavis P wrote:
Using logic similar to the Onsip.org config file i'm doing call forward no-answer using a TM timer, when the call is forwarded OSER sends a cancel to the original client which responds with a "200 OK". OSER doesn't seem to process this 200 ok, generating an error and resending the CANCEL message.
Running OSER in debug level 5 shows that OSER was not able to match the "200 OK" to the CANCEL message
Below is a trace of exchange, the following error is recorded in the debug log -- get_hdr_field: cseq <CSeq>: <102> <CANCEL> header field type 5, name=<CSeq>, body=<102 CANCEL> DEBUG: t_reply_matching: hash 44785 label 1883536846 branch 0 DEBUG: t_reply_matching: no matching transaction exists DEBUG: t_reply_matching: failure to match a transaction DEBUG: t_check: msg id=3 global id=3 T end=(nil) .... ERROR: forward_reply: no 2nd via found in reply --
# U OSER_PROXY:15061 -> SIP_UAC:5060 CANCEL sip:200110005333@192.168.99.240:5060 SIP/2.0. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. Call-ID: c818cfaf-edd9443f@192.168.99.66. To: sip:200110005333@OSER_PROXY:15061. CSeq: 102 CANCEL. Content-Length: 0. .
# U SIP_UAC:5060 -> OSER_PROXY:15061 SIP/2.0 200 OK. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. To: sip:200110005333@OSER_PROXY:15061;tag=00055e7cd6f33c1a551406a2-75f29afe. Call-ID: c818cfaf-edd9443f@192.168.99.66. CSeq: 102 CANCEL. Server: Cisco-CP7960G/7.5. Content-Length: 0. .
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Forgot to mention, this is using CVS HEAD checked out on friday
Klaus Darilion wrote:
Maybe this is also introduced by the CSeq optimations? (Just a guess)
klaus
Tavis P wrote:
Using logic similar to the Onsip.org config file i'm doing call forward no-answer using a TM timer, when the call is forwarded OSER sends a cancel to the original client which responds with a "200 OK". OSER doesn't seem to process this 200 ok, generating an error and resending the CANCEL message.
Running OSER in debug level 5 shows that OSER was not able to match the "200 OK" to the CANCEL message
Below is a trace of exchange, the following error is recorded in the debug log -- get_hdr_field: cseq <CSeq>: <102> <CANCEL> header field type 5, name=<CSeq>, body=<102 CANCEL> DEBUG: t_reply_matching: hash 44785 label 1883536846 branch 0 DEBUG: t_reply_matching: no matching transaction exists DEBUG: t_reply_matching: failure to match a transaction DEBUG: t_check: msg id=3 global id=3 T end=(nil) .... ERROR: forward_reply: no 2nd via found in reply --
# U OSER_PROXY:15061 -> SIP_UAC:5060 CANCEL sip:200110005333@192.168.99.240:5060 SIP/2.0. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. Call-ID: c818cfaf-edd9443f@192.168.99.66. To: sip:200110005333@OSER_PROXY:15061. CSeq: 102 CANCEL. Content-Length: 0. .
# U SIP_UAC:5060 -> OSER_PROXY:15061 SIP/2.0 200 OK. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. To: sip:200110005333@OSER_PROXY:15061;tag=00055e7cd6f33c1a551406a2-75f29afe.
Call-ID: c818cfaf-edd9443f@192.168.99.66. CSeq: 102 CANCEL. Server: Cisco-CP7960G/7.5. Content-Length: 0. .
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi there,
it might be a problem - I will take a fast look !!
regards, bogdan
Tavis P wrote:
Forgot to mention, this is using CVS HEAD checked out on friday
Klaus Darilion wrote:
Maybe this is also introduced by the CSeq optimations? (Just a guess)
klaus
Tavis P wrote:
Using logic similar to the Onsip.org config file i'm doing call forward no-answer using a TM timer, when the call is forwarded OSER sends a cancel to the original client which responds with a "200 OK". OSER doesn't seem to process this 200 ok, generating an error and resending the CANCEL message.
Running OSER in debug level 5 shows that OSER was not able to match the "200 OK" to the CANCEL message
Below is a trace of exchange, the following error is recorded in the debug log -- get_hdr_field: cseq <CSeq>: <102> <CANCEL> header field type 5, name=<CSeq>, body=<102 CANCEL> DEBUG: t_reply_matching: hash 44785 label 1883536846 branch 0 DEBUG: t_reply_matching: no matching transaction exists DEBUG: t_reply_matching: failure to match a transaction DEBUG: t_check: msg id=3 global id=3 T end=(nil) .... ERROR: forward_reply: no 2nd via found in reply --
# U OSER_PROXY:15061 -> SIP_UAC:5060 CANCEL sip:200110005333@192.168.99.240:5060 SIP/2.0. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. Call-ID: c818cfaf-edd9443f@192.168.99.66. To: sip:200110005333@OSER_PROXY:15061. CSeq: 102 CANCEL. Content-Length: 0. .
# U SIP_UAC:5060 -> OSER_PROXY:15061 SIP/2.0 200 OK. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. To: sip:200110005333@OSER_PROXY:15061;tag=00055e7cd6f33c1a551406a2-75f29afe.
Call-ID: c818cfaf-edd9443f@192.168.99.66. CSeq: 102 CANCEL. Server: Cisco-CP7960G/7.5. Content-Length: 0. .
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi again,
indeed, there was a problem - old story with priority of operations - shame on me :(. Extra round brackets fixed the problem - the fix is on CVS.
Thanks for the report, Bogdan
PS:let me know if it works properly
Bogdan-Andrei Iancu wrote:
Hi there,
it might be a problem - I will take a fast look !!
regards, bogdan
Tavis P wrote:
Forgot to mention, this is using CVS HEAD checked out on friday
Klaus Darilion wrote:
Maybe this is also introduced by the CSeq optimations? (Just a guess)
klaus
Tavis P wrote:
Using logic similar to the Onsip.org config file i'm doing call forward no-answer using a TM timer, when the call is forwarded OSER sends a cancel to the original client which responds with a "200 OK". OSER doesn't seem to process this 200 ok, generating an error and resending the CANCEL message.
Running OSER in debug level 5 shows that OSER was not able to match the "200 OK" to the CANCEL message
Below is a trace of exchange, the following error is recorded in the debug log -- get_hdr_field: cseq <CSeq>: <102> <CANCEL> header field type 5, name=<CSeq>, body=<102 CANCEL> DEBUG: t_reply_matching: hash 44785 label 1883536846 branch 0 DEBUG: t_reply_matching: no matching transaction exists DEBUG: t_reply_matching: failure to match a transaction DEBUG: t_check: msg id=3 global id=3 T end=(nil) .... ERROR: forward_reply: no 2nd via found in reply --
# U OSER_PROXY:15061 -> SIP_UAC:5060 CANCEL sip:200110005333@192.168.99.240:5060 SIP/2.0. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. Call-ID: c818cfaf-edd9443f@192.168.99.66. To: sip:200110005333@OSER_PROXY:15061. CSeq: 102 CANCEL. Content-Length: 0. .
# U SIP_UAC:5060 -> OSER_PROXY:15061 SIP/2.0 200 OK. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. To: sip:200110005333@OSER_PROXY:15061;tag=00055e7cd6f33c1a551406a2-75f29afe.
Call-ID: c818cfaf-edd9443f@192.168.99.66. CSeq: 102 CANCEL. Server: Cisco-CP7960G/7.5. Content-Length: 0. .
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Looks good
I've not been able to reproduce the issue since the update
Thank you!
tavis
Bogdan-Andrei Iancu wrote:
Hi again,
indeed, there was a problem - old story with priority of operations - shame on me :(. Extra round brackets fixed the problem - the fix is on CVS.
Thanks for the report, Bogdan
PS:let me know if it works properly
Bogdan-Andrei Iancu wrote:
Hi there,
it might be a problem - I will take a fast look !!
regards, bogdan
Tavis P wrote:
Forgot to mention, this is using CVS HEAD checked out on friday
Klaus Darilion wrote:
Maybe this is also introduced by the CSeq optimations? (Just a guess)
klaus
Tavis P wrote:
Using logic similar to the Onsip.org config file i'm doing call forward no-answer using a TM timer, when the call is forwarded OSER sends a cancel to the original client which responds with a "200 OK". OSER doesn't seem to process this 200 ok, generating an error and resending the CANCEL message.
Running OSER in debug level 5 shows that OSER was not able to match the "200 OK" to the CANCEL message
Below is a trace of exchange, the following error is recorded in the debug log -- get_hdr_field: cseq <CSeq>: <102> <CANCEL> header field type 5, name=<CSeq>, body=<102 CANCEL> DEBUG: t_reply_matching: hash 44785 label 1883536846 branch 0 DEBUG: t_reply_matching: no matching transaction exists DEBUG: t_reply_matching: failure to match a transaction DEBUG: t_check: msg id=3 global id=3 T end=(nil) .... ERROR: forward_reply: no 2nd via found in reply --
# U OSER_PROXY:15061 -> SIP_UAC:5060 CANCEL sip:200110005333@192.168.99.240:5060 SIP/2.0. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. Call-ID: c818cfaf-edd9443f@192.168.99.66. To: sip:200110005333@OSER_PROXY:15061. CSeq: 102 CANCEL. Content-Length: 0. .
# U SIP_UAC:5060 -> OSER_PROXY:15061 SIP/2.0 200 OK. Via: SIP/2.0/UDP OSER_PROXY:15061;branch=z9hG4bKb3b2.9e597b73.0. From: tavis sip:200110005334@OSER_PROXY:15061;tag=d478d8ef4036cbffo0. To: sip:200110005333@OSER_PROXY:15061;tag=00055e7cd6f33c1a551406a2-75f29afe.
Call-ID: c818cfaf-edd9443f@192.168.99.66. CSeq: 102 CANCEL. Server: Cisco-CP7960G/7.5. Content-Length: 0. .
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Klaus Darilion -
Tavis P