7 site IPO SCN with Avaya SBCE, split-dns & 1 public IP 2

[rgunther]

Hey guys...
So my vendor is helping set up an avaya SBCE for our 7 site IPO SCN. We have split dns setup in which on the public inet the FQDN's of the 7 sites all resolve to the public IP of the SBCe. On our private LAN, the FQDN's then all resolve the the public IP's of the individual IP500's. I have been told by several that this is completely fine and correct setup / but our vendor is telling me that we do have to have 7 public IP's (one for each IP office). We are stricly going to be using J179 SIP phones via the SBC Only. Do we really have to have 7 separate public IP's, or is the split-dns setup we are using with a single public IP on the sbce ok?

Thanks,

 

[rgunther]

Bump - Anyone used in this scenario? Thanks,

 

[kyle555]

https://www.tek-tips.com/viewthread.cfm?qid=1808748

?

 

[rgunther]

Thanks Kyle-
I do remember your previous recommendations, and am planning to set up our sbce this way. However, our Avaya re-seller is trying to pre-configure the sbce for us before shipping out, and I am trying to explain to them how we would like it configured. I have explained that we would like to set it up using our split-dns entries and the phones will be pointed to the sbce using the fqdn. They are telling me that I still need to have 7 routable IP addresses assigned to our SBC (one for each IP500). I explained that we would point all phones to the fqdn (which is currently resolvable on the public side to the IP address of the SBCe). Then on our internal/private side, all the FQDNs properly resolve to the corresponding IP office chassis. There response was "I don’t know of any way to route the calls by fqdn, with the ASBC. I asked my rep at Avaya he did not think it was possible with the Avaya border controller. If you know someone who can give me an example of the programming for to do this I would be happy to test it in my lab."

Do you have any recommendations I can pass on to my partner in order to get the initial config of this done? Thanks all very much for the assistance.

 

[rgunther]

And just got this response today -

"I spoke my technical rep at Avaya, and the t4 tech I was working on a different SBC issue, and they both said that there was no way the Avaya sbc could route calls the way you want. I also spoke to an engineer from a company that does nothing but work on border controllers and he also said there is no way to route calls using split DNS. He said there may be a way to route the calls by extension number, but that would not be able to even look into it for another 2 weeks."

 

[kyle555]

I was suggesting the 7 FQDNs to the same IP so the cert would work for any Workplace client

Otherwise, I'm saying to just setup 7 signaling interfaces on the same IP with different ports with 7 media interfaces and do the remote worker config 7 times.

It's a bit different if you're not the one configuring it. And hey, there's nothing wrong with using 7 IPs and if the people doing it want to follow their cookbook, good on them.

 

[rgunther]

Thanks Kyle. Being that we do have the public IP's available, I think we will just give them 7 public IP's per their request; and change our public DNS entries so that each FQDN points to the new public IP. I liked the idea of a single IP and seperate ports for each; but I guess 7 different public IPs will be fine too. I am assuming these public IP's will only be configured on the sbc, and not needed to be entered on the Avaya IP500 itself?

 

[kyle555]

That sounds right. IP500 needs the public IP when it's allowing remote registrations and you're just port forwarding from the router, but with the SBC in the middle, the IPO shouldn't need to know or care about the real public IP.