Calling Remote location from office

Status
Not open for further replies.
leejor said:
There are really only a few basic settings that need to be changed in a SIP device to place and receive calls. The server, user name, password, then, STUN settings if at a remote location. Many others, can, generally (of course all situations are different) be left at the defaults.

Since you can register and place calls, we'll assume that the server, user name and password are correct. You can try doing a factory reset and starting again, sometimes that will correct any inadvertent changes you've made that didn't seem important at the time.

I'm not familiar with the settings on that phone, but, get it to work, first, without STUN, on the 3CX LAN, if you decide to go the factory reset route. Then do a web search on how to implement STUN on that set. Others that have "gone before" may have some tips on what needs to be changed (or not changed) to get it to work.

You may just find that there was one setting that was incorrect.

I've just about tried everything now, reset phone to factory defaults and reconfigured, still won't work?
Phone works fine on the 3cx lan - just won't work from a remote location(when calling from office).

Maybe it's just these Yealink phones that are rubbish?
 
Configure the phone to use a VoIP Provider directily and test
 
davidbenwell said:
Configure the phone to use a VoIP Provider directily and test


We don't have a VoIP provider so i'm unable to test this?
 
ok, Do you know the firmware version for your phone? maybe upgrading the firmware may resolve the issue? just in case there is a bug in the current version
 
davidbenwell said:
ok, Do you know the firmware version for your phone? maybe upgrading the firmware may resolve the issue? just in case there is a bug in the current version

I've already tried that the lastest firmware for this phone is
Firmware Version 9.60.0.110
Hardware Version 7.0.0.1
 
I'm still unable to get this system fully working?

If i call the office from my mobile, then ring my home ext it rings but when i pick up the phone nothing happens and my mobile is still ringing, it's as if the system and not acknowledged the hardphone as been picked up?

Anyone got any ideas?
 
Somebody must have some idea on how I can fix this problem as I'm losing faith now.
 
Sometimes it hard to suggest a fix via the forums without actually looking at the system it self. Might be a good idea to contact a certified partner who will provide support remotely and check all the settings, run some tests and check the logs etc.

This I think will be the only way of you getting this resolved.
 
Martin,

I'm having the same problem and with a remote (non proxy) Yealink phone. I've got one phone each in two locations and both are having problems. I'm running the latest (June) firmware from Yealink.

My grandstream handytone 286 seems to be working OK for receiving calls, but not the Yealink 22P's.

I've set both phones up per the guide ( http://www.3cx.com/blog/voip-howto/remote-extensions/ ) and can make outgoing calls all day long. But when I try to receive a call from outside, no-go.

Very strange. If I find a solution I'll be sure to update the thread further.

-Sam
 
When using the 3CX softphone did you envolved 3CX tunnel or just 'out of the office' ?
Try setting 'PBX delivers audio' for this extension also (I didn't see it in the post above).
With sure Wireshark capture at your remote location will indicate what is the problem.

Regards
 
Sorry for late read and reply, don't get cahne to visit forum to often.

I have 1 question about you router, what flavour of 2830 do you have?

If it is the 2830V then you may have problems with IP phones on the inside receiving calls I have, but not had much time to play, I am just about to play with a port other than 5060 to by-pass the voip part of the router and go straight to the phone.

Regards
 
I had the same problem, Grandstream GXP 2020 on an external ext was registering but could not make calls, 403 not allowed to make call or Forbidden is using the 3CX Softphone.

After contacting the support team and providing all support information required they suggested i use the SIP Proxy manager but i said this was simply not acceptable as so many other PBX systems dont have a problem having external extensions.

Anyway so went away and done my own digging around. The solution for me was in the 3CX System:

Go to: Settings>Network>STUN Server tab and put a tick in "Turn off STUN Server", then put your public IP in the section "Public IP to specify in Contact and SDP". Once i dont this everything worked fine when i configured the phone as per this article: http://www.3cx.com/blog/voip-howto/remote-extensions/

Hope this helps.
 
Sorry if I'm jumping in late - but need to know if you have consulted this doc' which I have found to be a very useful reminder regarding configuration of remote extensions ...

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

There are some significant differences in settings between remote and local operation. What you have described sounds like you have the ports etc. open OK - but the 3CX just doesn't know where the phone is on the Internet (to put it simply). This means that there is something wrong with the process that creates the phone's local/public ID to put in registration packets - which normally implies the STUN process isn't doing what it should. I've sometimes had big problems getting to stun.3cx.com - so try pinging that address from your PC - if it's slow, or doesn't respond, use one of the others that does i.e. stun2.3cx.com or stun3.3cx.com.

Also - Draytek's are great routers, but can be a bit funny on the firewall if they are not worked constantly ... I've found that I need to reduce the registration timer on my phones down to around 120 seconds to keep the firewall ports open between the phone and the 3CX server. If the reg' timer is too long, the Draytek seems to close the firewall.

Best of luck
Graham Hill
 
This could be a problem caused by the Draytek V2830. We have used Drayteks for quite a while, but have often found them to be temperamental IF the registration time on the phone is too long i.e. if the phone doesn't register very regularly (& we set ours to register every 120 seconds!) the firewall in the router just seems to 'forget' about keeping the port open in the firewall for the phone.

As you say, outgoing call is great - 'cause you are opening the firewall and establishing the connect ... However, if a call tries to get in, the Draytek does its SPI thing and 'Intruder alert' blocks it off.

Try changing the registration timer on your T20 - which I think is the 'Subscribe period' on the Account's Advanced settings page. We had this problem with Cisco Linksys SPA phones, and reducing the reg' timer to keep the Draytek firewall tickled seem to do the trick!
 
Status
Not open for further replies.

Latest Posts

Members Online Now

Forum statistics

Threads
111,845
Messages
589,333
Members
164,681
Latest member
JV J