This external metadata is not added by default.
You have the following options
you can define a normal metadata field in your External content stub schema, and add some event system logic to copy the necessary fields from external metadata to your regular metadata fields. This is explained by Bart Koopman in the following blog : http://www.tridiondeveloper.com/ecl-event-handlers
you can add some custom TBB's to your dd4t templates that read the external metadata, and add these fields to your dd4t xml. You can find some sample code for this option here https://gist.github.com/bkoopman/6436263 (also code written by the great Bart Koopman)
The advantage of the first option is that the metadata properties are seen as "real" metadata, so as an added bonus, you can use these fields in broker queries.
The second option might be easier to implement, as you will only need to add a template building block. The disadvantage here is that these metadata fields won't appear in the broker custom meta table.