|Anonymous | Login | Signup for a new account||2017-09-20 09:22 CEST|
|My View | View Issues | Change Log | Roadmap | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000021||easycwmp||[All Projects] Question||public||2014-10-31 10:33||2014-11-05 09:00|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0000021: Work with genie acs and easycwmp|
|Description||Hello , i am working on implementation of tr069 acs, but i had a problem in remote access from connecting different router/gateway ,and i don't want to do port mapping. I implemented genie acs and i see my all parameters but i can't connect it from different router. I wonder can i implement genie acs for server side and easy cwmp for client side,is this work ? If so how can i do? May you help me on this issue ?|
|Tags||No tags attached.|
Yes, you can use EasyCwmp with genie acs.
concerning the install of easycwmp on your router, it depends of the linux system installed on your router.
Please refer to the install page (http://www.easycwmp.org/index.php/manual [^]) and follow the steps related to your linux system.
|Do i have to set up easycwmp in EVERY modem to connect devices?Also in this link i couldn't find the set up of easycwmp for modem ?|
If you have a device with easycwmp installed, and the device is behind a modem (with NAT configured), then you can not do a connection request from the ACS to the device. Because easycwmp doesn't support yet XMPP neither STUN.
The TR069 standard propose one of these protocols (XMPP or STUN) as a solution to make a connection request from an ACS to a device behind a NAT
|Thank you very much, i understand it.Can you help me is it necessary to genie acs have stun server support for remote access?Also for remote access i want to use udp, should i make a change in server, for requests coming from udp? At the end how will i know requests coming from udp ?|
You have to look at genie acs wiki to know the stun server used with genie acs.
According to TR069 standard, the procedures for making use of STUN to allow the use of UDP Connection Requests to a CPE are summarized as follows:
*The ACS enables the use of STUN in the CPE (if it is not already enabled by
factory default) and designates the STUN server for the CPE to use.
*The CPE uses STUN to determine whether or not the CPE is behind a NAT
Gateway with a private allocated address.
*If the CPE is behind a NAT Gateway with a private allocated address, the CPE
uses the procedures defined in STUN to discover the binding timeout.
*The CPE sends periodic STUN Binding Requests at a sufficient frequency to keep
alive the NAT binding on which it listens for UDP Connection Requests.
*When the CPE determines the public IP address and port for the NAT binding on
which it is listening for UDP Connection Requests, and whenever it subsequently
changes, the CPE communicates this information to the ACS. Two means are
provided by which the ACS, at its discretion, can obtain this information—either
from information provided in the STUN Binding Request messages themselves,
or via Notification on changes to the UDPConnectionRequestAddress Parameter,
which the CPE will update to include the public Connection Request address and
*Whenever the ACS wishes to establish a connection to the CPE, it can send a
UDP Connection Request to the CPE. To accommodate the broadest class
of NAT Gateways, this will be sent from the same source address and port as the
|2014-10-31 10:33||saleh||New Issue|
|2014-10-31 11:14||Anis||Note Added: 0000104|
|2014-10-31 11:14||Anis||Category||General => Question|
|2014-10-31 12:28||saleh||Note Added: 0000105|
|2014-10-31 14:56||Anis||Note Added: 0000106|
|2014-11-03 13:31||saleh||Note Added: 0000107|
|2014-11-03 14:53||Anis||Note Added: 0000108|
|2014-11-05 09:00||Anis||Status||new => resolved|
|2014-11-05 09:00||Anis||Resolution||open => fixed|
|2014-11-05 09:00||Anis||Assigned To||=> Anis|
|Copyright © 2000 - 2017 MantisBT Team|