Security on SIP Trunks and SIP Endpoints - Revision history

imported>Schoen.kevin: /* Customer Responsibility for endpoint security */

2012-03-05T15:47:15Z

Customer Responsibility for endpoint security

← Older revision		Revision as of 15:47, 5 March 2012
Line 16:		Line 16:
	*ACD is not responsible for mis-configured or poor security on the account associated with the end-point device. ACD enters a password security that is requested by the end-user.		*ACD is not responsible for mis-configured or poor security on the account associated with the end-point device. ACD enters a password security that is requested by the end-user.
	*Securing equipment that is not under the direct control and ownership of ACD.		*Securing equipment that is not under the direct control and ownership of ACD.
	*Any Expenses or fees associated with calls to and from ACD SIP Trunk accounts.		*Any Expenses or fees associated with calls to and from ACD SIP Trunk accounts are the responsibility of the purchase of the service.
	*~~Any~~ fees or expenses to consultants, other service providers for securing non-ACD owned and controlled equipment.		*ACD is not responsible for ny fees or expenses to consultants, other service providers for securing non-ACD owned and controlled equipment.
	*The customer is responsible for paying any fees and expenses associated with calls originating from your accounts.		*The customer is responsible for paying any fees and expenses associated with calls originating from your accounts, even if fraudulent. ACD did not committ the fraud. You are responsible for any and all fraudlend calls made from your account.
	*ACD is not responsible for any call blocking functions.		*ACD is not responsible for any call blocking functions.

	Bottom line: the end-user accepts full responsibility for any mis-configured equipment or accounts when they are in control of the end-point device.		Bottom line: the end-user accepts full responsibility for any mis-configured equipment or accounts, and any calls made from when they are in control of the end-point device.

	==ACD recommendations for security on endpoint devices==		==ACD recommendations for security on endpoint devices==

imported>Schoen.kevin at 18:28, 13 February 2012

2012-02-13T18:28:20Z

← Older revision		Revision as of 18:28, 13 February 2012
Line 21:		Line 21:
	*ACD is not responsible for any call blocking functions.		*ACD is not responsible for any call blocking functions.

	Bottom line: the end-user accepts full ~~responsibilty~~ for any mis-configured equipment or accounts when they are in control of the end-point device.		Bottom line: the end-user accepts full responsibility for any mis-configured equipment or accounts when they are in control of the end-point device.

	==ACD recommendations for security on endpoint devices==		==ACD recommendations for security on endpoint devices==
	*Always use a complex password.		*Always use a complex password.
	*Change the password ~~occassionally~~.		*Change the password occasionally.
	*Encrypt the passwords.		*Encrypt the passwords.
	*Ensure that there is adequate firewalling		*Ensure that there is adequate firewalling
Line 31:		Line 31:
	*Configure the endpoint to a static IP Address and relay that address to ACD.		*Configure the endpoint to a static IP Address and relay that address to ACD.
	*Review your call logs on http://phone.acd.net		*Review your call logs on http://phone.acd.net
	*Block ~~unneccessary~~ services in http://phone.acd.net, such as international long distance, etc.		*Block uneccessary services in http://phone.acd.net, such as international long distance, etc.

imported>Schoen.kevin: /* Where ACD is responsible for Security to the endpoint */

2012-02-13T18:27:17Z

Where ACD is responsible for Security to the endpoint

← Older revision		Revision as of 18:27, 13 February 2012
Line 4:		Line 4:

	==Where ACD is responsible for Security to the endpoint==		==Where ACD is responsible for Security to the endpoint==
	In some instances, ACD is responsible for the SIP endpoint. ACD is ~~responsbile~~ for security when:		In some instances, ACD is responsible for the SIP endpoint. ACD is responsible for security when:

	* The endpoint solely ~~controled~~ by ACD and no other party, and		* The endpoint solely controlled by ACD and no other party, and
	* The endpoint password has not been provided to the end-user, and		* The endpoint password has not been provided to the end-user, and
	* Where the endpoint is owned by ACD		* Where the endpoint is owned by ACD

imported>Schoen.kevin: /* ACD recommendations for security on endpoint devices */

2012-02-13T18:26:30Z

ACD recommendations for security on endpoint devices

← Older revision		Revision as of 18:26, 13 February 2012
Line 30:		Line 30:
	*Ensure keepalives are used to a static IP address.		*Ensure keepalives are used to a static IP address.
	*Configure the endpoint to a static IP Address and relay that address to ACD.		*Configure the endpoint to a static IP Address and relay that address to ACD.
	*Review your call logs on http://~~myaccount~~.acd.net		*Review your call logs on http://phone.acd.net
	*Block unneccessary services in http://~~myaccount~~.acd.net, such as international long distance, etc.		*Block unneccessary services in http://phone.acd.net, such as international long distance, etc.

imported>Schoen.kevin at 18:25, 13 February 2012

2012-02-13T18:25:09Z

← Older revision		Revision as of 18:25, 13 February 2012
Line 1:		Line 1:
	SIP Trunks and SIP Endpoints, are devices or software interfaces that accept SIP calls ~~from the ACD~~ network.		SIP Trunks and SIP Endpoints, are devices or software interfaces that accept or send SIP calls to a telephone network.

			In general sip services are described here: http://www.acd.net/sip.cfm

	==Where ACD is responsible for Security to the endpoint==		==Where ACD is responsible for Security to the endpoint==

imported>Schoen.kevin at 18:24, 13 February 2012

2012-02-13T18:24:13Z

← Older revision		Revision as of 18:24, 13 February 2012
Line 1:		Line 1:
	SIP Trunks and SIP Endpoints, are devices or software interfaces that accept SIP calls from the ACD network.		SIP Trunks and SIP Endpoints, are devices or software interfaces that accept SIP calls from the ACD network.

	In some instances, ACD is responsible for the SIP endpoint, ~~where~~ the ~~SIP~~ endpoint is ~~an ACD controlled device,~~ ACD ~~is responsible~~ for ~~ensureing the SIP enpoint is secure.~~		==Where ACD is responsible for Security to the endpoint==
			In some instances, ACD is responsible for the SIP endpoint. ACD is responsbile for security when:

			* The endpoint solely controled by ACD and no other party, and
			* The endpoint password has not been provided to the end-user, and
			* Where the endpoint is owned by ACD

			==Customer Responsibility for endpoint security==

	Where the SIP endpoint is not controlled or directly managed by ACD:		Where the SIP endpoint is not controlled or directly managed by ACD:

imported>Schoen.kevin at 18:18, 13 February 2012

2012-02-13T18:18:30Z

← Older revision		Revision as of 18:18, 13 February 2012
Line 22:		Line 22:
	*Configure the endpoint to a static IP Address and relay that address to ACD.		*Configure the endpoint to a static IP Address and relay that address to ACD.
	*Review your call logs on http://myaccount.acd.net		*Review your call logs on http://myaccount.acd.net
			*Block unneccessary services in http://myaccount.acd.net, such as international long distance, etc.

imported>Schoen.kevin: Created page with "SIP Trunks and SIP Endpoints, are devices or software interfaces that accept SIP calls from the ACD network. In some instances, ACD is responsible for the SIP endpoint, where t..."

2012-02-13T17:36:07Z

Created page with "SIP Trunks and SIP Endpoints, are devices or software interfaces that accept SIP calls from the ACD network. In some instances, ACD is responsible for the SIP endpoint, where t..."

New page

SIP Trunks and SIP Endpoints, are devices or software interfaces that accept SIP calls from the ACD network.

In some instances, ACD is responsible for the SIP endpoint, where the SIP endpoint is an ACD controlled device, ACD is responsible for ensureing the SIP enpoint is secure.

Where the SIP endpoint is not controlled or directly managed by ACD:
*ACD is not responsible for performing security functions on endpoint devices.
*ACD is not responsible for mis-configured or poor security on the account associated with the end-point device. ACD enters a password security that is requested by the end-user.
*Securing equipment that is not under the direct control and ownership of ACD.
*Any Expenses or fees associated with calls to and from ACD SIP Trunk accounts.
*Any fees or expenses to consultants, other service providers for securing non-ACD owned and controlled equipment.
*The customer is responsible for paying any fees and expenses associated with calls originating from your accounts.
*ACD is not responsible for any call blocking functions.

Bottom line: the end-user accepts full responsibilty for any mis-configured equipment or accounts when they are in control of the end-point device.

==ACD recommendations for security on endpoint devices==
*Always use a complex password.
*Change the password occassionally.
*Encrypt the passwords.
*Ensure that there is adequate firewalling
*Ensure keepalives are used to a static IP address.
*Configure the endpoint to a static IP Address and relay that address to ACD.
*Review your call logs on http://myaccount.acd.net