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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

bandwidth.com sip trunk

Status
Not open for further replies.

silicondarktide

IS-IT--Management
Apr 5, 2013
99
US
Has anyone got bandwidth.com sip trunk working with 500v2 8.0+?

They use ACL instead of username and password which is throwing me off.

We setup a static IP on our firewall that maps to the internal IP of the IPO500v2.
We also allowed the primary and secondary IP bandwidth.com told us full access through firewall to the IPO500v2. All other WAN IPs are blocked.
Do I need to setup anything special in my LAN settings? Right now STUN and PUBLIC IP are 0.0.0.0 Firewall is unknown.

They gave me a domain name but I can't seem to resolve it. OT.bandwidth.com
I used the primary IP as domain and proxy.

I can't even get incoming calls to work.

When I call them they say they can't directly help me because of liability issues.. wtf?
 
If they can't help you then can their butt, poor customer service if you ask me.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
Can someone recommend a good SIP trunk company.
Only need 2 trunks, unlimited LD.
This is what bandwidth.com is selling, just a pain in the butt to setup.
 
I got one site using them. It took 2 days of trial an error to get it working and their support was almost worthless. I'm running this on 7 still. It works so no reason to upgrade.

I'm behind a sonicwall firewall passing traffic to the IPO. I've got my stun server as 0.0.0.0, firewall is unknown. I've got public ip filled out with the IP I'm forwarding traffic from the sonicwall with. For my itsp domain name I'm using the ip address 216.82.224.202. Using the same for the ITSP proxy address. Let me know if you have any more questions.
 
voip.ms is very easy to setup and easy to manage from a BP end, but technically not supported by Avaya

Broadvox works well and supported by Avaya, but its all contract based, might not be good for 2 SIP trunks.

Try voip.ms, you can test stuff on the fly, creating usernames and passwords, ordering DIDs within secs. Use them for E911 service for remote sites and backup trunks for our inhouse system.
 
jhall mine is setup exactly the same as you say.

What codec are you using?
Eveything else default on the SIP line?
 
Ok so I took the sonicwall out of the picture and it works.
I hooked up the LAN2 directly to the internet modem and gave it the same outside IP I was natting through the firewall.

Something going through the sonicwall is messing it up. I don't have SIP transformation enabled.
I setup a 1:1 Nat from the outside IP to the internal Lan1 IP of IP office.
I even allows ALL incoming on firewall settings for testing. Meaning it was full access to the IP office from anyone. any port.

NAT was setup as Full Cone with outside IP in the (public ip) part of network settings in ip office.

--Daniel
 
jhall123 on the URI tab what did you set the

Local URI
Contact
Display Name

?

Should they be "Use Internal Data" or would * be better on all 3?
 
I have a channel with * for everything. I had to build the local URI with DID information to get it to push out the DID as caller ID. Internal data for the other fields for the ones I used the DID number in the local URI.

Also in my Sonicwall I do have SIP transformations turned on as well as Enable consistent NAT checked. It's been over 2 years since I set this up but I think those were pretty important to getting this to finally work.
 
OK so after weeks of changing 10000 different settings and combos I figured out the one thing that was messing up my SIP calls from bandwidth.com

I had it on "full cone nat" which is correct right??? It's a sonicwall with NAT. I did a 1 to 1 port to a static outside WAN IP.

Anyways I tried 100s of firewall settings/combos in the sonicwall and same stuff would happen. Ringing but couldn't answer on the deskphones. Just odd stuff.

What fixed it was changing to "static port block" in network topology on the IP office. "Full cone nat" would not work right.

All the STUN servers found "full cone nat" also. This is why I left it that way for so long.
 
flowroute has always worked GREAT for me, except for the incident the other weekend that took me out for 2 days. Some core routing equipment died in california...oh well.

-Austin
ACE: Implement IP Office
qrcode.png
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top