I just got some additional information from Jesse Rausch. It appears to be resolved.
Jesse: You can simply change one parameter to use your own core. MME IP is a web GUI parameter. An operator can change this to connect a Baicells eNB to a third party EPC. No remote programming is necessary for this. If you want to disable the local breakout to use the EPC's PGW, then you can configure a parameter in the CLI for this, which everyone has access to. Some customer may be sensitive to the fact that it is possible for technical employees of Baicells to remotely access their equipment. All customer radios have an IPsec tunnel to our cloud EPC. Because of this, I can remote into our cloud EPC, and from there, SSH into the client radio. It is recommended to change the default password on the eNB. This comes in very handy and I will at that point ask the customer for their password. For the duration of the trial, we will most likely keep ports open across the IPsec tunnel to make remote support easier. After the trials, we will most likely recommend all ports be closed except for a port for technical support to login to the eNB if necessary. Respectfully, Rick Harnish Director of WISP Markets Baicells Technologies, N.A.I Mobile: +1.972.922.1443 Email: rick.harn...@baicells.com <https://www.facebook.com/BaiCells> Follow us on Facebook for the latest news From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Rick Harnish Sent: Monday, June 27, 2016 10:52 AM To: 'WISPA General List' <wireless@wispa.org> Subject: Re: [WISPA] Baicells - who's deployed it? Nathan, Network security is very important to us. We are working on developing a secure channel to operators to enable operators to change ENB settings to flow to your own PGW. We will let everyone know when we have this accomplished. Until then, our technical staff will need to do this in the interim. It is a temporary limitation. Thank you for pointing this out. Respectfully, Rick Harnish Director of WISP Markets Baicells Technologies, N.A. Mobile: +1.972.922.1443 Email: rick.harn...@baicells.com <mailto:rick.harn...@baicells.com> <https://www.facebook.com/BaiCells> Follow us on Facebook for the latest news From: wireless-boun...@wispa.org <mailto:wireless-boun...@wispa.org> [mailto:wireless-boun...@wispa.org] On Behalf Of Nathan Anderson Sent: Sunday, June 26, 2016 3:12 AM To: WISPA General List <wireless@wispa.org <mailto:wireless@wispa.org> > Subject: Re: [WISPA] Baicells - who's deployed it? There has been a lot of talk about network performance both just by itself as well as compared to other products, but one thing I would be interested in hearing more discussion on -- assuming Baicells allows for it at this point -- is the configuration and management interface(s). Perhaps these UIs are in too embryonic a form currently for a productive discussion or a fair analysis to take place, and Baicells may be trying to concentrate this phase of the trial more on correct MAC function and performance. But as somebody who is intrigued by the idea of running a few of these side-by-side with a competing product on a heterogeneous (vendor-wise) 3GPP network with our own core, it would be good to know what we are up against as far as ongoing monitoring and maintenance goes, since it's presumably a given that we aren't going to be able to use our existing vendor's NMS (for example) to monitor and control these. Sooo...what does management look like at this point, what kinds of stats can you collect, and what mechanisms can you use to extract and collect them? Do operators using these ENBs feel somewhat blind at this point or are you able to track all of the performance indicators that you feel you need in order to be able to diagnose issues? As far as commissioning one of these ENBs goes, I would also be interested to know more about what that entails, especially given the claim of "4G Easy as WiFi." So what does that mean in practice, exactly? I admit I was a little disheartened to hear that at this point, in order to configure an ENB to send traffic to your own PGW, a Baicells engineer apparently has to remote into the thing to make the change for you. I'm hoping that this is a temporary limitation while they continue to work on the (beta) software and that this isn't a permanent state of affairs or indicative of the direction they are going, because as Patrick himself said during his ISP Radio interview, "we all like to drive our own cars." The goal of simplicity is a great one from both a "customer sat" and support perspective, so long as while you are chasing it you don't abandon or significantly hamper flexibility, restrict freedoms, and/or increase one's dependence on a third-party for every little thing. -- Nathan From: wireless-boun...@wispa.org <mailto:wireless-boun...@wispa.org> [mailto:wireless-boun...@wispa.org] On Behalf Of Josh Luthman Sent: Friday, June 17, 2016 12:09 PM To: a...@afmug.com <mailto:a...@afmug.com> ; WISPA General List Subject: [WISPA] Baicells - who's deployed it? Does anyone besides the guys in Amarillo have this gear deployed? Care to comment on/off list? Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
_______________________________________________ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
