SIP Trunks 1

[KyBoy]

I am setting up Sip for a customer and followed the notes from avaya but windstream didn't really know what the domain and proxy should be. So I asked for the public IP for my WAN/LAN 2 and after a test I could call out but no incoming

 

[Gunnaro]

What did you put in the URI tab on the Trunk?

(And when you get this working, you should really considering putting in a firewall between the Internet and LAN2).

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[Gunnaro]

Strange they had no info for you, as long as they did the comprehensive Avaya Compliance Test.

You can download the step-by-step for Winstream SIP trunks right HERE

On page 10, discard the recommended port range, since that might open for remote administration of your IPO.
Set min port = 49500 and max port = 50500

(and thanks for the star, to who ever gave it )

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[KyBoy]

Windstream gave me 192.168.0.17 from their SBC I set that address up as ITSP proxy and short code. I put the public address as my LAN2 and domain. We could make outbound but no inbound. We tried changing LAN2 to 192.168.0.18 and used that as domain and public but couldn't make inbound or outbound at that point. We tried several different setups but didn't work. They said there was an error code 503 when calling in and I never see the call hit the IPO in monitor

 

[Westi]

Sounds like incoming call route problem to me.
The SIP provider sends you the request but teh IPO doesn't know what to do with it.

Do a Monitor trace with all options disabled but SIP tab (only left hand side checkmarks) then call in and see what you get.
If you take out all private data then post it here and we can look but so far I think incoming call routing is the problem.

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[Gunnaro]

192.168.0.17? Not very public
Are you on some kind of VPN or other means of closed network with the provider?

If the provider see 503 from their side, it could also mean that they can't reach your system (which explains why you don't see anything on your side.)

Routing, badly configured VPN router, missing/bad IP route on IPO, etc.

Can you even Ping the other side?


Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[Westi]

he said that there is an SBC in play as well

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[Gunnaro]

I read that SBC as the far side, but I now see it can be an on-site equipment provided by the SIP provider as well

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[KyBoy]

So if Windstream hands off a local IP address for SIP through their router and SBC can I make that one SIP address as my domain and proxy in IPO?

 

[KyBoy]

And can I make that IP address given by windstream as my LAN2 IP address or is my thinking all wrong

 

[Gunnaro]

I have a hard time seeing the full picture here.

They only gave you one IP address? No MASK + Gateway?
Did they send you a SBC or VPN router? Or are you setting up your side with own equipment
What's the IP of the Provider side (SIP trunk server)?

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[KyBoy]

My LAN1 is 192.168.0.16 Windstream said they are going to give me 192.168.0.17 from their session border controller for SIP I have a spec sheet from them but according to the avaya notes windstream is supposed to give me a domain name and proxy address. I'm a little confused on what controls inbound and what controls outbound when I used short code
9N"@192.168.0.17 I was able to make outbound calls and I had LAN2 as win streams public IP address but WS tested inbound they said it didn't like the public IP there