help with remote connections

[SY]

leegor,
PBX does not rely on information provided by the remote phone in SIP message headers and SDP content. In general, it does not matter what is specified there in case if ALLOWSOURCEASOUTBOUND=1 and you use latest updates v10.
If PBX can get correct information about source IP/port of SIP messages and RTP packets then everything will work.
The reality is that some "NAT/Firewalls" are hiding or corrupting this information. For example, Kerio requires additional tuning.
Without verbose logs of problematic call there is nothing to suggest because too many variables are unknown...

 

[albertc]

Why should I have stun enabled? I have a static ip and ports are mapped.
Also, why would I have more function (atleast sound on one end) with stun turned off than with it on?

I can't run the checker because of this error
"Error opening 3CXFWChecker.dll Please check the bin folder."

There are too many unknown here. To successfully troubleshoot these issues. Firewall checker result, Current firewall setting and verbose logs are needed. As SY said, some NAT/Firewalls can be the cause of the problem. And since you have two location to deal with, you have two NAT devices and the problem can be on either side. Give us as much information as possible and see if we can help.

There are some tips out there on the internet about how to resolve 3CXFWChecker.dll error.

 

[ZenMasta]

Until I can resolve the firewall checker error I wont be able to provide that.

I will make some calls and inspect the servers firewall log when I get home. I'll also see if there is any difference with stun enabled on the hardphone.

 

[ZenMasta]

If I enable stun on the phone, I'm worse off... same as if I had it enabled on the server.

If I use the sip proxy manager, It will appear registered, but as soon as I lift the handset off the cradle the lights turn orange and the screen eventually says failed or no response.

So back to not using the proxy here is my 3cx log after restarting the system

Event Log:
Extension 104 is registered, contact: sip:[email protected]:5060 (my phone at home)
Extension 101 is registered, contact: sip:[email protected]:5060 (my office desk phone)

Activity Log:
10:54:59.901 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:[email protected]:5060/101]
10:50:49.580 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:[email protected]:5060/104]

 

[leejor]

Extension 104 is registered, contact: sip:104@192.168.1.101:5060 (my phone at home)

If ext 104, your phone at home, is registering this way, not using the Proxy manager and not using STUN, then is appears that 3CX thinks it has a private IP, and will therefore not be able to contact it.

What version of 3CX are you using?

Did you go over this article http://www.3cx.com/blog/voip-howto/remote-extensions/ , paying particular attention to the "Working Around the Issue" section?

 

[ZenMasta]

3CX Version 10.0.19547.1805 SP.1.1

then is appears that 3CX thinks it has a private IP, and will therefore not be able to contact it

I don't understand this because isn't the fact that it's registering indicating that 3cx found it?

As I explained in the first half of my post, I was even worse off using proxy manager because it might register but as soon as I lifted the handset it would fail/no response (on the lcd) and I couldn't get dial tone or dial out etc.

I followed the config instructions in the guide exactly and again this far have had the best success without stun enabled (server and client side)

So, as I was typing this. I thought I would give the proxy manager another try... Since I'm not at home I can't test the call to see if there is any audio since obviously I am not there to listen, but I can at least paste some log action. I restarted 3cx and once it was back up I started the proxy manager.

Softphone is using built in 3cx tunnel service not the proxy manager. I'm only using the proxy manager for the cisco phone.
When I get home I'll see what happens when I try to use the phone to make/receive calls etc.

Event Log:
Extension 104 is registered, contact: sip:[email protected]:5060 (hardphone at home)
Extension 111 is registered, contact: sip:[email protected]:63436;rinstance=96cbf60d6e3c6d12 (3cx phone at home)

Activity Log:
13:39:22.379 [CM504001]: Ext.104: new contact is registered. Contact(s): [sip:[email protected]:5060/104]
13:45:59.537 [CM504001]: Ext.111: new contact is registered. Contact(s): [sip:[email protected]:63436;rinstance=96cbf60d6e3c6d12/111]



I'm not sure how to read the proxy log but I'm sure the main thing to takeawya from is is "(Trace5):Not valid Route: sip:192.168.1.105:5080"

Proxy Log:

.\main.cpp(165) : {2012/03/23 >>
13:40:44.666}(Log2):
----------------------------------------- STARTING TUNNEL -------------------------------------------------
.\main.cpp(166) : {13:40:44.666}(Log2):Version: 9.0.23258.0
.\main.cpp(172) : {13:40:44.669}(Trace5):Loading settings from C:\ProgramData\3CX\Bin\3CXTunnel.ini
.\ConnMgr.cpp(15) : {13:40:44.674}(Log2):-- Initializing Connaction Manager
.\ConnMgr.cpp(42) : {13:40:44.682}(Log2):-- Master UDP channel initialized
.\ConnMgr.cpp(48) : {13:40:44.682}(Log2):-- Tunnel is prepared to listen for incoming TCP connections on 192.168.1.105:5090
.\Bridge.cpp(34) : {13:40:44.682}(Log2):Initializing Tunnel 'TunnelClient'(123456)
.\Tunnel.cpp(23) : {13:40:44.686}(Log2):** Starting outgoing tunnel connection TunnelClient; id=123456
.\Tunnel.cpp(24) : {13:40:44.686}(Log2):** Connects to **SERVER_IP**:5090
.\Bridge.cpp(73) : {13:40:44.687}(Trace5):Creating SIP stack(s) for Tunnel 'TunnelClient'(123456)
.\Tunnel.cpp(125) : {13:40:44.687}(Log2):Started thread [8200] for connection TunnelClient at **SERVER_IP**:5090
.\Stack.cpp(339) : {13:40:44.688}(Trace5):Iface info read: idx=a; ip=192.168.1.105; mask=0xffffff00
.\Stack.cpp(339) : {13:40:44.688}(Trace5):Iface info read: idx=14; ip=192.168.56.1; mask=0xffffff00
.\Stack.cpp(339) : {13:40:44.688}(Trace5):Iface info read: idx=1; ip=127.0.0.1; mask=0xff000000
.\Bridge.cpp(90) : {13:40:45.172}(Log2):Tunnel is receiving local SIP packets on the SipProxyPort 5080
.\Stack.cpp(63) : {13:40:45.173}(Log2):++ Starting SIP stack thread (3CXSIPProxy)
.\ConnMgr.cpp(240) : {13:40:45.173}(Log2):-- Starting Connections Manager's thread
.\ConnMgr.cpp(258) : {13:40:45.173}(Log2):Tunnel is now listening for incoming TCP connections on 192.168.1.105:5090
.\Bridge.cpp(188) : {13:40:45.173}(Log2):Connecting tunnel 'TunnelClient'(123456) to **SERVER_IP**:5090
.\TCPSide.cpp(32) : {13:40:45.174}(Trace5):Connecting to **SERVER_IP**:5090
.\Stack.cpp(102) : {13:40:45.184}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  NOTIFY 192.168.1.105:5080 tid=-49094fd7 cseq=NOTIFY [email protected]:5060 / 113 from(wire)
.\Stack.cpp(115) : {13:40:45.184}(Critical0):Tunnel is not connected, replying to stack with 'Not Connected'
.\TCPSide.cpp(43) : {13:40:45.210}(Trace5):Attempt to connect to **SERVER_IP**:5090 has succeeded
.\TCPSide.cpp(50) : {13:40:45.210}(Log2):UDP socket address 192.168.1.105:57110
.\TCPSide.cpp(55) : {13:40:45.210}(Log2):Slave UDP channel initialized
.\TCPSide.cpp(105) : {13:40:45.212}(Log2):Connection created (slave side) on socket 308; num.conn=1
.\Bridge.cpp(193) : {13:40:45.212}(Log2):Sent authentication to tunnel TunnelClient at **SERVER_IP**:5090; rnd=3
.\TCPSide.cpp(148) : {13:40:45.488}(Trace5):Authentication info update:**WANIP@HOME**:57110$3 UDP channel is stopped until authentication on **SERVER_IP**:5090
.\TCPSide.cpp(158) : {13:40:45.569}(Log2):Send reliable confirmation to master. Slave UDP channel is activated
.\Stack.cpp(102) : {13:41:00.205}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  NOTIFY 192.168.1.105:5080 tid=-28534696 cseq=NOTIFY [email protected]:5060 / 114 from(wire)
.\Stack.cpp(215) : {13:41:00.205}(Critical0):RL is of tunnel, but Route doesn't exists
.\Bridge.cpp(305) : {13:41:00.205}(Trace5):Processing SIP message (tid=-28534696) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:41:00.205}(Trace5):Preprocessing local SIP request: NOTIFY, tid=-28534696
.\Bridge.cpp(828) : {13:41:00.206}(Trace5):Not valid Route: sip:192.168.1.105:5080
.\Bridge.cpp(836) : {13:41:00.206}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:41:00.206}(Trace5):Process local request: NOTIFY
.\Bridge.cpp(366) : {13:41:00.207}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-28534696)
.\Stack.cpp(102) : {13:41:08.695}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **SERVER_IP**:5060 tid=-61686eaa cseq=REGISTER [email protected]:5060 / 65089 from(wire)
.\Bridge.cpp(305) : {13:41:08.695}(Trace5):Processing SIP message (tid=-61686eaa) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:41:08.696}(Trace5):Preprocessing local SIP request: REGISTER, tid=-61686eaa
.\Bridge.cpp(836) : {13:41:08.696}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:41:08.696}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {13:41:08.696}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-61686eaa)
.\TCPSide.cpp(158) : {13:41:14.533}(Log2):Send reliable confirmation to master. Slave UDP channel is activated
.\Stack.cpp(102) : {13:41:16.216}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **SERVER_IP**:5060 tid=-8ecabfa7 cseq=REGISTER [email protected]:5060 / 65090 from(wire)
.\Bridge.cpp(305) : {13:41:16.216}(Trace5):Processing SIP message (tid=-8ecabfa7) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:41:16.216}(Trace5):Preprocessing local SIP request: REGISTER, tid=-8ecabfa7
.\Bridge.cpp(836) : {13:41:16.217}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:41:16.217}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {13:41:16.217}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-8ecabfa7)
.\Stack.cpp(102) : {13:41:31.205}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  NOTIFY 192.168.1.105:5080 tid=-ae946998 cseq=NOTIFY [email protected]:5060 / 116 from(wire)
.\Stack.cpp(215) : {13:41:31.205}(Critical0):RL is of tunnel, but Route doesn't exists
.\Bridge.cpp(305) : {13:41:31.206}(Trace5):Processing SIP message (tid=-ae946998) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:41:31.206}(Trace5):Preprocessing local SIP request: NOTIFY, tid=-ae946998
.\Bridge.cpp(828) : {13:41:31.207}(Trace5):Not valid Route: sip:192.168.1.105:5080
.\Bridge.cpp(836) : {13:41:31.207}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:41:31.207}(Trace5):Process local request: NOTIFY
.\Bridge.cpp(366) : {13:41:31.207}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-ae946998)
.\Bridge.cpp(419) : {13:41:32.617}(Trace5):Got SIP msg
    brief=SipResp: 408 tid=-28534696 cseq=NOTIFY / 114 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:41:32.618}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:41:32.618}(Trace5):Process tunnel response: 408 Request Timeout / NOTIFY
.\Stack.cpp(162) : {13:41:32.618}(Trace5):Sending to stack(5080);
  brief=SipResp: 408 tid=-28534696 cseq=NOTIFY / 114 from(tu)
.\Bridge.cpp(419) : {13:41:41.222}(Trace5):Got SIP msg
    brief=SipResp: 408 tid=-61686eaa cseq=REGISTER / 65089 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:41:41.223}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:41:41.223}(Trace5):Process tunnel response: 408 Request Timeout / REGISTER
.\Stack.cpp(162) : {13:41:41.223}(Trace5):Sending to stack(5080);
  brief=SipResp: 408 tid=-61686eaa cseq=REGISTER / 65089 from(tu)
.\TCPSide.cpp(158) : {13:41:43.560}(Log2):Send reliable confirmation to master. Slave UDP channel is activated
.\Stack.cpp(102) : {13:41:47.216}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **SERVER_IP**:5060 tid=-77827edd cseq=REGISTER [email protected]:5060 / 65092 from(wire)
.\Bridge.cpp(305) : {13:41:47.217}(Trace5):Processing SIP message (tid=-77827edd) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:41:47.217}(Trace5):Preprocessing local SIP request: REGISTER, tid=-77827edd
.\Bridge.cpp(836) : {13:41:47.217}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:41:47.217}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {13:41:47.217}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-77827edd)
.\Bridge.cpp(419) : {13:41:47.981}(Trace5):Got SIP msg
    brief=SipResp: 407 tid=-77827edd cseq=REGISTER / 65092 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:41:47.982}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:41:47.982}(Trace5):Process tunnel response: 407 Proxy Authentication Required / REGISTER
.\Stack.cpp(162) : {13:41:47.982}(Trace5):Sending to stack(5080);
  brief=SipResp: 407 tid=-77827edd cseq=REGISTER / 65092 from(tu)
.\Stack.cpp(102) : {13:41:48.017}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **SERVER_IP**:5060 tid=-ae75ac42 cseq=REGISTER [email protected]:5060 / 65093 from(wire)
.\Bridge.cpp(305) : {13:41:48.017}(Trace5):Processing SIP message (tid=-ae75ac42) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:41:48.017}(Trace5):Preprocessing local SIP request: REGISTER, tid=-ae75ac42
.\Bridge.cpp(836) : {13:41:48.018}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:41:48.018}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {13:41:48.018}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-ae75ac42)
.\Bridge.cpp(419) : {13:41:48.742}(Trace5):Got SIP msg
    brief=SipResp: 408 tid=-8ecabfa7 cseq=REGISTER / 65090 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:41:48.743}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:41:48.743}(Trace5):Process tunnel response: 408 Request Timeout / REGISTER
.\Stack.cpp(162) : {13:41:48.743}(Trace5):Sending to stack(5080);
  brief=SipResp: 408 tid=-8ecabfa7 cseq=REGISTER / 65090 from(tu)
.\Bridge.cpp(419) : {13:41:48.743}(Trace5):Got SIP msg
    brief=SipResp: 200 tid=-ae75ac42 cseq=REGISTER [email protected]:5060 / 65093 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:41:48.743}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:41:48.744}(Trace5):Process tunnel response: 200 OK / REGISTER
.\Stack.cpp(162) : {13:41:48.744}(Trace5):Sending to stack(5080);
  brief=SipResp: 200 tid=-ae75ac42 cseq=REGISTER [email protected]:5060 / 65093 from(tu)
.\Bridge.cpp(419) : {13:41:48.989}(Trace5):Got SIP msg
    brief=SipReq:  NOTIFY [email protected]:5060 tid=da7df443b4751a47 cseq=NOTIFY [email protected]:5060 / 1 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:41:48.989}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(721) : {13:41:48.989}(Trace5):Process tunnel request: NOTIFY
.\Stack.cpp(162) : {13:41:48.990}(Trace5):Sending to stack(5080);
  brief=SipReq:  NOTIFY [email protected]:5060 tid=da7df443b4751a47 cseq=NOTIFY [email protected]:5060 / 1 from(tu)
.\Stack.cpp(102) : {13:41:49.021}(Trace5):Received from local SIP stack(5080):
  brief=SipResp: 200 tid=da7df443b4751a47 cseq=NOTIFY / 1 from(wire)
.\Bridge.cpp(305) : {13:41:49.021}(Trace5):Processing SIP message (tid=da7df443b4751a47) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(668) : {13:41:49.021}(Trace5):Process local response: 200 OK / NOTIFY
.\Bridge.cpp(366) : {13:41:49.022}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=da7df443b4751a47)
.\Stack.cpp(102) : {13:42:02.205}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  NOTIFY 192.168.1.105:5080 tid=-ebeb79d5 cseq=NOTIFY [email protected]:5060 / 118 from(wire)
.\Stack.cpp(215) : {13:42:02.205}(Critical0):RL is of tunnel, but Route doesn't exists
.\Bridge.cpp(305) : {13:42:02.206}(Trace5):Processing SIP message (tid=-ebeb79d5) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:42:02.206}(Trace5):Preprocessing local SIP request: NOTIFY, tid=-ebeb79d5
.\Bridge.cpp(828) : {13:42:02.206}(Trace5):Not valid Route: sip:192.168.1.105:5080
.\Bridge.cpp(836) : {13:42:02.207}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:42:02.207}(Trace5):Process local request: NOTIFY
.\Bridge.cpp(366) : {13:42:02.207}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-ebeb79d5)
.\Bridge.cpp(419) : {13:42:03.732}(Trace5):Got SIP msg
    brief=SipResp: 408 tid=-ae946998 cseq=NOTIFY / 116 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:42:03.733}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:42:03.733}(Trace5):Process tunnel response: 408 Request Timeout / NOTIFY
.\Stack.cpp(162) : {13:42:03.733}(Trace5):Sending to stack(5080);
  brief=SipResp: 408 tid=-ae946998 cseq=NOTIFY / 116 from(tu)
.\TCPSide.cpp(158) : {13:42:12.562}(Log2):Send reliable confirmation to master. Slave UDP channel is activated
.\Stack.cpp(102) : {13:42:18.216}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **SERVER_IP**:5060 tid=-70a36c6a cseq=REGISTER [email protected]:5060 / 65094 from(wire)
.\Bridge.cpp(305) : {13:42:18.217}(Trace5):Processing SIP message (tid=-70a36c6a) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:42:18.217}(Trace5):Preprocessing local SIP request: REGISTER, tid=-70a36c6a
.\Bridge.cpp(836) : {13:42:18.217}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:42:18.217}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {13:42:18.218}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-70a36c6a)
.\Bridge.cpp(419) : {13:42:23.750}(Trace5):Got SIP msg
    brief=SipResp: 503 tid=-ebeb79d5 cseq=NOTIFY / 118 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:42:23.750}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:42:23.751}(Trace5):Process tunnel response: 503 Service Unavailable / NOTIFY
.\Stack.cpp(162) : {13:42:23.751}(Trace5):Sending to stack(5080);
  brief=SipResp: 503 tid=-ebeb79d5 cseq=NOTIFY / 118 from(tu)
.\Stack.cpp(102) : {13:42:33.206}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  NOTIFY 192.168.1.105:5080 tid=-c6883e9 cseq=NOTIFY [email protected]:5060 / 120 from(wire)
.\Stack.cpp(215) : {13:42:33.206}(Critical0):RL is of tunnel, but Route doesn't exists
.\Bridge.cpp(305) : {13:42:33.206}(Trace5):Processing SIP message (tid=-c6883e9) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:42:33.206}(Trace5):Preprocessing local SIP request: NOTIFY, tid=-c6883e9
.\Bridge.cpp(828) : {13:42:33.207}(Trace5):Not valid Route: sip:192.168.1.105:5080
.\Bridge.cpp(836) : {13:42:33.207}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:42:33.207}(Trace5):Process local request: NOTIFY
.\Bridge.cpp(366) : {13:42:33.207}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-c6883e9)
.\TCPSide.cpp(158) : {13:42:41.606}(Log2):Send reliable confirmation to master. Slave UDP channel is activated
.\Stack.cpp(102) : {13:42:49.217}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **SERVER_IP**:5060 tid=-426cc810 cseq=REGISTER [email protected]:5060 / 65096 from(wire)
.\Bridge.cpp(305) : {13:42:49.217}(Trace5):Processing SIP message (tid=-426cc810) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:42:49.217}(Trace5):Preprocessing local SIP request: REGISTER, tid=-426cc810
.\Bridge.cpp(836) : {13:42:49.218}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:42:49.218}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {13:42:49.218}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-426cc810)
.\Bridge.cpp(419) : {13:42:50.736}(Trace5):Got SIP msg
    brief=SipResp: 408 tid=-70a36c6a cseq=REGISTER / 65094 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:42:50.736}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:42:50.737}(Trace5):Process tunnel response: 408 Request Timeout / REGISTER
.\Stack.cpp(162) : {13:42:50.737}(Trace5):Sending to stack(5080);
  brief=SipResp: 408 tid=-70a36c6a cseq=REGISTER / 65094 from(tu)
.\Stack.cpp(102) : {13:43:04.206}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  NOTIFY 192.168.1.105:5080 tid=-1d7b7897 cseq=NOTIFY [email protected]:5060 / 122 from(wire)
.\Stack.cpp(215) : {13:43:04.206}(Critical0):RL is of tunnel, but Route doesn't exists
.\Bridge.cpp(305) : {13:43:04.207}(Trace5):Processing SIP message (tid=-1d7b7897) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:43:04.207}(Trace5):Preprocessing local SIP request: NOTIFY, tid=-1d7b7897
.\Bridge.cpp(828) : {13:43:04.208}(Trace5):Not valid Route: sip:192.168.1.105:5080
.\Bridge.cpp(836) : {13:43:04.208}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:43:04.208}(Trace5):Process local request: NOTIFY
.\Bridge.cpp(366) : {13:43:04.208}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-1d7b7897)
.\Bridge.cpp(419) : {13:43:05.719}(Trace5):Got SIP msg
    brief=SipResp: 408 tid=-c6883e9 cseq=NOTIFY / 120 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:43:05.720}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:43:05.720}(Trace5):Process tunnel response: 408 Request Timeout / NOTIFY
.\Stack.cpp(162) : {13:43:05.720}(Trace5):Sending to stack(5080);
  brief=SipResp: 408 tid=-c6883e9 cseq=NOTIFY / 120 from(tu)
.\TCPSide.cpp(158) : {13:43:10.656}(Log2):Send reliable confirmation to master. Slave UDP channel is activated
.\Stack.cpp(102) : {13:43:20.217}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **SERVER_IP**:5060 tid=-1f0c2bf6 cseq=REGISTER [email protected]:5060 / 65098 from(wire)
.\Bridge.cpp(305) : {13:43:20.218}(Trace5):Processing SIP message (tid=-1f0c2bf6) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:43:20.218}(Trace5):Preprocessing local SIP request: REGISTER, tid=-1f0c2bf6
.\Bridge.cpp(836) : {13:43:20.218}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:43:20.218}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {13:43:20.218}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-1f0c2bf6)
.\Bridge.cpp(419) : {13:43:21.026}(Trace5):Got SIP msg
    brief=SipResp: 407 tid=-1f0c2bf6 cseq=REGISTER / 65098 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:43:21.027}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:43:21.027}(Trace5):Process tunnel response: 407 Proxy Authentication Required / REGISTER
.\Stack.cpp(162) : {13:43:21.027}(Trace5):Sending to stack(5080);
  brief=SipResp: 407 tid=-1f0c2bf6 cseq=REGISTER / 65098 from(tu)
.\Stack.cpp(102) : {13:43:21.068}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **SERVER_IP**:5060 tid=-9a3f2597 cseq=REGISTER [email protected]:5060 / 65099 from(wire)
.\Bridge.cpp(305) : {13:43:21.068}(Trace5):Processing SIP message (tid=-9a3f2597) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:43:21.068}(Trace5):Preprocessing local SIP request: REGISTER, tid=-9a3f2597
.\Bridge.cpp(836) : {13:43:21.069}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:43:21.069}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {13:43:21.069}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-9a3f2597)
.\Bridge.cpp(419) : {13:43:21.567}(Trace5):Got SIP msg
    brief=SipResp: 200 tid=-9a3f2597 cseq=REGISTER [email protected]:5060 / 65099 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:43:21.567}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:43:21.567}(Trace5):Process tunnel response: 200 OK / REGISTER
.\Stack.cpp(162) : {13:43:21.567}(Trace5):Sending to stack(5080);
  brief=SipResp: 200 tid=-9a3f2597 cseq=REGISTER [email protected]:5060 / 65099 from(tu)
.\Bridge.cpp(419) : {13:43:21.568}(Trace5):Got SIP msg
    brief=SipResp: 408 tid=-426cc810 cseq=REGISTER / 65096 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:43:21.568}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:43:21.569}(Trace5):Process tunnel response: 408 Request Timeout / REGISTER
.\Stack.cpp(162) : {13:43:21.569}(Trace5):Sending to stack(5080);
  brief=SipResp: 408 tid=-426cc810 cseq=REGISTER / 65096 from(tu)
.\Stack.cpp(102) : {13:43:35.207}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  NOTIFY 192.168.1.105:5080 tid=-1d81ecd8 cseq=NOTIFY [email protected]:5060 / 124 from(wire)
.\Stack.cpp(215) : {13:43:35.207}(Critical0):RL is of tunnel, but Route doesn't exists
.\Bridge.cpp(305) : {13:43:35.208}(Trace5):Processing SIP message (tid=-1d81ecd8) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:43:35.208}(Trace5):Preprocessing local SIP request: NOTIFY, tid=-1d81ecd8
.\Bridge.cpp(828) : {13:43:35.208}(Trace5):Not valid Route: sip:192.168.1.105:5080
.\Bridge.cpp(836) : {13:43:35.209}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:43:35.209}(Trace5):Process local request: NOTIFY
.\Bridge.cpp(366) : {13:43:35.209}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-1d81ecd8)
.\Bridge.cpp(419) : {13:43:36.739}(Trace5):Got SIP msg
    brief=SipResp: 408 tid=-1d7b7897 cseq=NOTIFY / 122 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:43:36.739}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:43:36.739}(Trace5):Process tunnel response: 408 Request Timeout / NOTIFY
.\Stack.cpp(162) : {13:43:36.739}(Trace5):Sending to stack(5080);
  brief=SipResp: 408 tid=-1d7b7897 cseq=NOTIFY / 122 from(tu)
.\TCPSide.cpp(158) : {13:43:39.643}(Log2):Send reliable confirmation to master. Slave UDP channel is activated
.\Stack.cpp(102) : {13:43:51.218}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **SERVER_IP**:5060 tid=-99c93575 cseq=REGISTER [email protected]:5060 / 65100 from(wire)
.\Bridge.cpp(305) : {13:43:51.219}(Trace5):Processing SIP message (tid=-99c93575) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:43:51.219}(Trace5):Preprocessing local SIP request: REGISTER, tid=-99c93575
.\Bridge.cpp(836) : {13:43:51.219}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:43:51.219}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {13:43:51.219}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-99c93575)
.\Bridge.cpp(419) : {13:43:56.621}(Trace5):Got SIP msg
    brief=SipResp: 503 tid=-1d81ecd8 cseq=NOTIFY / 124 from(tu)
    from tunnel's connection **SERVER_IP**:5090
.\Bridge.cpp(434) : {13:43:56.622}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {13:43:56.622}(Trace5):Process tunnel response: 503 Service Unavailable / NOTIFY
.\Stack.cpp(162) : {13:43:56.622}(Trace5):Sending to stack(5080);
  brief=SipResp: 503 tid=-1d81ecd8 cseq=NOTIFY / 124 from(tu)
.\Stack.cpp(102) : {13:44:06.208}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  NOTIFY 192.168.1.105:5080 tid=-5034faae cseq=NOTIFY [email protected]:5060 / 126 from(wire)
.\Stack.cpp(215) : {13:44:06.208}(Critical0):RL is of tunnel, but Route doesn't exists
.\Bridge.cpp(305) : {13:44:06.208}(Trace5):Processing SIP message (tid=-5034faae) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {13:44:06.208}(Trace5):Preprocessing local SIP request: NOTIFY, tid=-5034faae
.\Bridge.cpp(828) : {13:44:06.209}(Trace5):Not valid Route: sip:192.168.1.105:5080
.\Bridge.cpp(836) : {13:44:06.209}(Trace5):Outbound tunnel (**SERVER_IP**) is selected
.\Bridge.cpp(648) : {13:44:06.209}(Trace5):Process local request: NOTIFY
.\Bridge.cpp(366) : {13:44:06.209}(Trace5):Tunnel to **SERVER_IP**:5090 is selected for SIP message (tid=-5034faae)

 

[leejor]

I don't understand this because isn't the fact that it's registering indicating that 3cx found it?

Not really, it's like you phoning someone and telling then you are at the house next door, but in reality, you are at a pay phone in town.

3CX want to use the IP that the set registers with, as the way to contact the set. If it shows a private IP, then how does 3CX know where to go to make contact with it?

I think i left the link from the last post I made, I've stuck it in there now. the reason I asked about which version you are using is...some changes were made in Version 10 (that you could add manually in previous versions), read that article.

 

[ZenMasta]

Ok so its the phones responsibility to tell the server where it is... I followed the guide that was linked originally exactly and triple checked the allowed outbound is 1.

I don't know what would be required on my end so that it appears that its coming from my homes wan IP instead of a lan like ip.

 

[albertc]

The reason why i asked for your current firewall setting on the 3CX server location is because I have the exact same setup as you are. I have a 3CX hosting at location A and my Cisco SPA phone (not using SIP Proxy Mgr) at location B where I do not have a fix IP address. In the firewall at location A (where you have your 3CX server). The following ports should be forward to the 3CX server internal IP address.

TCP/UDP 5060
UDP 9000-9049
TCP 5000
TCP 5090 (Only IF you are going to use sip Proxy Mgr)

In the firewall at location B (where you have your cisco phone), you do not need to do any port forwarding. And when you use STUN on your Cisco phone, the stun service will find your public IP address at your home and your cisco phone will gives that information to the 3CX server so your 3CX server will know where to send you the sip signal when you have an incoming call and any other sip control function.

Double check your cisco phone setting with these information.

First, setup your cisco phone manually as if it is on the same network as your 3CX server.

http://www.3cx.com/sip-phones/ Updated link

Then, change the setting so it will work at the your home.

http://www.3cx.com/blog/voip-howto/remote-extensions/

I would prefer not to use SIP proxy Mgr at all since I do not want to have a computer being turn on 24/7 at home just so i can use the phone. Give this a try first and see what happen. Some steps may sounded silly but double checking everything will on troubleshooting the issue.

Good Luck.

 

[ZenMasta]

Just got home. Thought I would try to make a call while registered through proxy manager and here is the proxy manager log

I'm going to do a factory reset on the phone and attempt to set it up manually. I'll post back with the results. Again I'm certain the nat is all square on the server side.

Thanks to everyone chiming in so far, I appreciate it.

newOfferAddresses:
[192.168.1.101:16464,192.168.1.101:16465]
newOfferMediaPorts:
[10000]
registeredSockets:
[]
registeredAddresses:
[]
sockToData:
[]
localToSock:
[]

.\Bridge.cpp(366) : {16:15:42.726}(Trace5):Tunnel to **server_ip**:5090 is selected for SIP message (tid=-c59a02b5)
.\Stack.cpp(102) : {16:15:44.406}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  REGISTER **server_ip**:5060 tid=-222d06e2 cseq=REGISTER [email protected]:5060 / 65686 from(wire)
.\Bridge.cpp(305) : {16:15:44.406}(Trace5):Processing SIP message (tid=-222d06e2) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {16:15:44.406}(Trace5):Preprocessing local SIP request: REGISTER, tid=-222d06e2
.\Bridge.cpp(836) : {16:15:44.407}(Trace5):Outbound tunnel (**server_ip**) is selected
.\Bridge.cpp(648) : {16:15:44.407}(Trace5):Process local request: REGISTER
.\Bridge.cpp(366) : {16:15:44.407}(Trace5):Tunnel to **server_ip**:5090 is selected for SIP message (tid=-222d06e2)
.\Bridge.cpp(419) : {16:15:49.833}(Trace5):Got SIP msg
    brief=SipResp: 503 tid=-dbe61c20 cseq=NOTIFY / 712 from(tu)
    from tunnel's connection **server_ip**:5090
.\Bridge.cpp(434) : {16:15:49.833}(Trace5):Selected SIP stack on 192.168.1.105:5080
.\Bridge.cpp(750) : {16:15:49.833}(Trace5):Process tunnel response: 503 Service Unavailable / NOTIFY
.\Stack.cpp(162) : {16:15:49.833}(Trace5):Sending to stack(5080);
  brief=SipResp: 503 tid=-dbe61c20 cseq=NOTIFY / 712 from(tu)
.\Stack.cpp(102) : {16:15:59.395}(Trace5):Received from local SIP stack(5080):
  brief=SipReq:  NOTIFY 192.168.1.105:5080 tid=-5258f7ef cseq=NOTIFY [email protected]:5060 / 714 from(wire)
.\Stack.cpp(215) : {16:15:59.395}(Critical0):RL is of tunnel, but Route doesn't exists
.\Bridge.cpp(305) : {16:15:59.395}(Trace5):Processing SIP message (tid=-5258f7ef) from SIP stack 192.168.1.105:5080
.\Bridge.cpp(587) : {16:15:59.395}(Trace5):Preprocessing local SIP request: NOTIFY, tid=-5258f7ef
.\Bridge.cpp(828) : {16:15:59.395}(Trace5):Not valid Route: sip:192.168.1.105:5080
.\Bridge.cpp(836) : {16:15:59.396}(Trace5):Outbound tunnel (**server_ip**) is selected
.\Bridge.cpp(648) : {16:15:59.396}(Trace5):Process local request: NOTIFY
.\Bridge.cpp(366) : {16:15:59.396}(Trace5):Tunnel to **server_ip**:5090 is selected for SIP message (tid=-5258f7ef)
.\TCPSide.cpp(158) : {16:16:00.630}(Log2):Send reliable confirmation to master. Slave UDP channel is activated

 

[ZenMasta]

At this point though I feel like I've done the same stuff so many times its become a blur and I'm having a hard time remembering what was/wasn't working under which configs.

Okay... SOO I reset the phone and attempted to configure manually per
http://www.3cx.com/sip-phones/ Updated link and then
http://www.3cx.com/blog/voip-howto/remote-extensions/
no proxy manager involved.



The good:
1) The phone registers
2) the phone can be dialed by extension from other phones on the system (well I'm not at work to test with hardphones but softphones can dial it by extension)
3) there is 2 way audio on these calls
4) 3cx event log shows correct ip - Event Log: Extension 104 is registered, contact: sip:104@RemoteWanIP:5060

The bad:
1) when I make/receive a call to outside line (my cell phone) there is no audio on either end.
2) I noticed in the web admin of the phone it says "Current Time: 1/1/2003 12:01:22" would this cause any problems? Shouldn't 3cx provide the date and time?

Here is an Activity log

18:18:07.738  [MS105000] C:31.1: No RTP packets were received:remoteAddr=**RemoteWanIP**:16426,extAddr=0.0.0.0:0,localAddr=**ServerIP**:9008
18:18:06.995  [CM503008]: Call(31): Call is terminated
18:17:57.259  Currently active calls - 1: [31]
18:17:27.258  Currently active calls - 1: [31]
18:17:25.884  Session 5154 of leg C:31.1 is confirmed
18:17:25.597  [CM503007]: Call(31): Device joined: sip:[email protected]:5060;transport=udp
18:17:25.596  [CM503007]: Call(31): Device joined: sip:104@**RemoteWanIP**:5060
18:17:25.595  [MS210003] C:31.1:Answer provided. Connection(transcoding mode[unsecure]):**ServerIP**:9008(9009)
18:17:25.594  [MS210001] C:31.2:Answer received. RTP connection[unsecure]: 192.168.13.156:5004(5005)
18:17:25.593  Remote SDP is set for legC:31.2
18:17:21.772  [CM505002]: Gateway:[Grandstream GXW 4104] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4104 (HW 1.1, Ch:6) 1.3.4.13] PBX contact: [sip:[email protected]:5060]
18:17:21.772  [CM503002]: Call(31): Alerting sip:[email protected]:5060;transport=udp
18:17:19.122  [CM503025]: Call(31): Calling PSTNline:2542356@(Ln.10000@Grandstream GXW 4104)@[Dev:sip:[email protected]:5060;transport=udp]
18:17:19.122  [MS210002] C:31.2:Offer provided. Connection(transcoding mode): 192.168.13.144:7046(7047)
18:17:19.076  [CM503004]: Call(31): Route 1: PSTNline:2542356@(Ln.10000@Grandstream GXW 4104)@[Dev:sip:[email protected]:5060;transport=udp]
18:17:19.075  [MS210000] C:31.1:Offer received. RTP connection: **RemoteWanIP**:16426(16427)
18:17:19.075  [CM503010]: Making route(s) to <sip:92542356@**ServerIP**>
18:17:19.074  Remote SDP is set for legC:31.1
18:17:19.074  [CM505001]: Ext.104: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA504G-7.4.9c] PBX contact: [sip:104@**ServerIP**:5060]
18:17:19.074  [CM503001]: Call(31): Incoming call from Ext.104 to <sip:92542356@**ServerIP**>
18:17:19.069  [CM500002]: Info on incoming INVITE:
  INVITE sip:92542356@**ServerIP**:5060 SIP/2.0
  Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-cdc48904;rport=5060;received=**RemoteWanIP**
  Max-Forwards: 70
  Contact: "Robbie-Home"<sip:104@**RemoteWanIP**:5060>
  To: <sip:92542356@**ServerIP**>
  From: "Robbie-Home"<sip:104@**ServerIP**>;tag=196d10a49468d8e7o0
  Call-ID: [email protected]
  CSeq: 102 INVITE
  Expires: 240
  Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
  Proxy-Authorization: Digest username="104",realm="3CXPhoneSystem",nonce="414d535c057db19e59:e8eccd8829e6f09a185775783d81fd39",uri="sip:92542356@**ServerIP**:5060",algorithm=MD5,response="f9241dc77588d83eec5133ba8bd0bce2"
  Supported: replaces
  User-Agent: Cisco/SPA504G-7.4.9c
  Content-Length: 0
  
18:16:55.256  Currently active calls [none]

I think I'm going to have to bring another phone home with me so I can try to compare the provisioned config vs the bare minimum manual config.

 

[albertc]

If all function can be done between extensions without any issue, than the problem maybe somewhere else. Check the inbound and outbound rules for that extension. Check the codec that is being use on your phone G722 or G711u preferred (You can check the codec being use by going to the phone web admin under Ext 1). And for the time setting on the phone, go to the phone web admin. Under the System tab, enter the NTP address in Primary NTP server field. For a list of NTP servers, go to http://tf.nist.gov/tf-cgi/servers.cgi . Pick the one that is closest to you (Assuming you are in the US).

 

[ZenMasta]

I don't have any special ob rules. Codec is G711u

standard 7,11 digits use x gateway.

or dial 9 to use certain gateway and strip 1 digit.