Nearly sorted now... one more problem to fix.
At a remote site, I've got a T48G and an X-Lite softphone. Both are registering correctly and placing calls (and autoprovisioning, in the case of the Yealink). However only the X-Lite is getting audio through. I assume that it is a NAT issue, but I'm not sure whether I'm dealing with a NAT/RTP problem or incorrect configuration of the SIP/registration, or possibly something else entirely.
Looking at the configurations, both endpoints are set up to use rport, no NAT traversal, no proxy. Both are setting up calls with the G722 codec. Per the attached registrations page, the Yealink is registering with a 'LAN IP', which is its private LAN address... possibly indicating incorrect registration?
Looking through the call logs side by side, there are a couple of notable differences in the SIP packets that I can see:
Format of the Call-ID:
- Yealink: 0_2873399369@192.168.11.107
- X-Lite: 92361MTZkOThiMDQyNWM2YTc0NWUyMjgyNjQ3YjJiYzBmMmM
Format of the Contact:
- Yealink: <sip:{USER}@192.168.11.107:5060>
- X-Lite: <sip:{USER}@{REMOTE WAN IP}:27334;rinstance=d3a86907b0508f94>
Other than that, the order of the information in the SIP packets is different, but the fields are mirrored. Any suggestions what I'm up against or where to look?
Thanks again!
At a remote site, I've got a T48G and an X-Lite softphone. Both are registering correctly and placing calls (and autoprovisioning, in the case of the Yealink). However only the X-Lite is getting audio through. I assume that it is a NAT issue, but I'm not sure whether I'm dealing with a NAT/RTP problem or incorrect configuration of the SIP/registration, or possibly something else entirely.
Looking at the configurations, both endpoints are set up to use rport, no NAT traversal, no proxy. Both are setting up calls with the G722 codec. Per the attached registrations page, the Yealink is registering with a 'LAN IP', which is its private LAN address... possibly indicating incorrect registration?
Looking through the call logs side by side, there are a couple of notable differences in the SIP packets that I can see:
Format of the Call-ID:
- Yealink: 0_2873399369@192.168.11.107
- X-Lite: 92361MTZkOThiMDQyNWM2YTc0NWUyMjgyNjQ3YjJiYzBmMmM
Format of the Contact:
- Yealink: <sip:{USER}@192.168.11.107:5060>
- X-Lite: <sip:{USER}@{REMOTE WAN IP}:27334;rinstance=d3a86907b0508f94>
Other than that, the order of the information in the SIP packets is different, but the fields are mirrored. Any suggestions what I'm up against or where to look?
Thanks again!
