These phones are very competitively priced; and are perfect for anyone that needs reliable, basic calling functionality or needs a lot of phones either in one place or over a distributed set of large-facility locations.
However, you can be rest assured that they are manufactured to very high standards and have all the qualities you would expect in more expensive models.
With these two new phones you can utilise essential Unified Communications features without sacrificing the function and performance that is usually only available with more expensive IP phones!
Want a closer look? Watch the first P315 being unboxed in Europe! Contact us for how you too can get your hands on the P310 or P315 and for bulk pricing.
Installing FreeStats requires a good working knowledge of Asterisk and Freepbx. Documented here is the step by step process.
To install Asterisk FreeStats you need:
Enable writing queue logs to the MySQL database through ODBC . (more: Asterisk: queue _log in MySQL via unixODBC )
Set the username and password of the database in the Asterisk
Call Center Stats config.
Let's turn on the Asterisk queue log in the MySQL database
By default, queue statistics data is saved to the queue_log file.
Let's assign a MySQL database table for data storage - asteriskcdrdb.queuelog
CREATE TABLE IF NOT EXISTS asteriskcdrdb.queuelog (
id INT NOT NULL AUTO_INCREMENT,
time char (32) DEFAULT NULL,
callid char (64) DEFAULT NULL,
queuename char (64) DEFAULT NULL,
agent char (64) DEFAULT NULL,
event char (32) DEFAULT NULL,
data char (64) DEFAULT NULL,
data1 char (64) DEFAULT NULL,
data2 char (64) DEFAULT NULL,
data3 char (64) DEFAULT NULL,
data4 char (64) DEFAULT NULL,
data5 char (64) DEFAULT NULL,
PRIMARY KEY (id)
) ENGINE = MyISAM DEFAULT CHARSET = utf8;
CREATE TABLE IF NOT EXISTS agents_new (
id MEDIUMINT NOT NULL AUTO_INCREMENT,
agent char (64) DEFAULT NULL,
PRIMARY KEY (id)
) ENGINE = MyISAM DEFAULT CHARSET = utf8;
CREATE TABLE IF NOT EXISTS queues_new (
id MEDIUMINT NOT NULL AUTO_INCREMENT,
queuename char (64) DEFAULT NULL,
PRIMARY KEY (id)
) ENGINE = MyISAM DEFAULT CHARSET = utf8;
We have included in the download a file to do this for you. to install it just run the following command
mysql -ufreepbxuser -pSECRECT < ./freestats.sql
In the /etc/asterisk/asterisk.conf file , add to the options section:
[options]
queue_adaptive_realtime=yes
edit /etc/asterisk/logger_general_custom.conf
and add
queue_adaptive_realtime = yes
queue_log_to_file = yes
queue_log => odbc,asteriskcdrdb,queuelog
In the realtime configuration file /etc/asterisk/extconfig_custom.conf, we define the driver, family, and target table:
[settings]
queue_log => odbc,asteriskcdrdb,queuelog
; where asterisk is the db config, for example in /etc/asterisk/res_odbc_custom.conf
In freepbx the following are already set you just need to add the settings to /etc/asterisk/extconfig_custom.conf as above
If extconfig.conf does not exist, create it with the command:
touch /etc/asterisk/extconfig.conf
and set permissions:
chown asterisk. /etc/asterisk/extconfig.conf
/etc/asterisk/res_odbc_custom.conf
[asteriskcdrdb]
enabled => yes
dsn => asteriskcdrdb
username => dbuser
password => dbpass
pre-connect => yes
where is DSN , settings from file
/etc/odbc.ini
[asteriskcdrdb]
Description = MySQL connection to 'asteriskcdrdb' database
driver = MySQL
server = localhost
database = asteriskcdrdb
Port = 3306
Socket = /var/lib/mysql/mysql.sock
Apply configuration with
asterisk -rx 'core restart now'
NOTE 'core restart now' - drops all current calls
Check the connection of Asterisk with the database through odbc :
asterisk -rx 'odbc show'
ODBC DSN Settings
Name: asteriskcdrdb
DSN: MySQL-asteriskcdrdb
Number of active connections: 3 (out of 5)
Logging: Disabled
Now move freestats and set permissions:
mv freestats /var/www/html/
Asterisk FreeStats config
Edit the config.php file according to your data, where
$ DBServer - host (localhost)
$ DBUser - DB user.
$ DBPass - DB Password.
$ DBName - DB name.
$ DBTable - The name of the database table.
example:
$ DBServer = 'localhost' ;
$ DBUser = 'freepbxuser' ;
$ DBPass = 'STRONG_SECRET' ;
$ DBName = 'asteriskcdrdb' ;
$ DBTable = 'queuelog' ;
Open statistics in your favorite web browser:
http(s)://ip.address/freestats
To add agents and queues, click the appropriate buttons:
Sync :
The query will fetch the unique names of agents and queues and place them in the agents_new and queues_new tables .
In order for entities to appear , there must be at least one entry in the queuelog table about the incoming call to the queue.
In the future, if you have new agents or queues, simply synchronize the data to display statistics on them. Call data is saved regardless of synchronization, because the Asterisk queue logger is responsible for this.
FreePBX conversation recordings in the statistics interface
To display conversation records in statistics, copy the following context into the /etc/asterisk/extensions_override_freepbx.conf file.
The example shows the context [sub-record-check] of FreePBX Distro 14.
extensions_override_freepbx.conf
Or modify the context from your system in the same way by adding a custom queue event - REC .
exten = > recordcheck, n, Queuelog ( recordcheck, $ {UNIQUEID} , NONE, REC, $ {CALLFILENAME} )
You cannot edit the FreePBX context directly in the extensions_additional.conf file, but you can put the modified version in extensions_override_freepbx.conf
If you use Asterisk 'clean' , you can do the same in the context of calling the queue by adding instead of the ${CALLFILENAME} variable the name of the conversation recording file in accordance with the scheme you use.
Additional information about queue log and QueueLog () command.
Authorization through accounts FreePBX
To enable authorization with the password FreePBX, uncomment the following code in the config.php file and change the password freepbxpassword to the password of your installation. The password can be viewed in the /etc/asterisk/res_odbc_additional.conf file (for the latest freepbx versions).
Configure AMI and AJAM for Realtime module
The php-curl package must be installed.
The ajam_cookie file must be created in the root directory of the application:
touch ajam_cookie && chmod 777 ajam_cookie
Asterisk needs to have AJAM enabled /etc/asterisk/manager.conf
as below in freepbx go to advanced settings and set "Enable Static Content" to yes
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0
webenabled = yes
httptimeout = 60
create user AMI
[ajamuser]
secret = PASSWORD
deny = 0.0.0.0/0.0.0.0
permit = 127.0.0.1/255.255.255.0
read = system, agent, reporting
write = system, agent, reporting
and enable the built-in http server in
/etc/asterisk/http.conf
[general]
enabled = yes
enablestatic = yes
bindaddr = 0.0.0.0
bindport = 8088
prefix = asterisk
To test AJAM Interface is active
freepbx * CLI> http show status
HTTP Server Status:
Prefix: / asterisk
Server: Asterisk / 15.5.0
Server Enabled and Bound to 0.0.0.0:8088
HTTPS Server Enabled and Bound to [::]: 8089
Enabled URI's:
/ asterisk / httpstatus => Asterisk HTTP General Status
/ asterisk / amanager => HTML Manager Event Interface w / Digest authentication
/ asterisk / arawman => Raw HTTP Manager Event Interface w / Digest authentication
/ asterisk / manager => HTML Manager Event Interface
/ asterisk / rawman => Raw HTTP Manager Event Interface
/ asterisk / static / … => Asterisk HTTP Static Delivery
/ asterisk / amxml => XML Manager Event Interface w / Digest authentication
/ asterisk / mxml => XML Manager Event Interface
/ asterisk / ws => Asterisk HTTP WebSocket
Enabled Redirects:
None.
Finally, set the data to connect to AMI / AJAM in the application config.php file :
$ config [ 'urlraw' ] = 'http://127.0.0.1:8088/asterisk/rawman' ;
$ config [ 'admin' ] = 'ajamuser' ;
$ config [ 'secret' ] = 'PASSWORD' ;
$ config [ 'authtype' ] = 'plaintext' ;
$ config [ 'cookiefile' ] = null ;
$ config [ 'debug' ] = false ;
Some years ago we wrote a post on running macros on queue answer here. this was very useful for integration with backends, At the time we raised a feature request to get it added to Freepbx, But this never happened.
Now the variable QGOSUB is in the dialplan for freepbx queues, But still there is no way of setting this in a default freepbx installation and it requires a snip-it of custom dialplan that is called from freepbx by a ‘custom destination’ . For example at its simplest the dialplan to set it could be :-
This allows simple or more complicated routines to be run. For example sending an email on answer which was a request we had that caused us to revisit this.
[ians_routine]
exten = s,1,Set(origtime=${EPOCH})
exten = s,n,Noop(${CHANNEL})
exten = s,n,Set(Agent11=${CUT(CHANNEL,@,1)})
exten = s,n,Set(Agent12=${CUT(Agent11,/,2)})
exten = s,n,Noop(${Agent11} , ${Agent12} )
exten = s,n,Set(fulltime=${STRFTIME(${EPOCH},,%d%m%Y-%H:%M:%S)})
exten = s,n,system(echo "There has been a call , Callers Details: ${CALLERID(number)} , ${CRM_SOURCE} , Date and Time: ${fulltime} , Agent: ${Agent12} ,Timestamp: ${origtime} , Queue Number: ${QUEUENUM} " | mail -s "failed recall at ${fulltime}" email@address.com)
same = n,Return()
Step By step instructions for call transfer when using the Aastra 6753i with firmware 3.x.x and above.
Phone Idle screen.
Once a call is answered their number will show and an icon of a ‘off hook phone’ will also show
To transfer the call press your ‘Transfer key’. Another ‘line’ will show numbered 2 with a ‘ > ’ next to it.
Enter the number you want to dial and press ‘>‘ dial if the call isn’t immediately dialed.
To ‘Blind’ transfer the call press the Transfer Button again or put the Handset down. NOTE if you do this you will not be able to get the call back.
After pressing dial the Phone Icon will show ‘ringing’
To get the call back while it is ringing press the ‘ < ‘ button shown on the display next to ‘Cancel’. Then L1 in this example will flash and ‘call held’ will show on the display as below, you need to get the call back by pressing the Flashing Line Key.
If the call goes to Voicemail or the caller answers the display will show the ‘off hook’ icon against 2
If the Caller wants the call then Press the ‘Transfer key’ the Red ‘Hangup key’ or put the handset down and the call will be transferred to them. Do not press the ‘>‘ Drop button.
If they don’t want the call or it goes to voicemail and you want to get the caller back, Press the ‘ > ‘ Drop Button and that call will be dropped and as before ‘call held’ will show on the screen and you press the L1 button to get the caller Back
The SL750H PRO handset is the thinnest pro handset yet and has a large 2.4″ illuminated display with an intuitive, icon-based user interface. This handset delivers fantastic call clarity based on Gigaset’s patented HDSPTM audio quality. The SL750H allows users to easily control call and notification alerts with a choice of audio profiles to suit your business needs.
The SL750H PRO has been given a special coating that makes it resilient to scratches on the display, handset or keys. This coating also helps to protect it from disinfectants, making it an ideal choice for industrial and manufacturing companies, hospitals and similar environments.
This handset is fully compatible with both Gigaset N510IP PRO and N300IP singlecell solutions as well as the N720IP PRO multicell DECT solution.
Coronavirus: service updates and supplier information
03 APRIL 2020
Last updated: 17:00 5 June 2020
This page contains important updates from us and our suppliers that may affect our partners or customers during this unprecedented time. We’ve also included useful links and support information and a full breakdown of any service updates as we have them. This will continue to be updated at least once a day, so please check back here regularly.
Key points:
BT Openreach (who help us supply internet connectivity services) have advised that provision and repair of their services are now on a “best endeavours” basis only across the UK and will impact almost all connectivity products: DSL, Ethernet, FTTC, FTTP, FIBRE, PSTN, ISDN2, ISDN30, LLU and SMPF
Openreach will be assisting providers to bring forward certain WLR and MPF new line installs to an earlier date. They will be contacting customers directly to try to agree an earlier install date to complete the work on behalf of the Provider.
Priority restoration of services will only take place for organisations deemed “critical”, including NHS, pharmacies, utilities etc (full list below)
Ongoing repairs will continue for all, but with priority given to critical organisations and customers deemed “at risk” and you will now be asked if you are an “At Risk Customer” or “suffering COVID-19 Symptoms” before they assess priority of restoration
All newly-appointed provisioning will be pushed back to Monday 1st June 2020 at the earliest
All other Gradwell products (Wave, 3CX, SIP Trunks etc) remain unaffected with the exception of number porting, which may be delayed
Openreach/BT have declared that the current situation they and we are all facing is a matter beyond their control in light of COVID-19.
As such, appointments for provision and repair are on a best endeavours basis only, this covers everyone nationwide and will impact the following products that we provide: DSL, Ethernet, FTTC, FTTP, FIBRE, PSTN, ISDN2, ISDN30, LLU MPF and SMPF, including adjustment of orders.
Fault Repair
During this time, priority and restoration of services will take place for critical functions only, such as NHS, pharmacies, utilities, emergency services, retail and wholesale food distribution outlets and financial services. This also applies to customers deemed “at risk”.
Ongoing repairs to the BT/Openreach infrastructure will continue, but with high priority focus being on the above-mentioned critical core services ahead of all others. You will be asked by Gradwell if anyone is deemed within the building or location is considered at “at risk” of exposure to Covid-19: Customer meets criteria for repair and IS symptomatic Customer meets criteria for repair and IS NOT symptomatic
Ongoing repairs to the BT/Openreach infrastructure will continue, but with high priority focus being on the above-mentioned critical core services ahead of all others. We appreciate your patience during these times, and we’re sure you understand that the protection and restoration of core services is paramount to sustaining core infrastructure services.
Openreach have advised on Fault repair with immediate effect:
To support efforts to reduce human contact and promote social distancing, all installation activities that require access to a customer’s premises are now being assessed and the customer to state the following criteria to ensure if repairs are deemed essential that appropriate teams can deal with the issue at hand:
Customer meets criteria for repair and IS symptomatic
Customer meets criteria for repair and IS NOT symptomatic
Openreach will attempt to complete as much of the inflight orders from outside of the premises as possible, but if internal work is required, these will be done on a priority and risk assessed basis. Any orders that do not require on premise installation will proceed as normal, but we appreciate these cases are limited. The exception to these rules are those businesses identified as critical national infrastructure. This includes; NHS, pharmacies, utilities, emergency services, retail and wholesale food distribution outlets, and financial services businesses. On site installation work will be permitted for these businesses but we will have to justify the criticality of the service to Openreach.
The Openreach Emergency Helpdesk will remain open. However, all business as usual contact centres have now closed.
Porting of Numbers
Following on from previous updates on BT’s porting backlog, we are pleased to announce this has now been cleared and we are able to place new orders again. There still may be a slight delay in contrast to normal timescales, as it’s likely that BT and our direct suppliers will receive a large amount of new port requests all at once, but this will likely only add on 24-48 hours to the normal processing time. In conclusion, we will not be operating at our normal timescales for another few days, but we anticipate everything to be back to normal in the short term. We appreciate your patience during this time.
New Orders
All new orders received with immediate effect that require BT or Openreach infrastructure (the majority) are being moved to commence from 1st June 2020 onwards. This will be under constant review and may have further delays should the situation worsen. Exceptions apply for customers deemed “at risk”.
All existing orders in the system with BT or Openreach will continue to progress, but with a view to completing the orders as soon as possible and may be delivered well outside of expected and industry standard timelines.
We are still accepting new orders, however, there will be a delivery backlog for any products requiring BT or Openreach provision until at least 1st June 2020 onwards. All other Gradwell products, eg Wave, Multi User VoIP, 3CX and SIP Trunk services, are currently not impacted and delivery times will remain unaffected.
Openreach have announced the below with regards to WLR and MPF new line installs.
Openreach will be assisting providers to bring forward certain new line installs to an earlier date. They will be contacting customers directly to try to agree an earlier install date to complete the work on behalf of the Provider.
Only lines that have relatively simple installation journeys will be eligible for this support. Orders that are deemed to have complex delivery that would require additional engineering work or orders where Openreach feel that it would not be possible to gain access to the premises safely in adherence to their COVID-19 safe working practices will be excluded from this process. For example, orders that require entry to blocks of flats etc will be out of scope.
Core infrastructure service providers
We will of course continue to share more information from core suppliers like BT Openreach on this page as soon as we have it. A full breakdown of Openreach’s current service status is in the table below.
Openreach Critical Functions
Damage
Open (limited service)
Welfare
Open (limited service)
DSO
Open (limited service)
Product
Repair
Provision
Escalations (EPOC)
No new work accepted
No new work accepted
Premium Business Helpdesk
No new work accepted
No new work accepted
WLR
BAU if non-appointed
BAU if non-appointed
LLU
BAU if non-appointed
BAU if non-appointed
FTTC
BAU if non-appointed
BAU if non-appointed
SOGEA
BAU if non-appointed
BAU if non-appointed
GFAST
BAU if non-appointed
BAU if non-appointed
SOGFAST
BAU if non-appointed
BAU if non-appointed
Migration Services
BAU if non-appointed
BAU if non-appointed
ISDN
BAU if non-appointed
BAU if non-appointed
FTTP
BAU if non-appointed
BAU if non-appointed
Ethernet
BAU if non-appointed
BAU up to curtilage
BAU: For Total Loss of Service Faults: Openreach will attempt to activate the service remotely. If they are unable to, then they will visit the premises and ask two risk assessment questions:
1) Is there anyone on-site who has Covid-19 symptoms?
2) Has there ever been anyone on-site with symptoms?
3) Has anyone on-site been advised by the NHS via a letter to isolate for 12 weeks?
If the answer is yes to either of these questions then they will not access the premises and the fault repair will be postponed until restrictions have been lifted. If not, they will schedule a repair.
For all other repair faults, Openreach will only resolve if it’s possible to fix remotely and without access to the premises.
Provisions: Will only attempt to access the premises if the provider is classed as CNI/welfare/at risk/specific key worker (see below).
CNI: refers to “Critical Network Infrastructure.”
All Welfare/At Risk/Specific Key Worker cases will be reviewed by Openreach after a case submission by a customer.
Ofcom announced this afternoon the new 3-digit telephone number ‘119’ to be used as part of the NHS’s Covid-19 response, the number will be used as part of the NHS’s effort to handle the response to the Coronavirus situation.
The 119 number is supported by networks and so calls will connect as soon as the Government announce the service has been launched.
The number will be free to dial, in line with the NHS 111 service, as directed by Ofcom.
Sangoma Technologies announced the general availability of its new video conferencing and collaboration service Sangoma Meet. Sangoma Meet is a multi-party, video conferencing and desktop sharing, cloud-based service, specially designed to enable a great work from home or collaboration experience. HD video support is standard with Sangoma Meet, ensuring the highest quality video calls possible.
Sangoma Meet is also highly secure, fully encrypting password-protected video conferences to avoid problems with unauthorised users hacking into a video meeting, and Sangoma will not rent or sell Sangoma Meet user information to any third parties, including any social networks. It can also be used as a stand-alone service or in conjunction with its Unified Communication Business Phone Systems.
Its simple to use with all the features you need
Moderator Privileges: If you are holding a team call, you have full moderator privileges. You can mute/unmute attendees, send them private messages, or kick anyone off the call. You also have the option to invite audio-only participants to limit video sharing.
Chat: If you prefer not to talk on your video call, use the chat feature in Sangoma Meet to share your thoughts with the group. A full suite of emojis will keep the conversation engaging and light!
Screen Sharing: Give your coworkers real-time examples and streamline meetings with screen sharing in Sangoma Meet. Instantly share your screen and choose what you want to show to others.
Inviting users: Its as simple as, copy your meeting link and send it to the desired parties. As soon as users click on the link, they immediately join the conference.
Sangoma Meet is available for use today in the company’s General Availability release. It has already been in beta usage, both internally and with partners, with excellent reviews to date.
The Sangoma Meet cloud service has been updated to include additional functionality such as mobile apps (for iOS and Android), calendar integration (for Google G-suite and Microsoft Outlook), desktops apps (for both Windows and Mac) to further enhance user experience, and dial-in functionality to the video conference using a phone (with enhanced security via a PIN).
To help its end-users communicate more effectively during this global pandemic, Sangoma decided to launch this new service completely free of charge to everyone, during these troubled times.
The full datasheet explaining all the features can be viewed here and the help site is located here
Given the pressure on the emergency services presently, the Home Office have requested that the 101 Non-Emergency number be made free to all callers from 1st April 2020. Therefore these calls placed through our network will be free from midnight this evening.
We understand that this change is intended to be permanent, and not just for the duration of the Covid-19 emergency.
Please note that although this change will be in place from midnight tonight it may not be reflected in the ratesheet immediately .
BT Openreach (who help us supply internet connectivity services) have advised that provision and repair of their services are now on a “best endeavours” basis only across the UK and will impact all our connectivity products: DSL, Ethernet, FTTC, FTTP, FIBRE, PSTN, ISDN2, ISDN30, LLU MPF and SMPF
Priority restoration of services will only take place for organisations deemed “critical”, including NHS, pharmacies, utilities etc (full list below)
Ongoing repairs will continue for all, but with priority given to critical organisations
All newly-appointed provisioning will be pushed back to Monday 1st June 2020 at the earliest
Openreach/BT have declared that the current situation they and we are all facing is a matter beyond their control in light of COVID-19.
As such, appointments for provision and repair are on a best endeavours basis only, this covers everyone nationwide and will impact the following products that we provide: DSL, Ethernet, FTTC, FTTP, FIBRE, PSTN, ISDN2, ISDN30, LLU MPF and SMPF, including adjustment of orders.
Fault Repair
During this time, priority and restoration of services will take place for critical functions only, such as NHS, pharmacies, utilities, emergency services, retail and wholesale food distribution outlets and financial services.
Ongoing repairs to the BT/Openreach infrastructure will continue, but with high priority focus being on the above-mentioned critical core services ahead of all others. We appreciate your patience during these times, and we’re sure you understand that the protection and restoration of core services is paramount to sustaining core infrastructure services.
Openreach have advised on Fault repair with immediate effect:
To support efforts to reduce human contact and promote social distancing, all installation activities that require access to a customer’s premises are now suspended until after 1st June 2020. Openreach will attempt to complete as much of the inflight orders from outside of the premises as possible, but if internal work is required, these will be rebooked post 1st June 2020. Any orders that do not require on premise installation will proceed as normal, but we appreciate these cases are limited.
The exception to these rules are those businesses identified as critical national infrastructure. This includes; NHS, pharmacies, utilities, emergency services, retail and wholesale food distribution outlets, and financial services businesses. On site installation work will be permitted for these businesses but we will have to justify the criticality of the service to Openreach.
Porting of Numbers
During this time, the ability to port and move numbers between all core telecoms suppliers has also been affected, with BT/Openreach now declaring the following porting requests that are in flight will be affected with immediate effect. Those porting services affected are:
Ports that are Multi Line (a number of sequential numbers 01234 000000 – 01234 000100 or broken number ranges) as these have to be manually triggered. These port requests will be postponed until further notice and will not be ported to your new supplier. They will remain operational until they can be processed within a normal timeframe.
Single Line ports (i.e. 01234 567890) are still available but may be delayed beyond a previously agreed date
Any new import requests for porting where BT is the range holder will not be accepted until further notice
New Orders
All new orders received with immediate effect that require BT or Openreach infrastructure (the majority) are being moved to commence from 1st June 2020 onwards. This will be under constant review and may have further delays should the situation worsen.
All existing orders in the system with BT or Openreach will continue to progress, but with a view to completing the orders as soon as possible and may be delivered well outside of expected and industry standard timelines.
We are still accepting new orders, however, there will be a delivery backlog for any products requiring BT or Openreach provision until at least 1st June 2020 onwards.
Core infrastructure service providers
We will continue to share more information from core suppliers like BT Openreach on this page as soon as we have it. A full breakdown of Openreach’s current service status is in the table below.
This website uses cookies
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.AcceptRejectRead More
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
