• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Vintalk SIP trunks

Status
Not open for further replies.

gfrisco

Joined
Mar 17, 2011
Messages
7
Reaction score
0
Trying to get Vintalk SIP trunk set up on my 3CX.

This is what it shows in the Server Activity Log:
16:52:05.795 [CM504005]: Registration failed for: 10000@Vintalk; Cause: 503 Service Unavailable; warning: ; internal

and below is what it show if I run the Firewall checker:


3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

<17:05:18>: Phase 1, checking servers connection, please wait...
<17:05:18>: Stun Checker service is reachable. Phase 1 check passed.
<17:05:18>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
<17:05:19>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 13268::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

<17:05:19>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
<17:05:19>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 13268::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

<17:05:19>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
<17:05:19>: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 13298::5090. Phase 3 check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

<17:05:19>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
<17:05:21>: UDP RTP Port 9000. Response received WITH TRANSLATION 17208::9000. Phase 4-01 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9001. Response received WITH TRANSLATION 17209::9001. Phase 4-02 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9002. Response received WITH TRANSLATION 17210::9002. Phase 4-03 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9003. Response received WITH TRANSLATION 17211::9003. Phase 4-04 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9004. Response received WITH TRANSLATION 17212::9004. Phase 4-05 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9005. Response received WITH TRANSLATION 17213::9005. Phase 4-06 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9006. Response received WITH TRANSLATION 17214::9006. Phase 4-07 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9007. Response received WITH TRANSLATION 17215::9007. Phase 4-08 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9008. Response received WITH TRANSLATION 17216::9008. Phase 4-09 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9009. Response received WITH TRANSLATION 17217::9009. Phase 4-10 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9010. Response received WITH TRANSLATION 17218::9010. Phase 4-11 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9011. Response received WITH TRANSLATION 17219::9011. Phase 4-12 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9012. Response received WITH TRANSLATION 17220::9012. Phase 4-13 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9013. Response received WITH TRANSLATION 17221::9013. Phase 4-14 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9014. Response received WITH TRANSLATION 17222::9014. Phase 4-15 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9015. Response received WITH TRANSLATION 17223::9015. Phase 4-16 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9016. Response received WITH TRANSLATION 17224::9016. Phase 4-17 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9017. Response received WITH TRANSLATION 17225::9017. Phase 4-18 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9018. Response received WITH TRANSLATION 17226::9018. Phase 4-19 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9019. Response received WITH TRANSLATION 17227::9019. Phase 4-20 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9020. Response received WITH TRANSLATION 17228::9020. Phase 4-21 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9021. Response received WITH TRANSLATION 17229::9021. Phase 4-22 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9022. Response received WITH TRANSLATION 17230::9022. Phase 4-23 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9023. Response received WITH TRANSLATION 17231::9023. Phase 4-24 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9024. Response received WITH TRANSLATION 17232::9024. Phase 4-25 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9025. Response received WITH TRANSLATION 17233::9025. Phase 4-26 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9026. Response received WITH TRANSLATION 17234::9026. Phase 4-27 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9027. Response received WITH TRANSLATION 17235::9027. Phase 4-28 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9028. Response received WITH TRANSLATION 17236::9028. Phase 4-29 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9029. Response received WITH TRANSLATION 17237::9029. Phase 4-30 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9030. Response received WITH TRANSLATION 17238::9030. Phase 4-31 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9031. Response received WITH TRANSLATION 17239::9031. Phase 4-32 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9032. Response received WITH TRANSLATION 17240::9032. Phase 4-33 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9033. Response received WITH TRANSLATION 17241::9033. Phase 4-34 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9034. Response received WITH TRANSLATION 17242::9034. Phase 4-35 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9035. Response received WITH TRANSLATION 17243::9035. Phase 4-36 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9036. Response received WITH TRANSLATION 17244::9036. Phase 4-37 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9037. Response received WITH TRANSLATION 17245::9037. Phase 4-38 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9038. Response received WITH TRANSLATION 17246::9038. Phase 4-39 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9039. Response received WITH TRANSLATION 17247::9039. Phase 4-40 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9040. Response received WITH TRANSLATION 17248::9040. Phase 4-41 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9041. Response received WITH TRANSLATION 17249::9041. Phase 4-42 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9042. Response received WITH TRANSLATION 17250::9042. Phase 4-43 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9043. Response received WITH TRANSLATION 17251::9043. Phase 4-44 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9044. Response received WITH TRANSLATION 17252::9044. Phase 4-45 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9045. Response received WITH TRANSLATION 17253::9045. Phase 4-46 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9046. Response received WITH TRANSLATION 17254::9046. Phase 4-47 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9047. Response received WITH TRANSLATION 17255::9047. Phase 4-48 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9048. Response received WITH TRANSLATION 17256::9048. Phase 4-49 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<17:05:21>: UDP RTP Port 9049. Response received WITH TRANSLATION 17257::9049. Phase 4-50 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/


Application exit code is 53
 
It appears that your router is doing some port translation. What make/model are you using?
 
It is a SonicWall 240
 
sonicwalls are good for that. look for an enable SIP ALG check box


SIP
•Enable SIP Transformations - Select this option to transform SIP messaging from LAN (trusted to WAN (untrusted). You need to check this setting when you want the SonicWALL to do the SIP transformation. If your SIP proxy is located on the public (WAN) side of the SonicWALL and SIP clients are on the LAN side, the SIP clients by default embed/use their private IP address in the SIP/Session Definition Protocol (SDP) that are sent to the SIP proxy, hense these messages are not changed and the SIP proxy does not know how to get back to the client behind the SonicWALL. Selecting Enable SIP Transformations enables the SonicWALL to go through each SIP message and change the private IP address and assigned port. The Enable SIP Transformation also controls and opens up the RTP/RTCP ports that need to be opened for the SIP session calls to happen. NAT translates Layer 3 addresses but not the Layer 5 SIP/SDP addresses, which is why you need to select Enable SIP Transformations to transform the SIP messages. It's recommended that you turn on Enable SIP Transformations unless there is another NAT traversal solution that requires this feature to be turned off. SIP Transformations works in bi-directional mode and it transforms messages going from LAN to WAN and vice versa.
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,611
Messages
748,810
Members
144,721
Latest member
jabren
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.