如何实现DS34S132与其它TDMoP器件的互操作
加入技术交流群
图2. UDP/IPv4报头。
表2. IPv4报头结构
| Field | Description |
| IPVER | IP version number; IPv4 IPVER = 4 |
| IHL | Length in 32-bit words of the IP Header, IHL = 5 |
| IP TOS | IP type of service |
| Total length | Length in octets of IP Header and data |
| Identification | IP fragmentation identification |
| Flags | IP control flags; must be set to 010 to avoid fragmentation |
| Fragment offset | Indicates where in the datagram the fragment belongs; not used for TDMoP |
| Time to live | IP time-to-live field; datagrams with zero in this field are discarded |
| Protocol | Must be set to 0x11 to signify UDP |
| IP Header checksum | Checksum for the IP Header |
| Source IP address | IP address of the source |
| Destination IP address | IP address of the destination |
表3. UDP报头结构
| Field | Description |
| Source port number, destination port number | Either the source or the destination port number holds the bundle identifier. The unused field can be set to 0x85E (2142), which is the user's port number assigned to TDMoP by the Internet Assigned Numbers Authority (IANA). For UDP/IP-specific OAM packets, the bundle identifier is all 1s. |
| UDP length | Length in octets of UDP Header and data |
| UDP checksum | Checksum of UDP/IP Header and data. If not computed, it must be set to zero. |
根据IANA规定，UDP报头的目标端口应设定为0x85E (2142)，这是分配给TDMoP的用户端口号。Maxim TDMoP器件默认遵循该规范。
部分TDMoP厂商在UDP报中的目标端口号位置分配一个绑定标识号，而不是在源端口号位置。有些厂商还分配一个随机号作为用户端口号，而不是采用IANA分配的0x85E。使用DS34S132时，用户可采用两种方式解决这些问题。
- 在预配置菜单中，将全部绑定标识号赋予相应的位置。
- 向绑定引擎表明绑定标识号在接收数据包中的位置。
- RTP报头互操作性
RTP报头
Field Description V RTP version; must be set to 2. P Padding bit; must be set to 0. X 
相关推荐
-
-
soothmusic | 2012-05-06
-
-
star800 | 2007-09-29
技术专区
评论