Problem with outbound calls from remote phone using dyn.DNS.

[robhazes]

To summarize:

This call is made from remote extension 16 (PAP2) to remote extension 14 (3cx Softphone), with my.dyn.dns in the PAP2 proxy field. The call is rejected by 3cx.

13:46:30.640 [CM503008]: Call(336): Call is terminated
13:46:30.640 [CM502001]: Source info: From: "16"<sip:[email protected]>;tag=1c459c5460ea258301<sip:[email protected]>
13:46:30.640 [CM503013]: Call(336): Incoming call rejected, caller is unknown; msg=SipReq: INVITE [email protected] tid=-36a7ff9f cseq=INVITE [email protected]:49214 / 102 from(wire)
13:46:30.484 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 182.123.116.54:49214;branch=z9hG4bK-b92d2e7b;rport=49214
Max-Forwards: 70
Contact: "16"<sip:[email protected]:49214>
To: <sip:[email protected]>
From: "16"<sip:[email protected]>;tag=1c459c5460ea258301
Call-ID: [email protected]
CSeq: 101 INVITE
Expires: 240
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces
User-Agent: Linksys/PAP2T-5.1.6(LS)
Content-Length: 0
13:46:30.484 [CM302001]: Authorization system can not identify source of: SipReq: INVITE [email protected] tid=-b92d2e7b cseq=INVITE [email protected]:49214 / 101 from(wire)
13:46:24.484 [CM504001]: Ext.16: new contact is registered. Contact(s): [sip:[email protected]:49214/16]

-----------------------
This exact same call is made from remote extension 16 (PAP2) to remote extension 14 (3cx Softphone), as above, with 182.123.116.54 in the PAP2 proxy field. The call is accepted by 3cx. My.dyn.dns points to 182.123.116.54.

13:48:43.437 [CM503008]: Call(337): Call is terminated
13:48:41.078 [CM505001]: Ext.14: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10858.0] Transport: [sip:10.0.0.10:5060]
13:48:41.078 [CM503002]: Call(337): Alerting sip:[email protected]:64768;rinstance=e5c90ed7fc3530b2
13:48:40.781 [CM503024]: Call(337): Calling Shared:Ext.14@[Dev:sip:[email protected]:64768;rinstance=e5c90ed7fc3530b2]
13:48:40.765 [CM503024]: Call(337): Calling Shared:Ext.14@[Dev:sip:[email protected]:5061]
13:48:40.750 [CM503004]: Call(337): Route 1: Shared:Ext.14@[Dev:sip:[email protected]:5061, Dev:sip:[email protected]:64768;rinstance=e5c90ed7fc3530b2]
13:48:40.750 [CM503010]: Making route(s) to <sip:[email protected]>
13:48:40.734 [CM505001]: Ext.16: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/PAP2T-5.1.6(LS)] Transport: [sip:10.0.0.10:5060]
13:48:40.718 [CM503001]: Call(337): Incoming call from Ext.16 to <sip:[email protected]>


The only parameter I change is the Proxy field in the Line-page of the PAP2.

 

[leejor]

You didn't say if you put your DyNDNS into 3CX.
In the Advanced tab/Settings for Direct SIP Calls/ Local SIP domain, put in your dynamic address
See if 3CX will then recognize the incoming call as valid.
On my setup the incoming call is in exactly the same format as yours with the DynDNS info there.

 

[robhazes]

You didn't say if you put your DyNDNS into 3CX.
In the Advanced tab/Settings for Direct SIP Calls/ Local SIP domain, put in your dynamic address
See if 3CX will then recognize the incoming call as valid.

Yes! Great!

That was it, it works now!

Thanks a lot, really good to get it working. 8)

 

[leejor]

That wasn't the first option that came to mind as I had datafilled mine when I first set up 3CX and hadn't thought much about it since. The more i looked what the log was saying, that it didn't know how to react to a number@the DynDNS. The only way to correct that is to somewhere tell it that the DyNDNS is valid and that it is OK to route a call that includes that particular information and not an IP address per say.

 

[E Kafeman]

I had a very similar problem. Some phones was not allowed to make neither local or external calls but could receive calls.
Have been searching for a solution, for two weeks now. With help from your tip was the problem solved.
In my case was it enough to remove "sip." in local SIP domain and just keep the dyndns domain name.

Thanks!!

 

[kanshare]

Hi,

Try using other routers. I had problems with Linksys too.

Cant solve till today.

But use a TPlink, Dlink or Level One no problems what so ever. Much cheaper too with more reliability. They even have sip and streaming support if you choose the right one.

The only time you get the issue is when not enough bandwidth or if you associated it from another location to be used at your location. As the address would be for that location or modem.

 

[mhanson]

I just had this issue today.

Editing the domain in Advanced is required for anyone using a remote phone without a tunnel or proxy manager, and is registering TO a DNS entry rather than a Public IP.

The issue is source identification. If you are registering to your public IP, that IP is verified by your Stun settings (which will either determine your IP via the stun service or allow you to enter it manually).

When you are registering to a DNS entry for your public domain (I.e. phones.888voipstore.com) calls coming in remotely TO that address will be blocked by 3CX until you enter that address into your sip domain settings.