Hi,
Hoping I can get a Cisco god out there that can assist with the NAT rules for the One-X Mobile application on a Cisco 881 router.
I am not in the slightest bit Cisco savvy so I've been playing around and reading every bit of documentation that I can on Cisco and after the resulting headaches, I've gotten close to having it working with the following rule:
ip nat inside source static udp x.x.x.x 49152 interface Dialer0 49152
And repeat this static rule over and over for all my RTP ports (limited the IP Office to only 256 ports).
This works without fault for a remote H.323 phone and outgoing calls from the One-X Mobile app on my iPhone, but when I answer a call on the app, it's hit and miss as to whether I get a speech path or not. What I've noticed in the instances that I don't get a speech path, the RTP streams in Monitor, show the calls source port as 49152, but the destination port as 5000 or 5002 or 5004, counting up to the next even ports as test calls are made. Yet, I do a "show ip nat translations" and I can see the router has actually mapped 49152 internally to a random high port eg. 50452, hence why I believe I don't get speech. In the instances where I do get a speech path the destination port was successfully mapped as the 50452 in the Avaya and firewall and it works.
The questions are then...
1. Is the way I've configured the NAT correct?
2. Is this actually a problem in the Cisco or could it be on the Avaya side of things?
3. What have not done or done wrong that could cause this?
Really appreciate any help, been doing my head in for a while on this now.
Thanks,
Tristan
Hoping I can get a Cisco god out there that can assist with the NAT rules for the One-X Mobile application on a Cisco 881 router.
I am not in the slightest bit Cisco savvy so I've been playing around and reading every bit of documentation that I can on Cisco and after the resulting headaches, I've gotten close to having it working with the following rule:
ip nat inside source static udp x.x.x.x 49152 interface Dialer0 49152
And repeat this static rule over and over for all my RTP ports (limited the IP Office to only 256 ports).
This works without fault for a remote H.323 phone and outgoing calls from the One-X Mobile app on my iPhone, but when I answer a call on the app, it's hit and miss as to whether I get a speech path or not. What I've noticed in the instances that I don't get a speech path, the RTP streams in Monitor, show the calls source port as 49152, but the destination port as 5000 or 5002 or 5004, counting up to the next even ports as test calls are made. Yet, I do a "show ip nat translations" and I can see the router has actually mapped 49152 internally to a random high port eg. 50452, hence why I believe I don't get speech. In the instances where I do get a speech path the destination port was successfully mapped as the 50452 in the Avaya and firewall and it works.
The questions are then...
1. Is the way I've configured the NAT correct?
2. Is this actually a problem in the Cisco or could it be on the Avaya side of things?
3. What have not done or done wrong that could cause this?
Really appreciate any help, been doing my head in for a while on this now.
Thanks,
Tristan