Hi
One-X drives me crazy. We have one installation with IP500v2, AppServer and the preferred mobile client. This is for 9.1
All is fine, except the VoIP mode for the mobile. If the mobile is connected via WLAN at the customers LAN side, VoIP registers to the external public IP address. The result is all is green, call is setup, but no audio.
I did a second installation in the lab, same story but different. It works in the internals WLAN but doesn't if connected from outside. I can see the SIP registration in SSA is shown with the LAN address of the firewall. But no issue internally. Here it is a UCM and not the AppServer, but still the same Linux thing.
In both cases i have a split dans with the external FQDN of ipo.customer.com and 1xp.customer.com pointing to the public WAN IP. Internally they point to the IPO and the Portal server. The domain name in LAN1/VoIP is set to ipo.customer.com and the public IP in LAN1/STUN is the external address. In Application server, the Domain name is portal.customer.com and in Portal XMPP is portal.customer.com. Ports for 5060 and NTP range are forwarded to IPO while 5222,8444 and 5269 are forwarded to the portal.
The mobile clients are setup to register to portal.customer.com
What I don't understand is the magic how the mobile client gets the information for VoIP registration. Which IP and Ports. If it just the FQDN this is resolved into the proper IP, then it would just work. And how is the Client/Portal knowing if the internal or the NAT RTP range shall be used?
Maybe most helpful: How to trace this?
As I said, I have just two installations behaving odd, but in the opposite way. Although I'm sure they are setup the same way!
Nay help is welcome.
One-X drives me crazy. We have one installation with IP500v2, AppServer and the preferred mobile client. This is for 9.1
All is fine, except the VoIP mode for the mobile. If the mobile is connected via WLAN at the customers LAN side, VoIP registers to the external public IP address. The result is all is green, call is setup, but no audio.
I did a second installation in the lab, same story but different. It works in the internals WLAN but doesn't if connected from outside. I can see the SIP registration in SSA is shown with the LAN address of the firewall. But no issue internally. Here it is a UCM and not the AppServer, but still the same Linux thing.
In both cases i have a split dans with the external FQDN of ipo.customer.com and 1xp.customer.com pointing to the public WAN IP. Internally they point to the IPO and the Portal server. The domain name in LAN1/VoIP is set to ipo.customer.com and the public IP in LAN1/STUN is the external address. In Application server, the Domain name is portal.customer.com and in Portal XMPP is portal.customer.com. Ports for 5060 and NTP range are forwarded to IPO while 5222,8444 and 5269 are forwarded to the portal.
The mobile clients are setup to register to portal.customer.com
What I don't understand is the magic how the mobile client gets the information for VoIP registration. Which IP and Ports. If it just the FQDN this is resolved into the proper IP, then it would just work. And how is the Client/Portal knowing if the internal or the NAT RTP range shall be used?
Maybe most helpful: How to trace this?
As I said, I have just two installations behaving odd, but in the opposite way. Although I'm sure they are setup the same way!
Nay help is welcome.