In prior releases, the system transcoded all AMR-to-AMR calls or all AMR-WB-to-AMR-WB calls when the Offer/Answer differed only in the assignment of dynamic payload types, or in the values assigned to certain AMR/AMR-WB parameters. Oracle® Enterprise Session Border Controller connects endpoints that choose AMR with different dynamic payload types but equivalent AMR parameters, payload type remapping can be handled by the local network processor rather than using transcoding resources. This is done to increase the interoperability with devices that do not support mptime. When Oracle® Enterprise Session Border Controller includes an mptime in an outgoing SDP, it will also always add a ptime attribute with the value of the most preferred codec. Invalid: dash cannot be first mptime value m=audio 10000 RTP/AVP 96 0 Valid: 'ptime' attribute is ignored m=audio 10000 RTP/AVP 0 8 If a valid mptime is received in the incoming SDP, its values will be used for packetization times of each corresponding codec and a valid mptime line will be sent in the outgoing SDP. If the Oracle® Enterprise Session Border Controller receives an invalid mptime, it is ignored and removed. The dash character, "-", on an mptime line is used for non-packetized codecs, such as CN or telephone-event. The mptime line uses an integer to indicate the packetization time for each corresponding codec in the m= line. The Oracle® Enterprise Session Border Controller adheres to PKT-SP-NCS1.28 and PKT-SP-EC-MGCP-I06-021127 for processing and generating mptime. When multiple codecs appear on a single m= line, the PacketCable mptime attribute can specify different packetization times for each codec. The ptime attribute is not related to a specific codec but to the entire m= line. The SDP specification lacks the ability to specify unique packetization times per codec when more than one codec is listed in an m= line.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |