• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1799
  • Last Modified:

NO AUDIO ON VOICEFLEX SIP TRUNK WITH ALCATEL OMNI PCX (WATCHGUARD X750e)

Hello all - I have an annoying problem with SIP calls. the call goes through but no audio in both directions. Apparently you cant add a stun setting on the omni PCX? Apparently the PABX is passing the local 192.168.1.x address to the SIP provider, however noone seems to know a resolution! Will give 500 points as rtearing my hair out now!

Thanks
0
datafocus
Asked:
datafocus
1 Solution
 
Istvan KalmarCommented:
HI,

Please show the netwrork topology...
0
 
dinkon4uCommented:
Place/Enable Session Border Controller in between Provider and your PBX.
I know cisco has device for SBC.
HTH
0
 
dpk_walCommented:
Do you get any deny messages in the System Manager->Traffic monitor when this happens; this would help understand if firewall is blocking any traffic.

Few questions:
1. Is NAT configured for PBX.
2. If yes, then what type, dynamic or 1-1.
3. Which policy is configured on firewall.

If feasible for testing configure ANY policy and 1-1 NAT and check if this helps.

Thank you.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
datafocusAuthor Commented:
Hi,
Yes - tried ANY first - calls come up but no Audio. Tried Dynamic & 1 to 1 NAT...
have set logging but nothing seems to get allowed or denied in traffic manager.
Thanks
0
 
dpk_walCommented:
If possible put PBX outside the firewall and then check the behavior.

Thank you.
0
 
datafocusAuthor Commented:
Hi,
Not really possible. Voiceflex are saying the PABX is advertising its internal IP & this is clearly what the problem is... What I need to know is how to get it to display the external IP.
However, Alcatel doesnt have a STUN setting & Watchguard say this isnt possible?
 
Any one any ideas?
0
 
dpk_walCommented:
Sorry dont think this comment is of much help to you but still putting it:

As you said PABX is on private IP; so it must be using firebox external interface IP by default; if you setup 1-1 NAT then it would advertise the 1-1 NAT public IP.

Am not sure if this is an option; but can you open web browser on PABX and go to http://www.whatismyip.com; this would show the public IP of PABX as seen to everyone. OR may be initiate any session from PABX and do packet capture on external interface of firebox and see what the packets have as the source IP for the specific port/protocol/destination.

Thank you.
0
 
datafocusAuthor Commented:
The SIP Provider states that it is advertising the PRIVATE ip....
Thanks

policy.PNG
advanced.PNG
0
 
datafocusAuthor Commented:
When I change to 1 to 1 NAT it no longer makes or receives calls....
0
 
dpk_walCommented:
Do not configure policy based NAT. Revert to "Use Network NAT Settings".

Current policy only allows outbound traffic from internal host 192.168.1.246 to external host 146.x.x.x.

Assuming you wish to allow all inbound traffic from 146.x.x.x to 217.y.y.202, add 1-1 NAT and add one more ANY service and configure as below:
Enabled and allowed; from 146.x.x.x; to 217.y.y.202

To ensure 1-1 NAT is configured properly, please look at link below:
http://watchguard.custhelp.com/app/answers/detail/a_id/1545/kw/1-1%20NAT/p/214%2C215/sno/1

Finally make sure that 217.y.y.202 IP is not listed under external alias [used for static NAT]:
http://watchguard.custhelp.com/app/answers/detail/a_id/1497/kw/adding%20external%20alias

Thank you.
0
 
datafocusAuthor Commented:
202 is the main IP address - i.e. not an alias. Is this what you mean?
0
 
datafocusAuthor Commented:
So I have created a separate outbound policy as below... with 1 to 1 NAT
nat-SIPRTP.JPG
0
 
datafocusAuthor Commented:
Policy
sip-RTP.JPG
0
 
dpk_walCommented:
202 is the public IP of firebox external interface; then you cannot use it for 1-1 NAT and also the incoming part of the service would not get configured the way explained above.

I thought you have .202 dedicated only for PBX. If so, then ensure that .202 is not added as alias [to be used in policies using static NAT (what I tried to list in the my earlier post)].

Most of times PAT causes problems with voice protocols hence using 1-1 NAT is preferred but for 1-1 NAT you must have one public IP dedicated only for PBX other than the public IP of your firebox.

Let me know if I got you confused.

Thank you.
0
 
datafocusAuthor Commented:
Are you saying I need a spare IP that is not an alias? I dont have any spare.
0
 
datafocusAuthor Commented:
Great! Thanks for that. I think it was just the alias thing I hadnt tried... works fine with an aliased IP.

Thanks for your help!
0
 
dpk_walCommented:
Welcome; Happy to be of assistance.

Thank you.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now