Hi!
We set a system like this
OXO <<==vpn==>> GXW4008 (it´s a Grandstream Voice Gateway with 8 FXS port)
At OXO ARS it show like ALIVE and I can acess the either side of the VPN without restriction.
When I try to make calls from GXW to OXO, it does not works, it give a busy tone.
Then, I just make one call from OXO to GXW, this call works perfectly, and after it I can make calls from GXW to OXO.
It look like a time out between OXO and GXW, because it still working for a period of time, and after a time, it stops, then it´s necessary to make a new call from OXO to GXW to "reactivate" the communication.
The connection is made peer-to-peer, a SIP trunk connection, it´s not a SIP user.
Some one experience this before?
Time out between OXO and GXW4008 Grandstream
Re: Time out between OXO and GXW4008 Grandstream
hi, at first glance it looks like the issue is in the gateway. as you can always make calls from the oxo that means the oxo is not loosing connection (sip options /imcp) keep alive is working. in the gateway do you register or what type of timeout is it using?
Best Regards
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data
-
MRFischer
Re: Time out between OXO and GXW4008 Grandstream
Hi!
At gateway I had set to 300 seconds.
But, i´m nothing using REGISTER it´s a trunk connection with out register.
At OXO I set a Secondary Trunk Group to ARS and set de Gateway IP.
At Gateway I set de OXO IP and the user, without password, and set to make calls without register.
Suppose to be simple like this.
At gateway I had set to 300 seconds.
But, i´m nothing using REGISTER it´s a trunk connection with out register.
At OXO I set a Secondary Trunk Group to ARS and set de Gateway IP.
At Gateway I set de OXO IP and the user, without password, and set to make calls without register.
Suppose to be simple like this.
Re: Time out between OXO and GXW4008 Grandstream
two things i can think of although i do not know the device at all.
1: when unit fails, reboot the ATA then try to make a call.
2: use register from the ATA to the oxo then the connection should stay alive.
another thing I see on the unit it can send keep alives for nat firewalls maybe turn this on and see if it helps.
1: when unit fails, reboot the ATA then try to make a call.
2: use register from the ATA to the oxo then the connection should stay alive.
another thing I see on the unit it can send keep alives for nat firewalls maybe turn this on and see if it helps.
Best Regards
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data
-
GrandstreamSupport
Re: Time out between OXO and GXW4008 Grandstream
Hi,
I am from Grandstream Technique Support team. Happy New Year.
Regarding your problem, it seems that on your gateway to OXO path there is a NAT that closes the SIP ports going outbound. Keep your previous settings and here is my suggestions:
Go to web interface of gateway and profile set NAT Traversal (STUN): to No, but send keep alive, that will keep the ports alive. Configure and reboot Or you can open the ports by setting on your router.
Please let me know if it helps.
Best
I am from Grandstream Technique Support team. Happy New Year.
Regarding your problem, it seems that on your gateway to OXO path there is a NAT that closes the SIP ports going outbound. Keep your previous settings and here is my suggestions:
Go to web interface of gateway and profile set NAT Traversal (STUN): to No, but send keep alive, that will keep the ports alive. Configure and reboot Or you can open the ports by setting on your router.
Please let me know if it helps.
Best
-
MRFischer
Re: Time out between OXO and GXW4008 Grandstream
Hi!
That´s do good to know that there is a GrandStream Support over here!
Thanks for your presence.
Well, actually I did both:
- set the NAT Traversal (STUN): to No, but send keep alive
and
- set the Session Expiration to 900 (in seconds. default 180 seconds)
At this moment, it look to be working great.
Thank you
That´s do good to know that there is a GrandStream Support over here!
Thanks for your presence.
Well, actually I did both:
- set the NAT Traversal (STUN): to No, but send keep alive
and
- set the Session Expiration to 900 (in seconds. default 180 seconds)
At this moment, it look to be working great.
Thank you

