Yeah, I have leveraged LAN1 for the sip trunk before.
I've never come off the A1 interface on the SBC and gone directly into LAN1, usually we have a switch inbetween, but I don't see why it wouldn't be doable
My situation is this:
Windstream trunks coming in from their voice edge/sbc (10.250.0.5). From there they route to their router that is at the customer site (a.b.5.1). From there the traffic goes to our SBC B1 (a.b.5.3). Now the traffic needs to get to the IPO. LAN 1 is on a different subnet though. The A1 interface IP is 1.b.2.3 and the IPO LAN 1 is a.b.2.21.
Having trouble understanding what routing needs to be in place for the SIP traffic to get from Windstream voice edge (10.250.0.5) to IPO (a.b.2.21).
Thanks for your reponses. To clarify, there is a switch between A1 and LAN1. I have followed the document to setup the IPO and SBC however it is still not working. The document refers to a LAN2 setup for the SIP Trunks. Also, you referenced the Session Flows to address my problem traversing the .2 and .5 subnets but I'm not understanding how the session flows will help. Any help is greatly appreciated.
Hi, I am working with VTTD1870. We have configured, and went by all 3 devconnect application notes (that we can find) that deal with Windstream SIP /SBC 6.2 and IPO 9.0. The only application note that uses session flows, is the Broadsoft Platform, and that is using LAN2 for the sip connection, which we can not use. Only the Sonus and the Metaswitch Platform are configured to use LAN1 for the SIP connection, but these notes do not use session flows?
Are their different application notes out there that deal with this set up?
Also if you can explain how the IP flow is supposed to work. My understanding is that the IPO LAN 1 looks to register to the SBC internal IP first, then the SBC talks to the Windstream Router, then out to the SIP IP. Is that right?
When I ping from the IPO system status, the sip trunk pings from the LAN1 to the SBC internal IP, which does work.
We can not ping out to the Windstream SIP IP from the SBC, not really sure if we are supposed to be able to do that??
The way the heartbeat is configured in the SBC is that it tries to ping from external SBC ip to the Windstream SIP IP.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.