DrayTek UK Users' Community Forum
Help, Advice and Solutions from DrayTek Users
Any ideas on this
- bradley porter
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 75
- Thank you received: 0
15 Nov 2010 16:05 #64873
by bradley porter
Kind regards,
Bradley Porter
Any ideas on this was created by bradley porter
Dear all,
I have a strange issue I am scratching my head over. I wonder if someone could offer any pointers.
I have a Siemen's A580i base and cordless handset connected to my Draytek 2820Vn router. (This is bypassing the internal VoIP settings and just using the Internet Connections).
I have had, for some time, VERY slow call set-up. When I press the green button after tapping in the number, it seems to struggle for up-to 30 seconds before it starts to ring. However, replace the Draytek with a Thompson or NetGear Router and the call set-up is blisteringly fast - as soon as you press the green button you are ringing. Each time, every time.
What on earth with the Draytek would cause the outgoing call set-up to be heavily delayed but a cheaper Thompson or NetGear dials out in seconds?
Brad
I have a strange issue I am scratching my head over. I wonder if someone could offer any pointers.
I have a Siemen's A580i base and cordless handset connected to my Draytek 2820Vn router. (This is bypassing the internal VoIP settings and just using the Internet Connections).
I have had, for some time, VERY slow call set-up. When I press the green button after tapping in the number, it seems to struggle for up-to 30 seconds before it starts to ring. However, replace the Draytek with a Thompson or NetGear Router and the call set-up is blisteringly fast - as soon as you press the green button you are ringing. Each time, every time.
What on earth with the Draytek would cause the outgoing call set-up to be heavily delayed but a cheaper Thompson or NetGear dials out in seconds?
Brad
Kind regards,
Bradley Porter
Please Log in or Create an account to join the conversation.
- acseuser
- Offline
- Junior Member
Less
More
- Posts: 24
- Thank you received: 0
19 Nov 2010 07:20 #64922
by acseuser
Replied by acseuser on topic Any ideas on this
don't know that particular device; is it just a normal PSTN telephone, plugged into one of the Phone1/2 sockets?
If so, then the delay is most likely due to the 2820 not switching into bypass properly; there's been a lot of posts here about that. Wonder if it's fixed/better in the new f/w version.
If so, then the delay is most likely due to the 2820 not switching into bypass properly; there's been a lot of posts here about that. Wonder if it's fixed/better in the new f/w version.
Please Log in or Create an account to join the conversation.
- bradley porter
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 75
- Thank you received: 0
19 Nov 2010 14:14 #64931
by bradley porter
Kind regards,
Bradley Porter
Replied by bradley porter on topic Any ideas on this
Nope, this is just a VoIP device which plug into one of the 100Mb Network ports on the Draytek via a CAT5 cable.
As much as the Siemens device is pretty poor, when used in the same fashion with the Netgear or Thompson Routers, the call set-up and ringing is instantaneous. To me, it just feels like the Draytek is struggling for some reason before finally letting the call get set-up.
I just cant work out what could cause the delay which is related to the Draytk router but not the Thompson or Netgear. The calls are certianly OK once established.
Any further ideas?
As much as the Siemens device is pretty poor, when used in the same fashion with the Netgear or Thompson Routers, the call set-up and ringing is instantaneous. To me, it just feels like the Draytek is struggling for some reason before finally letting the call get set-up.
I just cant work out what could cause the delay which is related to the Draytk router but not the Thompson or Netgear. The calls are certianly OK once established.
Any further ideas?
Kind regards,
Bradley Porter
Please Log in or Create an account to join the conversation.
- acseuser
- Offline
- Junior Member
Less
More
- Posts: 24
- Thank you received: 0
19 Nov 2010 14:26 #64932
by acseuser
Replied by acseuser on topic Any ideas on this
OK; sorry. I googled it after (1) replying and (2) drinking some coffee... then I was thinking straight-er.
I'm guessing here, but - perhaps the 2820 is allowing your outgoing SIP request, but trying to handle the incoming response. It then realises that it can't (VoIP undefined) and THEN hands it to NAT to pass to the ethernet interface/s.
Do you have any VoIP setup in the 2820? And I guess you don't have any port forwarding setup for the Siemens device?
Don't suppose you can run Wireshark? .. then look at the timestamps between data. That should show where the delays are occurring.
I'm guessing here, but - perhaps the 2820 is allowing your outgoing SIP request, but trying to handle the incoming response. It then realises that it can't (VoIP undefined) and THEN hands it to NAT to pass to the ethernet interface/s.
Do you have any VoIP setup in the 2820? And I guess you don't have any port forwarding setup for the Siemens device?
Don't suppose you can run Wireshark? .. then look at the timestamps between data. That should show where the delays are occurring.
Please Log in or Create an account to join the conversation.
- bradley porter
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 75
- Thank you received: 0
19 Nov 2010 14:37 #64933
by bradley porter
Kind regards,
Bradley Porter
Replied by bradley porter on topic Any ideas on this
I think you may be onto something there. For example, there has been occasions where I think the call has not connected BUT the other side have picked up. In short, the call has been 'set-up' and reached the destination BUT I cannot hear them. When this happens, I sometimes connect and hear them just in time to say 'hello' a second time.
So, maybe calls are getting set-up and (as you say) the router is not allowing the traffic back in for that device for a delayed period - until it hands it back over to the eth port. (This is still strange as my Grandstream GXP2020 is just connected in the same way and this never happens to that!).
With this new revelation in mind - what do you suppose the next thing I should check is?
So, maybe calls are getting set-up and (as you say) the router is not allowing the traffic back in for that device for a delayed period - until it hands it back over to the eth port. (This is still strange as my Grandstream GXP2020 is just connected in the same way and this never happens to that!).
With this new revelation in mind - what do you suppose the next thing I should check is?
Kind regards,
Bradley Porter
Please Log in or Create an account to join the conversation.
- acseuser
- Offline
- Junior Member
Less
More
- Posts: 24
- Thank you received: 0
20 Nov 2010 12:00 #64941
by acseuser
Replied by acseuser on topic Any ideas on this
.. it works for the Grandstream box?? oh, that's weird.
I would have thought it would be the same for both. Maybe there's a difference in SIP timer values used by the GS Vs Siemens unit.
The simple solution as you realised is to use another IP address (via WAN aliasing / address mapping), or NAT all the relevant ports...
I would have thought it would be the same for both. Maybe there's a difference in SIP timer values used by the GS Vs Siemens unit.
The simple solution as you realised is to use another IP address (via WAN aliasing / address mapping), or NAT all the relevant ports...
Please Log in or Create an account to join the conversation.
Moderators: Sami
Copyright © 2024 DrayTek