BigMatza
join:2005-06-24
Philadelphia, PA
|  [Other] One-way audio problem for Direct-to-PAP2
STUN Config (from SIP) | 
Line 1 Config |
Ok.. here's an interesting quagmire:
I went through the process of setting up an IPKall-direct-to-PAP2 configuration. I'm having a problem with the direct dialing. I performed a battery of tests, and the results are baffling... I should also note that I have a FWD account configured on the troubled line. I assume most people who signed up for IPKall had a FWD account at some point.
TEST 1 - Calling IP phone from a landline to a PSTN-to-FWD gateway... Chose "option 2" at voice prompt, and entered my 6-digit FWD account number: NO PROBLEMS!
TEST 2 - Dialing my IPKall number directly from a landline: IP phone rings promptly. The IP phone can receive audio from the caller. The caller cannot receive audio from the IP phone.
TEST 3 - Added a permanent forward URI (sip:username@myhost.dyndns.org) to my FWD account: I perform the same steps in TEST 1 above. The IP phone rings as expected. No audio in either direction, and after about 4-5 seconds, the IP phone makes a busy signal. The landline just continues to emit dead air.
I have performed these tests calling from both a mobile phone, and also from another VoIP provider, both yielding the same results.
I've already attempted putting the PAP2's IP address in the DMZ, with no success.
I'm have 3.1.6(LS) on my PAP2, behind a WRT54G running DD-WRT v0.23b. Additionally, I am mirroring DracoFelis's STUN config and Line-1 settings, which is where IPKall points. Screenshots attached.
Any thoughts? I'd be much obliged to receive a response from the great one himself (DracoFelis.. you the man!)
Thanks. |
|
DracoFelis
Premium
join:2003-06-15
| Re: [Other] One-way audio problem for Direct-to-PA
Sorry to say, I'm stumped too. My initial idea as to what is wrong didn't turn out to be the case, as your PAP2 settings all appear (to me) to be correct for this "trick"! So I don't know why the 1-way audio.
About all I can suggest, is to setup your PC with a SysLog server, and turn on "debug mode" on your PAP2 (I'm assuming that the PAP2 has the same debug mode as the Sipura). If you did that, you might be able to tell from the debug mode log files, what is going on.
Or, you could just "give up", and route calls via FWD. Not exactly "direct to your adapter", but at least it appears to work for you. Sorry I couldn't be of more assistance... |
|
BigMatza
join:2005-06-24
Philadelphia, PA
3 edits |  reply to BigMatza
Re: [Other] One-way audio problem for Direct-to-PAP2
Thanks for the debugging suggestion. I'll try that out when I get home from work.
I've been thinking about the difference between talking to my PAP2 directly via SIP URI (sip:username@myhost.dyndns.org) versus through FWD's method (sip:123456@fwd.pulver.com). I understand that when connecting through FWD, FWD proxies the communication, passing data back and forth between the two endpoints. When connecting directly, IPKall creates some sort of direct connection between the two endpoints. If we dig a little deeper, what do we find as the relevant differences between the two connection models? Different ports? Is registration an issue? Is STUN used for both models?
INTERESTING RELATED MATERIAL:
Codecs - »www.voipuser.org/forum_post_701.html
VoIP/NAT Traversal -
-»www.voip-info.org/wiki-NAT+and+VOIP
-»ag-projects.com/docs/PressArticl···ices.pdf
Port Forwarding -
-»www.voipuser.org/forum_post_4556.html
-»www.voipuser.org/forum_topic_3777.html |
|
BigMatza
join:2005-06-24
Philadelphia, PA
1 edit | reply to BigMatza
I think I've honed in on a solution. I don't have the DD-WRT "VoIP" build, which runs a lightweight outbound proxy on the WRT54G. Apparently it makes up any STUN shortcomings fairly well.
»forum.bsr-clan.de/ftopic3190.html
Oh yeah, I just found out the WRT54G running DD-WRT is considered a symmetric NAT. Guess that answers some questions too! »forum.bsr-clan.de/viewtopic.php?t=4277
I'll try this when I get home, and post my results. |
|
