Half-Duplex incoming calls (outgoing is fine)
sdb-:
Quote from: wr5678 on December 18, 2013, 03:00:32 pm
The device does get a routeable IP address, I've tried making it a DMZ host (there is an option to forward incoming to a single host on the network in the router), that didn't make a difference.
That does not make sense.
What device gets a routeable IPv4?
What device did you make a DMZ host?
Quote
If it's some sort of routing problem, why do both RTP streams come up and work for an outgoing call, but not for an incoming call (i.e. the caller hears me, but I don't hear them).
Not specifically a routing problem, but because of NAT. Any NAT can mess up SIP leading to what you describe. Routeable address is just a way of detecting NAT.
Any addresses in these ranges are not routeable across the Internet: 192.168.x.y/16, 172.16-31.x.y/12, 10.x.y.z/8. Technically anything can be made not-routeable by your ISP, and there are a few others that sometimes get used, but hopefully not often as services using those addresses will be broken...
If you visit a "what is my ip" page, the displayed IP address for you should be the same as shown on your PC network interface properties if you have a routeable address to your PC, or your modem/router's WAN address if it is the routeable address, or something totally unlike anything on your devices if carrier NAT or going thru a web proxy.
If you have a routeable address on every device it means you don't have any NAT. If you have a routeable address only on your modem/router's WAN interface then the NAT is done by your modem/router and hopefully under your control. If nothing you have gets a routeable address then you have carrier NAT and all bets are off.
wr5678:
The router WAN interface has a routable IP address. I have the WAN interface on the obihai set for DHCP, and it gets a private ip address from the router which is performing NAT.
In the port forwarding rules for the router no combination of ports i've found (up to and including putting the obihai into the DMZ) makes the issue I'm having go away.
I can always make outgoing calls, but I never get audio on my side of incoming calls, the caller can hear me.
Tried alternate ports with SIP provider, STUN, no STUN, looking for other ideas.
MikeHObi:
Did running the VOIP test give you any indication of an issue?
http://myspeed.visualware.com/indexvoip.php
Mango:
Quote from: wr5678 on December 18, 2013, 11:59:38 am
Incoming calls ring, I can answer fine, however I cannot hear the caller (but they can hear me).
Half-duplex audio is where the other party is temporarily muted while you're speaking, and it's impossible for them to interrupt you - a la walkie-talkies. What you're describing is one-way audio, which may be why you've received some suggestions that didn't work.
May I suggest you set the following:
Service Providers >> ITSP Profile x >> SIP >> X_DiscoverPublicAddress: (unchecked)
Also, disable STUN.
My guess is that CallWithUs is trying to negotiate direct media, which is failing. I hope this will force it to proxy the audio. Let us know if this solves the problem or changes the symptoms.
Navigation
[0] Message Index
[*] Previous page