Can't Connect to Sip Trunk
-
Tagging
@Mike-Ralston and @art_of_shred -
What steps should I try to troubleshoot this?
There is a proxy, however I have added it to FreePBX.
The ports are open. I can't ping inbound35.vitelity.net, however with the proxy I am not sure if I should be able to or not....
-
Is tcp correct? Shouldn't that be udp for that traffic?
-
Instead of ping, try a traceroute to the server. See what it hits, where it stops, etc.
-
@art_of_shred said:
Is tcp correct? Shouldn't that be udp for that traffic?
Um.... I think so? Sorry, I am not a SIP expert...
-
Vitelity has the settings required on their website although you need to specify both inbound and outbound. I think it should be UDP.
-
@coliver Beware the accuracy of what they list on their site. Try it, but you may end up needing to open a support ticket to get the most current settings. I've encountered that before, more than once.
-
@art_of_shred said:
@coliver Beware the accuracy of what they list on their site. Try it, but you may end up needing to open a support ticket to get the most current settings. I've encountered that before, more than once.
That's right, I remember you guys saying something like that. It's unfortunate they can't keep those settings up-to-date.
-
Well that's not good. Maybe the proxy is in the way? or is it more likely a firewall issue?
Sadly, I don't have access to the firewall, but I have to email HQ.
traceroute to inbound35.vitelity.net (66.241.99.208), 30 hops max, 60 byte packe ts 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * -
I opened a ticket for the most up to date settings to use with FreePBX.
-
Well that was quick:
Hello,
This is a courtesy message from Vitelity Communications regarding an active Trouble Ticket you have in our system for the account 'XXXXXXXX'.
Your Trouble Ticket has been updated with a response/resolution to your problem.
Posted by vcdreece on 2016-02-09 08:31:26
Hello,You will want your trunk settings to look like this:
[vitel-inbound]
type=friend
dtmfmode=auto
host=inbound35.vitelity.net
context=from-trunk
username=
secret=
allow=all
insecure=port,invite
canreinvite=no[vitel-outbound]
type=friend
dtmfmode=auto
host=outbound.vitelity.net
username=
fromuser=
secret=
trustrpid=yes
sendrpid=yes
allow=all
canreinvite=noregister => rfna_XXXX:[email protected]:5060
Please let us know if we can be of any further assistance.
Sincerely,
David
Network TechnicianPlease visit https://portal.vitelity.net/login.php?show=tickets for more information regarding this ticket.
Sincerely,
Vitelity Communications
[email protected] -
@anonymous said:
Well that was quick:
<snip>The question is: Were you able to get it going again?
-
@dafyre No, still not working
-
Sent a email to HQ to confirm the ports are open.....
-
@art_of_shred said:
Is tcp correct? Shouldn't that be udp for that traffic?
SIP is TCP. RTP is normally UDP.
-
@anonymous said:
Well that's not good. Maybe the proxy is in the way? or is it more likely a firewall issue?
Do you have non-web traffic going through the proxy? If so, does it pass it?
-
-
@anonymous said:
@scottalanmiller said:
SIP is TCP. RTP is normally UDP.
It is? HQ said they opened udp only.....
You CAN do SIP on UDP. Not many places do.
-
@scottalanmiller Well that could be a problem
-
Just got a confirmation from Vitelity, they do use UDP.
