Mossman, Paul (CAR:9D30) wrote: > Bob wrote: >> There is another dimension to the problem which goes beyond >> the inefficient use of resources. Basically, when a MOH >> session is left dangling, the phone that was involved in that >> MOH continues to be hammered with RTP packets. If that phone >> takes part in a new call before the dangling MOH is cleaned >> up then that phone will be subjected to two RTP streams (the >> dangling MOH stream and the legitimate one from the far-end) >> and in the case of Polycom, because of the way it re-uses the >> same RTP port across media sessions, it will receive two >> different RTP streams on its media port which will confuse it >> and will result in silence being played out. > > Ah yes, that is quite severe. > > Also, sipXpark continues to send OPTIONS on this dialog, I suppose > because the Polycom did not terminae it. The Polycom is happily > returning OK, and so it would seem that the dangling dialog is not > actually being cleaned up after all. >
Looks like the polycom phones wrongly treat in-dialog OPTIONS the same way as out-of-dialog OPTIONS. So, in this case, the 'keep alive' mechanism will not be able to clean up the dangling MOH session, and as Bob said, you will have a stray RTP session (for 24 hours before it is torn down). Arjun _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
