I have been looking into http://track.sipfoundry.org/browse/XTRN-931 and it looks like the problem is related to the m-line in SDP generated by sipXpage.
When sipXpage answers a call it generates SDP with the following m-line: m=audio 8502/2 RTP/AVP 0 According to section 5.14 of rfc4566 (http://tools.ietf.org/html/rfc4566#section-5.14) <port>/<number of ports> format is used for: "... applications where hierarchically encoded streams are being sent to a unicast address, it may be necessary to specify multiple transport ports..." What is the rational for using this format in sipXpage? What is a specific use of this format by the caller or paged sets? Thank you in advance, Mark. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
