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). immediate after 491, sems sbc sends sems echo server a bye, but ua - sems 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
491.pcap
Description: 491 pcap
_______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
