Draytek router with Ip01

ckleea

I found a possible solution to deal with sip connection problem in a network environment with Draytek router 2920 or 2930 and IP01. I understand there is always problems with this setup for sip client to connect to the IP01 despite one has open the port and done port redirection.

I figure our that in the draytek router, use port re-direction to direct an unused port (i.e. not UDP 5060) e.g. 15060 to the IP01 IP:5060. In this case, the IP01 does not need to change any port binding and allows internal client to connect via standard 5060 UDP port. For outside LAN or internet connection, the client has to use a different port (usually in a form of xxx.xxx.xxx.xxx:15060 to connect.

I try this with great success.

See if you need this as a workaround for draytek router.

CK

ckleea

I have no idea but the previous experience with asterisk severs and IP01 worked. Now I have two machines I can see if this can work or not.

As far as I know, it should be ok.

ckleea

The draytek router concerned is Vigor2930Vn

ckleea

回復 6# bubblestar

2930VN is a different issue. It has VOIP as well. I don't know why it needs to change to different port but I believe that the router has something set up to default all traffic of sip to its ports first.

You may recall others using draytek has similar problem in sip connection.

Anyway it helps to fix some problems and at the same time enhance security i.e. not using standard 5060 port for SIP.

ckleea

Can you post the link?

ckleea

Additional tricks for the set up
1. since IP01 is not a very powerful CPU, when you update the file via GUI, you need to wait for a while to allow the write to complete
2. Switchfin GUI though is better is still limited in handling the conf file. Please bear this in mind and try to use SSH or FTP within the lan for file editing. I.e. encourage to do it via APL not GUI
3. if after changes, not able to sip login, try to reboot the IP01 and your sip client. Very often, it caches the previous information.
4. always save copies of working conf and it allows you to restore the working conf when you encounter problem.
FYI, my sip.conf. is corrupt but working, it is a result of previous GUI write with duplicate settings. I try to trim down and remove duplicates, then it does not work. Don'r know why!!

ckleea

回復 15# bubblestar
You cannot see the trunk status if you set up under APL. You need to manually add the calling rules e.g.

[CallingRule_USCall]
exten => 01.,1, Dial(SIP/1${EXTEN:2}@gimzo5,,r)
exten =>01.,2, hangup

For cron job, you can create a file /persistent/etc/crontab

ckleea

回復 17# bubblestar

For iptables, create a file as /etc/iptables.rules

ckleea

回復 15# bubblestar


    Another interesting points for dialplan and outgoing rule:
with more complex set up, I suggest to print out dialing prefix for the sake of memory. It would be difficult to remember single especially if you work like having a multiple skype trunks, multiple voip services, multiple abbreviations for speed dials, etc

ckleea

回復 20# bubblestar

記住，IP01 processing power 有限，所以不要做太多 tasks.