Hi,
I got the following scenario which can be reproduced (sems 1.6 / master):
A --> SBC --> proxy --> B
A is hanging up up while the call is ringing, the CANCEL from the caller
and the 200OK from the callee "cross the line" but the CANCEL from A
arrives at SEMS and is replied correctly (487 terminated) the 200OK
(coming from B) is sent from the proxy to SEMS/SBC but is not forwared
by SEMS.
According to the information i found regarding the CANCEL/200OK race
condition the 200OK is supposed to be forwarded to the callee A. But
Sems is not forwarding the 200OK at all... ?
https://tools.ietf.org/html/rfc5407#page-13
Call-flow (Made by "homer") is attached, the 487 is missing in the
call-flow graph but i can see it in e.g. ngrep traces (this is probably
related to something else/"homer"...) sbc1 is the external interface/IP
and sbc1(internal) the internal IP/network. It seems to work with
Kamailio/Opensips (200OK is correctly forwarded to the caller who hangs
up) but not if SEMS is in the mix...
Any ideas/hints or remarks?
Best Regards
--
Max Mühlbronner
42com Telecommunication GmbH
Straße der Pariser Kommune 12-16
10243 Berlin
E-Mail: [email protected]
Web: www.42com.com
Firmenangaben/Company information:
Handelsregister/Commercial register: Amtsgericht Berlin HRB 99071 B
Umsatzsteuer-ID/VAT-ID: DE223812306
Geschäftsführer/CEO: Thomas Reinig, Alexander Reinig
Diese E-Mail enthält Informationen von 42com Telecommunication GmbH. Diese sind
möglicherweise vertraulich und ausschließlich für den Adressaten bestimmt.
Sollten Sie diese elektronische Nachricht irrtümlicherweise erhalten haben, so
informieren Sie uns bitte unverzüglich telefonisch oder per E-Mail.
This message is intended only for the use of the individual or entity to which
it is addressed.
If you have received this message by mistake, please notify us immediately.
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
