[prev in list] [next in list] [prev in thread] [next in thread]
List: semsdev
Subject: [Semsdev] 491 Request Pending
From: Juha Heinanen <jh () tutpro ! com>
Date: 2012-02-29 4:17:17
Message-ID: 20301.42701.761792.127489 () sip ! test ! fi
[Download RAW message or body]
Juha Heinanen writes:
> any idea why 491 and bye are sent and why ua - sems sbc leg is not
> terminated?
i still don't know answer to the above, but i got a bit further by
aligning minimum session timers in sems sbc and sems echo applications.
now i have in sems sbc:
session_expires=120
minimum_timer=90
and in sems echo server:
session_expires=240
minimum_timer=90
with this config 491 does not occur, but both sems sbc and sems echo
server send session timer re-invites to each other although session
timer negotiation resulted in uas (= sems echo server) doing the
refreshes (packet 19).
when sems sbc then sends re-invite to sems echo server, sems echo server
replies with '421 extension required' perhaps because sems sbc is not
supposed to do the refresh?
pcap file is enclosed.
-- juha
["421.pcap" (application/octet-stream)]
_______________________________________________
Semsdev mailing list
Semsdev@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/semsdev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic