Dan Actually I modified it so that both the deviceId and the requestEvent would be passed to my api. I added a second variable to the NOTIFICATION_URL so my code could take different actions for a PERIODIC inform or VALUE CHANGE inform that I may not want to do, on a BOOT. In the end it just gives me more flexibility, as opposed to doing the same actions for all the requestEvents that are included in the NOTIFICATION_TYPES.
Don Johnson Internal Developer / DBA Uniserve Communications Suite 330 - 333 Terminal Avenue, Vancouver, BC V6A 4C1 Phone: 604-996-8213 Email: [email protected]<mailto:[email protected]> www.uniserve.com<http://www.uniserve.com> [logo] This e-mail, and any attachments thereto, is intended for use by the addressee(s) named herein, and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please notify me by e-mail (by replying to this message), or by telephone (noted above), and permanently delete the original. Thank you. From: Users [mailto:[email protected]] On Behalf Of Dan Morphis Sent: December 4, 2015 11:54 AM To: Community support for GenieACS users <[email protected]> Subject: Re: Best way to autoconfigure routers and resist reset to factory defaults Not sure why you had to modify the fork. I bet you forgot the %s in NOTIFICATION_URL. %s is replaced with the device ID. Example: "http://my-site/Api/ACS/Event/%s<http://my-site/Api/ACS/Event/%25s>" Would get turned into: http://my-site/Api/ACS/Event/00236a-96318REF-SR360NA025%2D0005755 As to your issue with the CPE not finding the ACS, try using DHCP. In your dhcpd.conf file put this: # always send option 43 (0x2b) even if the client was too lame to ask for it option dhcp-parameter-request-list = concat(option dhcp-parameter-request-list,2b); # define the TR-069 server in the vendor-options option space tr069; option tr069.acs-server-url code 1 = text; vendor-option-space tr069; option tr069.acs-server-url "https://YOUR-ACS-URL:7548/";; On Fri, Dec 4, 2015 at 8:14 AM, Don Johnson <[email protected]<mailto:[email protected]>> wrote: I’m using Dan’s fork as well. I had to modify the message the GenieACS sends to include the event as well as the device_id as I wanted to do some different things for different events, and not need to set the login for all events. The GenieACS sends the message to our own API, and from there I can find the device in my inventory database, match it up with the service details in the services database, and then create a couple setPrameterValues Tasks for that device, with a connection request, that will update the login on the device. This is working well in my test environment so far, but I’m having problems with firmware not finding my ACS out of the box even with the ACS url built into the firmware. Not an issue with the ACS, or dan’s fork, just a headache with the modem. Don Johnson Internal Developer / DBA Uniserve Communications Suite 330 - 333 Terminal Avenue, Vancouver, BC V6A 4C1 Phone: 604-996-8213<tel:604-996-8213> Email: [email protected]<mailto:[email protected]> www.uniserve.com<http://www.uniserve.com> [logo] This e-mail, and any attachments thereto, is intended for use by the addressee(s) named herein, and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please notify me by e-mail (by replying to this message), or by telephone (noted above), and permanently delete the original. Thank you. From: Users [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Dan Morphis Sent: December 4, 2015 8:06 AM To: [email protected]<mailto:[email protected]>; Community support for GenieACS users <[email protected]<mailto:[email protected]>> Subject: Re: Best way to autoconfigure routers and resist reset to factory defaults I use my notification patch for genie. That sends events like BOOT and BOOTSTRAP (first boot from factory reset) to my server. There I figure out what needs to be done to the cpe. My fork is at github/akcoder/genieacs -dan On Dec 4, 2015, at 2:30 AM, Sergio Fernández <[email protected]<mailto:[email protected]>> wrote: Good Morning! I've been told that configuring presets in order to autoconfigure routers and resist a client's factory default action it's bad for GenieACS. So I want to change the way I'm doing it. So my question is: What is the best way so all the routers of my company accomplish these 2 things: 1) That when you connect the router to the ADSL or the WAN port it autoconfigures by itself 2) When the client performs a factory default, it autoconfigures by itself with its own PPPoE login I thank you in advance for all the advice given -- Nombre: Sergio Fernández Rubio Cargo: Ingeniero de Software y de Redes Departamento: TIC mail: [email protected]<mailto:[email protected]> ficina: 968 165 000 Página web: www.electronicamartinez.com<http://www.electronicamartinez.es> _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.genieacs.com/mailman/listinfo/users _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.genieacs.com/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.genieacs.com/mailman/listinfo/users
