Jump to content

Wifi Calling


Shima

Recommended Posts

I don’t know if anyone has already posted information about wifi calling, so I thought it would be good to add this.  In the last 2 weeks, I posted on the sprint.com forum and the Sprint reps were unable to answer the simple question of what port does wifi calling use. Previous to posting I called customer service and Airrave support and no one could answer either. I didn’t expect a detailed answer, but they could have called someone who knew the answer.  Anyway, two very knowledgeable users on the forum narrowed things down, and wifi calling uses UDP port 4500. I had already narrowed down the ports to a handful, since I found information on the web about TMobile’s similar wifi calling. Also, I found a netstat option built into my Asus RT-AC66U router that was helpful for looking at ip/ports for our phones. The Sprint server the wifi calling traffic heads to is 68-31-26-1.pools.spcsdns.net  The reason I started asking about the port and connectivity is because we experienced many calls that would either drop or when you called someone it would go silent during the call. This goes along with UDP traffic being connectionless and sensitive to any disruption.  I prioritized traffic for our GS4T and GS5 phones for port 4500 and found there was a firmware updated from Asus for the router that helped.  Also, I skimmed over (on some other android forums) the updates for the GS5 to android 4.4.4 and I noticed something with wifi calling bug fixes.  I am happy to say that the wifi calling is working a lot better now. 

 

 

  • Like 1
Link to comment
Share on other sites

So far after removing the port priority I've noticed that HD calling and wifi calling will interrupt each other.  Sunday when I was called by a relative, the called started with wifi, and then become choppy and had pauses with no voice. This happened within the first couple minutes of the call. I hung up and called back and noticed the call establish in HD (as it now shows up with 4.4.4 Android).  I wonder if anyone else has run into this, and if it has contributed to the issues I've experienced recently. 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...