Hello,
o Juha Heinanen on 02/29/2012 04:44 AM:
i started a new thread on 491 Request Pending issue. i made mode tests
in configuration:
ua (192.98.102.10:5074) - proxy (192.98.102.10:5060 and 5080) -
sems sbc (192.98.102.10:5090) - sems echo server (192.98.102.13:5090).
it turned out that it is sems sbc that replies with 491 when sems echo
server sends sems sbc an in-dialog invite (session timer refresh).
can you please send me a full log of that call (from the beginning)
from sems sbc?
I'm trying to understand what INVITE transaction is pending in sems sbc.
immediate after 491, sems sbc sends sems echo server a bye, but ua - sems
I'll fix that one in a minute.
Stefan
sbc leg is not terminated.
any idea why 491 and bye are sent and why ua - sems sbc leg is not
terminated?
pcap file is enclosed.
-- juha
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
--
Stefan Sayer
CEO (Geschäftsführer)
FRAFOS GmbH
email: [email protected]
mobile:+49 162 1366449
www.frafos.com
Prinzessinnenstr. 19/20 betahaus
10969 Berlin
Germany
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
