Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No Talk Path for iPhone One-X Mobile on Public Connection

Status
Not open for further replies.

GoApex

Vendor
Jun 25, 2003
22
US
I've been banging on this for several days now. I've installed the iPhone APP, it works great in the WLAN but as soon as I go LTE I lose talk path both ways. I verified the Split DNS and the phone does register, I can call out, receive calls in but no luck on the audio. I'm going through a Cisco ASA 5505 running IOS 8.4 and ASDM 7.1 to one public IP address. The ports are open because the iPhone registers with the IPO but I feel the RTP settings may not be correct. I've created a Security Policy Rule for RTP ports 49152-53246 (I've read where I'll get hacked but I want to see it work once and I'll modify them). I've gone through the manual and everything else appears to be working correctly. On the LTE side when the phone is registered I can play voicemail messages left with no issues and IM other users. I know they're functions of the OneX and the VMPro so I'm still looking for the trouble either in the Cisco or the IPO. I'm open to suggestions before I break out the sledgehammer and turn back on my NorStar.
 
Don't use ports 49152-53246 go higher than 53246 also make sure SIP ALG or SIP inspect is off, search here on how to turn it off. Make sure STUN works.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
OK, I bumped the RTP range to 54000 to 55000, Sip inspection is off and I ran the STUN check and it came back and auto populated the UDP port. Still no luck.....
 
Did you change the remote ports and did you forward them?
Split DNS is used internally, port forwarding is used for externally.
So if it work internally then you need to look in to the external part.


BAZINGA!

I'm not insane, my mother had me tested!

 
Still no luck, I'll try reconfiguring it directly to the Internet utilizing the WAN port to bypass any port forwarding. I'm sure the issue is in the Cisco ASA Firewall. I just can't seem to get through it.
 
Be very careful, a group of hackers from the gaza strip (yes, we know who you are) will be on it like flys around sh1t once it's on the internet directly :)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top