8 | | > |
9 | | > It appears that the bound_addr is converted twice from host byte order |
10 | | > to network byte order: |
11 | | > |
12 | | > The first conversion is in create_rtp_rtcp_sock calling via |
13 | | > pj_sockaddr_in_set_str_addr (calling pj_inet_addr etc.) |
14 | | > |
15 | | > The second conversion is in create_rtp_rtcp_sock calling pj_sock_bind_in |
16 | | > (calling pj_htonl). |
| 7 | >[[BR]] |
| 8 | >[[BR]] |
| 9 | > It appears that the bound_addr is converted twice from host byte order to network byte order: |
| 10 | >[[BR]] |
| 11 | >[[BR]] |
| 12 | > The first conversion is in create_rtp_rtcp_sock calling via pj_sockaddr_in_set_str_addr (calling pj_inet_addr etc.) The second conversion is in create_rtp_rtcp_sock calling pj_sock_bind_in (calling pj_htonl). |