Jump to content

lilotimz

S4GRU Staff
  • Posts

    9,863
  • Joined

  • Last visited

  • Days Won

    141

Posts posted by lilotimz

  1. What would happen if I put a iPhone 8 SIM in a iPhone 6s??? I find it odd that Sprint needs different SIM's for different phone's when the other 3 carriers and MVNO's can provide a single universal SIM...
    It will not authenticate and the iPhone 6 will not have service.

    Sprint Sims are paired to device and specific to device models as currently designed.

    Sent from my Pixel 3 using Tapatalk



  2. I bought a Huawai 5G CPE Pro router/hub.  It supports Sprints 4G LTE (Band 41) among many other bands.
    I ordered a SIM card for it:
            https://shop.sprint.com/mysprint/shop/accessory/ao_details.jsp?accSKU=121700244&accCatId=78300001
    This is a 4-pack of SIM cards, labeled A, B, C, D.  Card A didn't work.  Card B,C,D were recognized, and I have Card D in there now and it is talking to the Sprint network (green lights, 3 bars, 4G LTE, etc. etc). The 5G CPE Pro uses a nano-SIM card.
    HOWEVER, SPRINT WILL NOT ACTIVATE THIS UNIT.  Tried talking to them for 2 hours, many many reps, support, etc.  All they say is that 'the database says that it isn't "eligible".   "Eligible" is a funny word.  They don't say incompatible, or that it doesn't work, or that it is the wrong band or wrong protocol.  So I assume that all Huawai is flagged in Sprint's database due to the USA ban.
    So be forewarned.  I also tried using one of my already-activated nano-SIM cards, but the 5G CPE Pro still wouldn't do internet things.  Even though it  IS  talking to the Sprint tower (I can see the back-and-forth handshake traffic).
    It is a nice unit, and does many 4G and 5G bands.  Huawei 5G CPE Pro, model#   H112-372   (there is another model of the CPE Pro that is less capable).
    Scott
     
     


    Just because it supports the technologies sprint uses doesn't mean it's compatible.

    All networks that uses the Sprint network must pass through their internal testing and then be white listed. The Huawei is not a support device and is being rejected by the network as such.

    Sent from my Pixel 3 using Tapatalk

  3. On 11/22/2019 at 5:46 AM, red_dog007 said:

    The only 5331 I am seeing is 37-40GHz. 

    Also didn't think m-mimo as a thing yet in mmwave. 

    Air5121 is the correction.

     

    - Oh yes it very much is. All current mid high band 5GTF and NR 5G deployments use M-MIMO antennas. 

    sCZBbDf.png

    MVsfMBu.png

    • Like 5
  4. I suspect that in addition to lack of 5 GHz support, there's some other compatibility issue that's holding you up.  What Wi-Fi router do you have and what encryption is it running?
    5 GHz works fine on my UBNT AC Lites and AC68p.

    They're 2.4/5 GHz Qualcomm AC1300 chips.

    Sent from my Pixel 3 using Tapatalk

    • Like 2
  5. On 9/30/2019 at 8:33 AM, Rawvega said:
    As we're about to enter October, the September security update is now available. No VoLTE, of course.

    Sent from my SM-N960U using Tapatalk

     

    Ofcourse not yet. Theres a schedule for when that's to be pushed out. I would say you wouldn't say that next month =p

    Sent from my Pixel 3 using Tapatalk
     

    • Like 1
    • Thanks 1
  6. The issue with devices holding onto fringe 1x800 connections instead of the strong 1X connection from the Airave is common and incredibly frustrating. The Airave 2.5 had a 1x800 beacon that your phone would "see" and know to flip to it. There is no comparable feature in the A3 or A4, so until your device scans other 1X bands, it never lets go of the macro 1x800.
     
    The solution I have found works best for me is to force 1X to only use Sprint's 1900 MHz PCS network -- although that may not be in everyone's best interest, depending on the coverage in the areas you frequent. There is a shortcut in SCP to change this, go to System Shortcuts > Voice Band Mode and select "PCS". Understand that you will no longer connect to 1x800 and I believe 1X roaming will also be impacted unless the roaming partner uses PCS bands. To change back to factory behavior, simply go to that menu and choose "Automatic".
     
    You could also choose PCS each time you get home, and switch back to Automatic once it connects to the A4.
     
    -Mike
    Just to clarify for others.

    The Airave 3 had a 1x800 Beacon... It was just never really worked (like the A3 itself). The airave 4 just doesn't have it at all.

    So if your device is on 1x800, unless you toggle the 1x radio to refresh the scan, it will stay on 1x800.

    You need to force the device to scan and latch onto 1x1900 or already be on 1x1900 in order to use the Airave 1x.

    Sent from my Pixel 3 using Tapatalk

    • Like 1


  7. So my Airave 4 arrived and I connected it. After hours I am left with this situation
    1) The WAN, L-NET, GPS, and LTE lights are solid green
    2) The C-NET and CDMA lights cycle between flashing red or just off
    3) I have an LTE signal (no VoLTE), and get about 70 Mbs down when near the device
    4) My WiFi calling works nicely through out the house as it always sees an LTE tower for GPS location
    5) No CDMA signal (see #2 above), but can live with that as WiFI calling now works reliably
    The curious thing is when I went to do Port Forwarding to open the ports, there are two devices showing up. One with a MAC ID of 00:a0:0a:6f:e4:26 and the other with 00:a0:0a:6f:e4:27.  Curiously, my ASUS router identified the 26 devices as XEROX CORPORATION, but didn't do an identification for the 2nd box. Online reference shows they both belong to Airspan.  Anyhow, the question is, to which device do I forward the ports 53, 67, 500, and 4500.  Right now, I have them all forwarded to the 27 device. I'm wondering if two of the ports are for the CDMA tunnel and two for the LTE tunnel and to split the forwarding up in some manner. On the A3, I only saw one device and forwarded all ports to that device.


    The CDMA and LTE femto are separate devices in one package hence the two Mac IDs and two IP addresses used by the unit.

    No port forwarding is needed as it's plug and play (generally).

    For CDMA, make sure the GPS is properly positioned and then leave it be. Sometimes it takes a few days for the unit to stabilize but if it doesn't then send me a PM and I can maybe see if I can poke someone to take a look at why it is not working properly.

    Sent from my Pixel 3 using Tapatalk

    • Like 1
  8. [mention=21091]ingenium[/mention] or anyone else, i really dont want to give up, i get no reception in my house....any suggestions?

    Factory reset your Eero and redo everything from the ground up is what I'll say.

     

    Something about the eeros current configuration is blocking the A4 and just doing these Config edits are not helping much.

     

    So factory reset it to the basics and make sure the A4 works with that. Then slowly add custom settings and rules while ensuring the A4 is operational.

     

     

    Sent from my Pixel 3 using Tapatalk

     

     

     

  9. 23 minutes ago, SeanK_ said:

    No no no! 

    Ok, look at my setup. https://imgur.com/yxvJBZr This is how I got this figured out.

    I want you to do this.

    Modem has 4 ethernet ports, plug the airave into the first port with the black cable, now plug the eero into the second port with the white cable, now the eero has an extra port, plug the ethernet cable to the switch yellow cable, then the blue and yellow cable for the tv/tivo can be connect to the switch.

    That won't work unless he has multiple static IP addresses.

    The A4 itself will need 2 IP addresses. One for the CDMA network and one for the LTE network. It needs to be placed behind a router in a typical setup and a CM1200 is not one as it's strictly a D3.1 modem with multiple GBe ports. 

    The Eero may need to be modified to do port forwarding and in the worst case scenario may need to place the A4 into a DMZ net. 

  10. 49 minutes ago, jtrotter54 said:

    =

    I've attached a picture.

    The modem does not have wireless routing capabilities. I rearranged the switch. Now the order goes Airave, Eero, TV and TiVo. It looks like a promising setup as both Eero and TiVo are working along with the MoCA connection for the TiVo Mini. However, while most lights on the Airave are solid green, L-Net and LTE are blinking red. Thank you!

     

    A cable modem, such as the CM1200, passes a single public IP address to the device connected behind it. It is not a router. It does not do routing or if so it's very limited. 

    The proper setup is Modem --> Router --> Switch --> hardwire connected devices. 

    So make sure the white ethernet cable goes into the Eero's WAN port. Then you want to connect an ethernet cable from the LAN port of the Eero into one of the ethernet ports on the switch. Then you want to connect other hardwired devices, like the AIrave 4, to the ethernet switch. 

    Also give the Airave 4 a good hard reset when you do this so it erases whatever previous IP assignment it had on file. 



  11. [mention=14486]SeanK_[/mention], [mention=21091]ingenium[/mention] or anyone else that can help a basic user. I attached a picture of my setup (can't see the TiVo), I have RCN internet. The only time the Airave seems to almost work, is when the wifi is down, the eero and airave are not working together. What can I do to get this to work? About ready to give up. Thank you all.
    IMG_20190902_172321094_4274.thumb.jpg.9c9b971560db63b38d0ff55c868a5d32.jpg


    Plug the airave 4 into the switch behind That is connected to the eero.

    It's very likely your RCN cable modem router is in bridge mode and passing the single public IP address to the Eero which is doing NAT+DHCP+ routing.

    What's likely happening is there is an ip conflict as you likely only have one IP address given to you as part of your residential account hence why when Eero is off then the A4 works.

    TLDR: connect the A4 behind the eero so it gets a private ip assignment and not fight over it for the single public ip.

    Sent from my Pixel 3 using Tapatalk

  12. 16 port antennas in Ericsson markets should feature two RRUS11 which are virtually chained together to act as a single 4x RRU.
    I don't recall if Sprint is deploying a single 4-port radio in Ericsson regions. Maybe [mention=4387]lilotimz[/mention] can chime in and clarify this. 
    There is no B26 + CDMA model for ALU, Nokia, or Ericsson. They will continue to use those RRUS11 B26s and 2x50 800's unless Ericsson decides to make a 4x4 44xx series radio.

    To date for all carriers, Ericsson is super impacted for 4x4 radios of the newest gen. They've been using 2x2 22xx radios and software bonding them to leverage 2x4/4x4 while additional 4x4 44xx radios are being produced and delivered.

    Only Samsung produced a new 800 MHz CDMA+LTE radio and its probably because they had to make a 750mbz + cdma radio for the PR VI region and it wasn't a big deal to make it for 800.

    Sent from my Pixel 3 using Tapatalk

  13. Starting to think this phone simply isn't getting it. But, when I use LTE calling on this S9, the call quality is horrendous. I'd rather not use it and keep legacy 800 CDMA. Voice over LTE will never be even close to as reliable, at least from my experience here in Atlanta when using LTE calling vs CDMA. The difference is staggering.
    Voice over LTE has minimum GBR as part of its QOS. Calling Plus does not.


    There is a world of difference between the two implementations and the voice quality.

    Sent from my Pixel 3 using Tapatalk

    • Like 1
  14. 5 minutes ago, mdob07 said:

    At the rate they're throwing these up around here I wouldn't be surprised if they try to launch 5G here first half of next year. Three weeks ago I found 4 site conversions in one week. The new GCI makes it easy to notice the change even if I don't directly drive by that site. 

    There is actually multiple Air6468/6488 revisions floating around with different supported frequency bandwidths and the like....

  15. Have there been any comments about VoLTE or WiFi/Ethernet backhaul?  I feel like it's the missing piece for networking at my condo.
    I don't recall if I mentioned it here but major updates like those above features are usually sent out each quarter so it's not ready as I last checked a few weeks and they don't expect it til at least fall at the earliest.

    They've been doing field tests on the alternative backhaul mode but it requires network configurations and hw deployments out of the hands of the MB team.

    Sent from my Pixel 3 using Tapatalk

    • Like 1
  16. Question for you all. It would appear that a new B41 small cell has appeared in downtown DTW right in front of the RenCen. It is on Cellmapper with the EARFCN of 40270, PCI of 466 and band 41 RSRP of -58dBm. You can see something that looks like it might be a small cell but it's not up on a pole, it's just on the side of a box but there is conduit laying on the ground next to it. https://www.google.com/maps/@42.3300147,-83.0409325,3a,18.7y,328.84h,87.13t/data=!3m6!1e1!3m4!1sjf7wH1t39cFa2MR41W2Tiw!2e0!7i16384!8i8192
    Thoughts?
    Yeah that's a typical omni antenna mounted to the little cabinet which likely houses the small cell unit.

    Sent from my Pixel 3 using Tapatalk

    • Like 4
×
×
  • Create New...