Direct IP call: connected but packets not received
Toulousaing:
Hi,
hope you're doing well.
I'm trying to make simple direct IP call call from device A (static public IP) to device B (static public IP).
The device A gets connected to device B, but packets sent by A are not received by B. Both devices are running behind a NAT and I redirected all needed ports 5060 to 5063 (UDP+TCP) and 10000 to 20000 (UDP+TCP).
The symptom is that device B rings but when other person picks up, he doesn't hear anything, neither do I. I can see that devices are connected to each other with G711U codec, but packets sent by one party is not received other party (RTP Packet Count: tx=320;rx=0).
My configuration is the same on both ends:
ITSP profile B general > all default
ITSP profile B RTP > LocalPortMin : 10000
ITSP profile B RTP > LocalPortMax : 20000
ITSP profile B SIP > ProxyServer: 127.0.0.1
SP2 Service > SP2 Service > Enable: checked
SP2 Service > SP2 Service > X_ServProvProfile: B
SP2 Service > SP2 Service > X_CodecProfile: B
SP2 Service > SP2 Service > X_InboundCallRoute: aa
SP2 Service > SP2 Service > X_RegisterEnable: unchecked
SP2 Service > SIP Credentials > AuthUserName: aaaa
And I set in phone digitmap a shortcut to dial sp2(bbbb@bb.bb.bb.bb:5061) where bbbb is the AuthUserName of device B, and bb.bb.bb.bb is the public IP of device B.
Maybe it's due to device A sending to local IP of device B, and vice versa. Here is what I get:
State connected
Peer Number bbbb@bb.bb.bb.bb:5061
Peer RTP Address 192.168.0.13:10006
Local RTP Address 192.168.1.11:10000
192.168.0.13 is the local IP of device B, maybe it should be bb.bb.bb.bb?
Could you please help me?
Cheers :)
RFord:
Try setting up a STUN Server (for example, stun.ideasip.com; Port 3478)and also forward the RTP Port range (16600 - 16998) on your Router to your OBi Device.
Toulousaing:
Thanks for your answer.
Actually I'd like to avoid any need for third party, direct IP without STUN server should be possible as reported by other users.
Also, I port forwarded from 10000 to 20000, which includes the ranges you mentionned.
Aside from this, I managed to have the correct Peer RTP Address by setting my public adress in
ITSP Profile B SIP > X_PublicIPAddress
But I still have the same issue: no packets received on both ends.
azrobert:
You can try 2 methods.
ITSP profile B SIP
X_DiscoverPublicAddress: unchecked
X_PublicIPAddress: aa.aa.aa.aa (your local public IP addr)
OR
Using your current config.
ITSP profile B SIP
ProxyServer: bb.bb.bb.bb (device b public IP addr)
ProxyServerPort: 5061
Then call:
sp2(bbbb)
RFord:
I haven't done this on the OBi ATA, but have done IP dialing using the following recommended settings on a SPA3102. Not sure how the following would translate to the OBi ATA:
Quote
Here's a more general set of steps to properly set up a PAP2/SPAxxxx type ATA behind a NAT router, that should work under just about any conditions.
Browse to the ATA's advanced, admin level web configuration. Under the SIP tab:
1) Record the port number specified by RTP Port Min.
2) Record the port number specified by RTP Port Max.
3) Set Handle VIA received to yes.
4) Set Handle VIA rport to yes.
5) Set Insert VIA received to yes.
6) Set Insert VIA rport to yes.
7) Set Substitute VIA Addr to yes.
8 ) Set Resp to Src Port to yes.
9) Set STUN Enable to yes.
10) Set STUN Server to your choice for STUN server, eg "stun.voxalot.com".
11) Set Ext RTP Port Min to match the value recorded in step 1). May be omitted depending on router's NAT implementation.
Under the Line 1/2 tab:
12) Set NAT Mapping Enable to yes.
13) Optionally, set NAT Keep Alive Enable to yes. Isn't really necessary with ports forwarded.
14) Make a note of the value of field SIP Port.
15) Set Ext SIP Port to the value from step 14). May be omitted depending on router's NAT implementation.
16) Set Ans Call Without Reg to yes.
In your router's setup:
17) Forward the port number from step 14) for UDP, from your router to the ATA.
18) Forward the range of port numbers defined by the values from steps 1) and 2) for UDP, from your router to the ATA.
Finally, in G5's setup, make sure that the SIP forwarding goes to the same port number as recorded in step 14).
Navigation
[0] Message Index
[#] Next page