Installing UK voice prompts for Asterisk

26th September 2011, 08:53 pm

By default the English language voice prompts that Asterisk comes with have an American accent. There are some free UK voice prompts available and below are instructions for downloading and installing those. The instructions below will replace the existing US prompts with the UK ones.

The prompts can be found here – http://www.enicomms.com/cutglassivr/

More details about different language voice prompts can be found here – http://www.voip-info.org/wiki/view/Asterisk+sound+files+international

The commands below download the wav, ulaw, alaw, g729 and g723 codec versions.

First create a folder to download the files to -

cd /usr/src
mkdir uk
cd uk

next grab the files -

wget http://www.enicomms.com/cutglassivr/audiofiles/Alison_Keenan-British-English-...
wget http://www.enicomms.com/cutglassivr/audiofiles/Alison_Keenan-British-English-...
wget http://www.enicomms.com/cutglassivr/audiofiles/Alison_Keenan-British-English-...
wget http://www.enicomms.com/cutglassivr/audiofiles/Alison_Keenan-British-English-...
wget http://www.enicomms.com/cutglassivr/audiofiles/Alison_Keenan-British-English-...

next extract the files that were downloaded -

find . -name 'Alison_Keenan-British-English-*' -exec tar xvfz {} \;

now we’re going to replace the file extensions on some of the files to match the default Asterisk ones -

find . -exec rename .g711a .alaw {} \;
find . -exec rename .g711u .ulaw {} \;

now remove the original tar files, copy over the new files and tidy up the download folder -

rm -f Alison_Keenan-British-English-*
unalias cp
cp -rf * /var/lib/asterisk/sounds/en
cd ..
rm -rf uk

You can hear an example of these prompts by calling the echo test number here – http://sysadminman.net/livedemo.html

Good prompts - Notes

Updated trunk configuration Asterisk, freepbx and Portech MV-3xx

This is my new updated functional configuration of Portech.

This guide will help you settings up Trunk in Asterisk (freebox, trixbox, PBIF, etc.) for Portech GSM Gateway.

The new configuration will pass Caller ID.

First we will configure the Portech MV-372 i believe this configuration will also work with Portech MV-370 and other Portech MV-3xx like MV-374.

Login to your portech

Route

• Mobile To Lan Settings:
  

  Item	CID	URL
  0	*	192.168.x.x (your asterisk ip)

  
  
• Lan To Mobile Settings:
  

  Item	URL	Call num
  0	*	#

• Mobile
  • Settings:
    Mobile 1:
    Sip From: Tel/Tel (No reg)
    CLID Presentation: Invocation
    LAN Answer Mode: Income

    Do the same for Mobile 2

• SIP Settings
  • Service Domain
    You only fill Domain Server and Proxy server with your asterisk IP address:
    Domain Server: 192.168.x.x
    Proxy Server: 192.168.x.x

    Again do the same for Mobile
    

  • Port Settings
    Make sure SIP Port for Mobile 1 is 5060 and port 5062 for Mobile 2
    

Other settings are fine you may leave them as they are, only check Network (WAN) settings if you don't have DHCP or you need static IP for Portech gsm gateway.

Don't forget to save changes (should reboot after saving)

Asterisk/Freepbx

Login to your FreePBX and add SIP Trunk

Outbound Called ID: xxxxxxx (put you number here)
Maximum Channels: 1

Outgoing settings
Trunk Name: SIM1 (you may put anything you like)
PEER Details:
host=192.168.x.x (your Portech IP address)
type=peer
port=5060

Incoming Settings:
USER Context: xxxxxxx (put you mobile number)
Leave Incoming settings blank.

Click submit (don't forget the Orange bar on top after you make changes in your server)

Add another SIP Trunk for SIM2

Outbound Called ID: yyyyyyyy (put you phone number here)
Maximum Channels: 1
go to Outgoing settings

Trunk Name: SIM2
PEER Details:
host=192.168.x.x (your Portech IP address)
type=peer
port=5062 (important)

Incoming Settings:
USER Context: yyyyyyyy (put you second phone number)

Again apply changes.

We're almost done. Now to make this work we have to create Outbound Route, so click Outbound Routes
Put Route name as you wish, i have called it Portech_1 (since i will add another and will make it Portech_2)
Dial Patterns: i have put 049XXXXXX because i want only mobile numbers from the same provider to go through this trunk (through Portech) i mean i want to cut the costs right?

Trunk Sequence: i added SIP/SIM1 and SIP/SIM2
You can separate Trunks from OutRoutes if you have SIM cards from two different providers, just create another Outbound Route remove one Trunk from trunk sequence of the first route that we created and add it to this new one. Submit.

Also don’t forget in order to receive calls you need to have Inbound Route setup on Asterisk/freepbx. To get you started just create new Incoming route set you destination to an extension or ring group or any other destionation you would like to transfer calls to.

Only thing you left to do now is click Submit Changes then Apply Configuration Changes and pray for this to work.

Hope this new configuration will work better.

Notes - Works Great

There are two types of transfer on a Gigaset IP DECT phone. The first way is called a DECT transfer and can only be used to transfer a call to another handset registered to the same base station.

The second type is a SIP transfer and can be used to transfer a call to any other number using your VoIP service provider or PBX. Chances are this is the type of transfer you want to do so you can skip right to the SIP transfer section if you want to.

DECT/Internal Transfer How-To

• During a call, press the "int" key on the handset. This is usually the left hand button on the four way key in the middle but it depends on the handset model.


• The person you were talking to now hears some awful music on hold generated by the Gigaset phone itself!


• You will see a list of the other DECT devices registered to the base station, select one of these and it will ring.


• Announce the call and press the conf button just under the screen when ready to transfer.


• You will actually be in the 3-way conference now but if you don't want this then just hang up and the other two parties will be talking to each other.

SIP/External Transfer How-To

An external transfer is made a lot easier if you change a setting in the web interface of the phone before hand. You only need to do this once by the way!

The setting is called "Transfer Call by On-Hook" and is found by clicking "settings" then "telephony" and "advanced" in the web interface. Change it to "yes"

After this the actual transfer process is fairly straight forward:

• During a call, press the options button just under the screen and choose the ext call option.


• Dial a number and make a call as normal.


• When you are ready to transfer, simply press the hang up key on the Gigaset handset and the other two callers are connected.

Notes

( - or: How can I add [Active Directory] user accounts into some? clients’ local Administrators group without touching each client?)

This article describes the feature “Restricted Groups” in Group Policy. This feature enables you - as the administrator - to configure group memberships on the client computers or member servers. You can add user accounts to groups on client machines that are in the scope of the policy.

As there are many questions about this in the newsgroups, I will come up with an example that shows how to put a group of Active Directory users into the local Administrators group on the clients.

For this article, I assume that you already created a global security group containing all users that shall become local Administrators on some client computers. In my example, the group is called “localAdmins”. The target (= client) computers reside in a specific OU.

If you’re using the Group Policy Editor, you navigate to the OU where the client computers reside and right-click it. Choose “Properties” and “Group Policy” where you create a new Policy and click “Edit”. You then navigate to:

CompConf\Windows Settings\Security Settings\ and then right-click “Restricted Groups” and choose “Add Group”.

You simply add the created group by clicking “Browse..” or typing the group name into the box.

After clicking “OK”, another beautiful window opens up, where you can find two boxes. The upper box, saying “Members of this group”, the lower one saying “This group is a member of”.

If you added users or groups into the “Members of this group” box, you would advise the Restricted Groups feature to put the users and groups you selected into the localAdmins group. Restricted Groups would then replace the current members of the localAdmins group with the users and groups you filled into the box. Please recognize my words, it would replace them - just wipe existing users out of the localAdmins group.

As we do not want to add users or other groups to our group, but add our localAdmins group the local Administrators group on our clients, we have a look at the lower box - labeled “This group is member of”. We click “Add” and type in the name of the group, we want localAdmins to be member of. In this case, it “Administrators”. We then simply click “OK” and “Apply” and close all windows. “This group is member of” advices “Restricted Groups” to add our localAdmins group into the “Administrators” group of the clients. The existing group members will not be touched - it simply adds our group.

Notes

To reset a Cisco router to factory default (removing the startup configuration file), perform these steps:

1.	To erase the configuration file, issue the erase nvram: command.

Reload the router by issuing the reload command. 2. If this does not solve the problem, attempt to break into ROM Monitor (ROMmon) by issuing the break sequence (usually Ctrl and break from the Hyperterminal) from a console connection.

Refer to:

Cisco Standard Break Key Combinations

You should see this ROMmon prompt:

rommon 1>

3. Change the configure register value to ignore the startup configuration by issuing the confreg command, as shown in this example:

rommon 2> confreg 0x2142

4. To reload the router, issue the reset command, as shown in this example:

rommon 3> reset

5. After the router boots, issue the enable command at the Router > prompt.

The prompt changes to Router#, indicating that the router is now in privileged mode.

6. To enter config mode, issue the config terminal command.

You should now see a Router(config)# prompt.

7. To change the configure register to recognize the startup configuration, issue the config-register command, as shown in this example:

Router (config)# config-register 0x2102

To break out of configuration mode, press Cntl and Z.

To save the blank configuration, issue the copy-running config-startup config command.

notes

A session with Apple's telephone support came up with a solution. My wife hard established an iCloud account but had no signed in. Once she did so, the "plus" sign returned, she could add events by tapping +, double-tapping a date, and by using Siri.

Notes

If the Remote Procedure Call (RPC) service is not listed as a dependency for your Print Spooler Service, you need to inform XP that the Print Spooler service depends on the RPC service.

Click Start, Run and in the box enter (including the important space after the equals sign):

sc config spooler depend= RPCSS

Click OK to assign the RPC service to the Print Spooler service, then be sure the RPC Service is running and start your Print Spooler Service.

Notes

Could Not Get Lock /var/lib/apt/lists/lock

Posted by Irfan Ashraf

Problem:
When i try to update software packages in Ubuntu i get following error

• E: Could Not Get Lock /var/lib/apt/lists/lock

Solution:
Run Terminal and type these commands

• sudo rm /var/lib/apt/lists/lock
• sudo apt-get clean
• sudo apt-get update

Notes

Cisco PIX/ASA Causes SMTP Banner Corruption

November 8th, 2009 Aaron Leave a comment Go to comments

Traffic inspection rules on a Cisco PIX or ASA firewall will sometimes cause the SMTP banner to appear corrupted.

When testing access to your mail server from outside, you may notice that the SMTP banner looks like this:

This is just a symptom of the problem, which is that the SMTP traffic inspection rule is interfering with the SMTP data stream.  Another symptom would be to see email messages destined for this server seemingly stuck in the SMTP queue on a server outside the network.  This can ultimately cause delayed and undeliverable mail, especially for larger messages, such as those with attachments.

The resolution for this problem is to disable the traffic inspection rule for SMTP/ESMTP on the Cisco PIX or ASA firewall.

On a PIX, this can be done from the command-line using the “no fixup protocol SMTP 25” command.  It can also be disabled from the PIX Device Manager (PDM).

On an ASA, it’s a little different.  From the command line (assuming your policy map is named “global_policy” and your class is named “inspection_default”):

CiscoASA(config)#policy-map global_policy
CiscoASA(config-pmap)#class inspection_default
CiscoASA(config-pmap-c)#no inspect esmtp 

From the Adaptive Security Device Manager (ASDM):

1.       Go to Security Policy –> Open the inspection rule:

2.       Go to the Rule Actions tab and uncheck the box next to ‘ESMTP’

3.       Test from outside the PIX/ASA again by telnetting to port 25; your SMTP banner should now look like this (I have masked the name of the server for privacy).

That’s it.  I have made it standard practice to just disable this inspection rule on all Cisco ASA firewalls that I deploy to avoid problems.

Notes

HowTo: Elastix DAHDI Trunk Routing with DID

If you have multiple FXO (PSTN) lines into your PBX, it is always nice to be able to route these in-bound calls based on the physical line they arrive upon.  Getting this working with DAHDI in Elastix has been driving me up the wall!

This issue has been bugging me for over a week now and I have finally got it to work.  I have two trunks connected via FXO modules on a TDM400 card, but I could not get the DID working with them (CLI with BT sorted).  But once Asterisk had the call, I could not make Asterisk make a decision with call based on which number/line the caller called.  Not the number the caller is calling from, this is CLI or CID, but the number they dialled to make your line ‘ring’.

Asterisk was either saying there was no route and answering the call to say the number you have called is not in service, or just handling the 2 lines in the same way – i.e. it could not tell them apart.  Here I detail my findings so you can process lines automatically.

I had most of the configuration right, but I had to hand edit another configuration file to actually to get the changes made via the web interface actually working.  Trying to find this last little bit of information on the forums has been maddening to say the least.

Changing the route

First you need to correct the router handler, by changing a setting in a configuration file.  There is no graphical interface for this I’m afraid and it is the only file you need to manually edit by a suitable means.

The default setting in this configuration file is ‘from-pstn’ and this needs to be changed to ‘from-zaptel’.  You need to edit:

/etc/asterisk/dahdi-channels.conf

You need to find the correct section for your line connection.  For me this was lines 3 & 4.  Below is the example original settings for my channel 3:

;;; line=”3 WCTDM/4/2 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
callerid=
group=
context=default

And you need to edit this for each channel to become like this:

;;; line=”3 WCTDM/4/2 FXSKS”
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 3
callerid=
group=
context=default

Then save the file back and restart Asterisk.

Marking the Channel DID

The next stage is to assign DID numbers to these channels so a decision can be made on how to process the call based on line ID.

Elastix does not have an interface to the required facility, so you need to un-embed the FreePBX console, details are here.

Once in the FreePBX console, you need to choose ‘ZAP Channel DIDs’ from the menu on the left.  You should get a screen similar to:

ZAP DIDs

It is quite simple to complete, needing only 3 bits of information:

• Channel – The DAHDI channel you are assigning the DID to.
• Description – Your description for this allocation.  I would suggest an name and a summary of the DID you will be allocating.
• DID: The DID number need to call to make this channel ‘ring’.

An example UK configuration might look like this for channel 3, used to be routed (Inbound Routes) to the sales department for the number: 01234-123456:

ZAP DID Sample

Once completed, you can click ‘Submit Changes’.  You need to repeat this for each FXO port you have for inbound calls.

You can then save the changes back and configure the ‘Inbound Routes’ to actually ‘route’ the calls where you want them.

You can actually use almost any number in the DID, but I suggest you use the full number, including the STD, in case you have any ‘out of area’ number.  And it generally reduces confusion in the future.

Notes

Figure 2-13 shows the use of source and destination ports. The host on the 10.1.2.0/24 network accesses a single host for both web services and Telnet services. When the host accesses the server for web services, the local address is translated to 209.165.202.129. When the host accesses the same server for Telnet services, the local address is translated to 209.165.202.130.

Figure 2-13 Policy NAT with Different Destination Ports

The syntax for this configuration example follows:

access-list WEB permit tcp 10.1.2.0 255.255.255.0 209.165.201.11 255.255.255.255 eq 80

access-list TELNET permit tcp 10.1.2.0 255.255.255.0 209.165.201.11 255.255.255.255 eq 23

nat (inside) 1 access-list WEB

global (outside) 1 209.165.202.129 255.255.255.255

nat (inside) 2 access-list TELNET

global (outside) 2 209.165.202.130 255.255.255.255

Limitations

The following configuration limitations apply to policy NAT:

•Access lists must contain permit statements only. Access lists for policy NAT cannot contain deny statements.

•An access list must be used only once with the nat command. For example, the following configuration would produce an error:

nat (inside) 1 access-list mylist-A

nat (inside) 2 access-list mylist-A

Whereas, the following configuration would not produce an error:

nat (inside) 1 access-list mylist-A

nat (inside) 2 access-list mylist-B

•Use an access list only once between the nat and static commands.

•A global address cannot be used concurrently for NAT and PAT.

•static commands are matched and executed before nat commands.

•Policy NAT does not support SQL*Net, which is supported by regular NAT.

Notes

Servers	Ports	Descriptions
Port Mapper	449	Port Mapper returns the port number for the requested server.
Sign-on	8476 (9476)	Sign-on is used for every iSeries Access connection to authenticate users and to change passwords. It is also used to retrieve Application Administration settings.
Central	8470 (9470)	Central is used when an iSeries Access license is required. It's also used for downloading conversion tables.
Data Queue	8472 (9472)	Data Queue allows access to the iSeries data queues, used for passing data between applications.
Database	8471 (9471)	Database is used for accessing the OS/400 database.
Remote Command	8475 (9475)	Remote Command is used for sending commands from a PC to an iSeries and for program calls.
File	8473 (9473)	File is used for accessing any part of the OS/400 file system.
Print	8474 (9474)	Print is used to access printers known to the OS/400.
Web Admin	2001 (2010)	Web Admin is used to access Web applications served by the iSeries.
DDM	446 (448)	DDM is used to access data via DRDA. It's also used for record-level access.
Telnet	23 (992)	Telnet is used to access 5250 emulation.
Netserver	137, 138, 139, 8474	Netserver allows access to the OS/400 Integrated File System (IFS) from Windows PCs.
USF	8480	USF (or Ultimedia) is used for multimedia data. (Note: This server is being removed in a future release.)
LDAP	389 (636)	LDAP provides a network directory service.
Management Central	5555 5544 5577 (5566)	Management Central is used to manage multiple iSeries 400s in a network.

Figure 1: These are the ports associated with the servers used by iSeries Access for Windows.

Figure 2 lists some common iSeries Access functions and the servers that they utilize. Using Figure 1 and Figure 2, you should be able to determine which ports you need to open on your firewall. Also, these two tables are available on the iSeries Access Web site, in the Information APARs section. Select II12227. This page is kept up-to-date with the latest information on iSeries Access port usage. There could be additions to this table at any time, although it's likely that changes will be seen only on release boundaries.

Client Access Function	Servers Used
PC5250 display and printer emulation	Sign-on, Central, Telnet
Data transfer	Sign-on, Central, Database
Base iSeries Navigator support	Sign-on, Remote Command
All iSeries Navigator functions	Sign-on, Remote Command, File, Print, Database, Web Admin, Management Central, USF, Netserver, LDAP, Data Queue
ODBC	Sign-on, Database
OLE DB	Sign-on, Database, DDM, Remote Command, Data Queue
AFP Viewer	Sign-on, Print
Client Access Install from iSeries	Netserver
Incoming Remote Command	Uses no specific server, and iSeries port will vary. PC-side port is 512.
Fax support	Sign-on, Print

Notes

if you type in .\ before the username, that will instruct it that you are logging onto the local computer.  so for your Administrator example, you would put in     .\Administrator

Notes

To reset the SST password:
-sign on as QSECOFR
-use the  Change IBM Service Tools Pwd (CHGDSTPWD) command:
CHGDSTPWD PASSWORD(*DEFAULT)
-now go into STRSST, and sign on with user QSECOFR and password QSECOFR
you will be prompted to change the password.

You can access a similar hardware listing without going into SST using the Display Hardware Resources (DSPHDWRSC) command:
DSPHDWRSC TYPE(*AHW) OUTPUT(*PRINT)

Getting Support for Form Types on One or More Remote Output Queues

Remote writers can support form types; however, you must start the writer with the message option set to *INQMSG (so you get an inquiry message whenever the form type changes) or change the writer after it has started. To start the writer with form type support, use the following operating system command:

STRRMTWTR OUTQ(remote-outq-name) FORMTYPE(*ALL *INQMSG)

To change an existing writer to have form type support, use the following operating system command:

CHGWTR WTR(remote-outq-name) FORMTYPE(*ALL *INQMSG)

After you have done either of these, you will receive message CPA3394 - Load form type '&4' device &5 writer &1 in the writer's message queue whenever the form type changes. However, if the writer ends and restarts automatically or manually without specifying FORMTYPE(*ALL *INQMSG), you will no longer receive message CPA3394.

Notes

Admin Alert: More on Remote OUTQs and Printer Load Form Messages

by Timothy Prickett Morgan

One of the nice things about writing the Admin Alert column is the dedicated readers who fill in the gaps in my knowledge. Several readers e-mailed to correct my assertion last week that remote writers don't send reply messages to your iSeries or AS/400, demonstrating that the auto-answer technique for replying to printer load form messages, which I wrote about a few weeks ago, would indeed work with remote printer output queues.

For the record, I was wrong when I said that you could not auto-answer printer load form messages for remote writers, because OS/400 doesn't allow for these messages with remote output queues. OS/400 remote writers are capable of sending and receiving replies to printer load form messages from remote writers, and here's a sampling of the volumes of e-mail I received on the subject to prove it. I offer these tidbits to add to this column's collective knowledge.

The general reaction to my comments is best summed up in this e-mail from Doug Streifling:

Regarding your column's comment that "remote OUTQs don't care about forms," I beg to differ.

IBM does indeed support forms changes for remote output queues. All of our printers (about 50) are TCP/IP-attached devices. Six of these are used to print checks, and it is vital that the operator is warned if it is time to load check forms. I can assure you that our payroll and accounts-payable people receive a break message to load forms, just like we are used to from days of old. We have done no special programming; we just specify the form type on the print file.

The default for the Form Type options (FORMTYPE) parameter of Start Remote Writer (STRRMTWTR) is FORMTYPE(*ALL *NOMSG), which causes the printer to behave exactly as described in your article (that is, it leaves load form message handling to the remote system). However, if you specify FORMTYPE(*ALL *INQMSG), the remote writer will generate a "load forms" message when a spooled file is sent to the printer that has a form type that is different from the last form type sent. A really easy way to implement load form inquiry messages is to change the STRRMTWTR FORMTYPE parameter command default from *NOMSG to *INQMSG. This solves the problem instantly.

So this means I was half-wrong and that remote output queue writers will send load form type messages back to OS/400, provided that they are started correctly. I tested the above technique on a fresh remote printer output queue, started through Doug's FORMTYPE settings, and it worked. I did receive printer load messages prompting me to load the correct forms before printing started.

But notice that Doug mentioned that you can change the default settings for the STRRMTWTR FORMTYPE parameter to (*ALL *INQMSG) in order to specify that new remote writers will automatically send back inquiry messages. The exact command for doing so was provided by Peter Amstutz:

You can change the command so that you do get load forms messages by changing the FORMTYPE parameter default option to *INQMSG, with the following Change Command Default (CHGCMDDFT) command:

CHGCMDDFT CMD(STRRMTWTR) NEWDFT('FORMTYPE(*ALL *INQMSG)')

Unless specifically overwritten, any remote output queue created with STRRMTWTR will automatically send back printer messages. Your change to the reply list entry would work in this case for a remote writer.

So in two e-mails, I received one quick technique for configuring my remote output queues to receive form messages. But that wasn't the end of it. Another reader wrote in with an additional technique for receiving printer messages from remote writers:

If you use the CHGOUTQ command to put the following string in the Destination Option parameter of your remote output queue, then the reply list entry technique will work.

CHGOUTQ OUTQ(output_queue_name) DESTOPT('XAIX XAUTOQ')

For this technique, only the XAUTOQ string will have an effect on your printer messages, but it's worth putting in both strings to better handle your printouts.

According to IBM documentation, the auto-queue destination option (XAUTOQ) tells OS/400 to send the files directly to the remote system unless the remote printer times out during the operation. During a timeout, the spool files are sent back to your remote output queue using the AS/400's Line Printer Daemon (LPD) server, generating an inquiry message in the process. When the remote writer is running again, it will resend the spool file to the remote system.

I tested the ability of XAUTOQ to generate a form load message on a new remote printer output queue by sending it two consecutive spool files with different form types. Sorry to say, I didn't receive an error message to change the form type. Both files printed automatically without sending out a change form type message. It's possible that I configured my test wrong, so be careful if you decide to try this solution for load form type messages. One reader said it worked and another was unable to verify that claim (although it seems that XAUTOQ by itself might be a good solution for resending spool file output when the remote printer is out of paper or offline).

The XAIX string controls how you print multiple copy spool files to the remote system. Specifying XAIX tells OS/400 that when it's printing multiple copies of the same spool file to the remote system, it should send the printouts multiple times, once for each copy. The default is to send the data once, along with its control commands, with multiple print commands embedded in the control file. According to several sources, using XAIX to control multiple spool file printing is a much more reliable way to do this.

But this reader didn't stop there. He also reminded me that one of the challenges in using TCP/IP printing is to implement page range support, where users print a range of pages from the spool file to the remote writer, rather than printing the entire spool file. Midrange Guru recently published an excellent tip on how to perform page range printing for TCP/IP printers.

So there you have it. My mistake brought out a deeper understanding of how remote output queues work and of how you can apply them to your advantage. Keep those e-mails coming, folks, because we can all learn something from them.

Notes

To clear any entry and return to the default settings run “NET TIME /SETSNTP:”. Then run “NET TIME /SET /YES”. If this is OK then run “W32TM /monitor” to ensure that each member server/workstation is actually pointing to a DC. Finally, run “W32TM /resync /rediscover” followed by “W32TM /resync /nowait”.

Notes

http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/PackageProperties.xml
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/51395005.cab
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/ConsumerC2R.en-us_14.0.5139.5005.fs.hmp
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/ConsumerC2R.en-us_14.0.5139.5005.sft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/descriptor.xml
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/click2run.msi
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/click2run64.msi
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/Office.exe
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/launchofficeintl.dll
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/autorun.inf
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/Welcomedocument.dotx
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/SetupConsumerC2ROLW.exe
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/6c21ae9e-364d-493d-957b-2e76318c4aa0.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/49676270-ab58-44e4-988f-830cfa31925a.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/2f998045-f7f5-425c-8240-2b6f0494c071.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/6fdf2913-284b-4fa3-a464-52ca68e7ee23.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/810215b0-e248-41f4-ab94-a4e5ccf04a3a.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/bc495025-9190-4fed-a7b0-81c4ee7b6608.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/ef86d2be-af9a-4862-b685-8df11bca0e90.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/71f09ff7-78de-4473-b9a3-405aab2b2d58.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/825806cd-8d35-4bf1-8b98-bcab6ce9f010.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/03c24f8a-8eee-49e0-af9e-0d022f981804.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/72c2adc3-1477-4808-968d-5839ef937741.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/977410a7-02d2-4cb1-acf1-5912ff8e1c52.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/0f334ebd-19cc-4525-822e-c89d04fe8afe.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/8fc7e737-67b6-4775-8c4b-fd25a57c88be.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/f75e9752-e901-4098-a305-d6f5abfe9723.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/ace78f19-e59a-48c1-bdad-e6ac49a3d5d9.dsft
http://c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/a13c2c8d-7f5c-45f7-ae31-039187eaf73d.dsft

Execute 'SetupConsumerC2ROLW.exe'

Thats handy - download and install office starter